Each Pathmonk account is designed to generate micro experiences in one single language. So, if your website is multilanguage, there are different options that could suit you.
1. Create micro experiences for selected pages in another language
This option works best when your site is mainly in one language but includes a few pages targeting a different audience segment.
Example: An English website with a single landing page for a Chinese-speaking community.
How it works:
Go to the Accelerate Tab → Microexperiences → Products & Services.
Create a micro experiences tied to the specific URL that uses the second language.
Repeat for any additional pages you want to localize.
Pathmonk will display the micro experience only after the visitor browsed those selected pages.
2. Create a separate account for each language-specific subdomain or subdirectory
This option is ideal for websites that switch subdomains or subdirectories based on language (e.g., example.com/es/ or es.example.com).
How it works:
Set up a dedicated Pathmonk account for the language version.
Build a full set of micro experience in that language.
At the account level, exclude other domains or directories so visitors only see micro experiences relevant to the language they’re browsing.
This ensures clean separation and accurate targeting for each language.
3. Show micro experience only to visitors from certain countries
This option suits websites that receive global traffic but want to trigger micro experiences only for users from specific language-based regions.
Example: A website receiving traffic from across LATAM but only wanting to show Spanish-language micro experiences.
How it works:
Purchase our Geolocation add-on
Apply audience filters based on country.
Micro experiences will be shown only to visitors from the selected regions.
Need help setting up your multilanguage website?
Get in touch with our team at support@pathmonk.com and we'll evaluate the best option for your case.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article