Thanks for clarifying, @lime_will!
HubSpot's out-of-the-box solution for country localizations is the smart content Country filter. You can set modules to display different content based on the IP country of the visitor.
With this approach, you wouldn't have to send query parameters, but IP country values aren't foolproof either. As I'm sure you know, someone on a VPN could appear as browsing from a different country than what you have on file.
I understand your concern about conflating language and country. I brought that up in response to @John_Wachunas bringing up a
lang parameter. The
hslang parameter allows you to leverage translations of HubSpot pages, which is a bit more robust a solution than smart content, however it relates more to language than country.
As a quick comparison:
- Smart content was developed before page translations.
- Smart content is used to modify the content within modules on a single page.
- In contrast, page translations are truly different pages with language-specific slugs.
- You must translate the content on translated pages yourself — HubSpot has no auto-translate feature at this time.
- Translated pages support smart content themselves, so, if you wanted, you could have different translated pages based on the visitor's preferred language and a layer within each translation for the IP country.