In this article: About custom content according to browser language | Examples | How to set up a browser language condition
The browser language condition lets you add or replace content on your website according to the users’ defined languages for their browser.
Possible Use Cases
Display product recommendations in the visitor’s language.
Redirect users to a page in their own language
Grab attention with a short message in the visitor’s language
Translate your website’s calls to action
Most desktop browsers have settings that allow you to edit your language preference settings. These tell the server what language you prefer for pages and resources that it sends you (separate from the language of the browser user interface).
For browsers on mobile devices, the language preferences are likely to be determined by the operating system settings, or in some cases by the language of the system when you installed the browser.
Browsers that allow you to change your language preferences will generally allow you to specify a list of languages so that if your first choice is not available, you can set which alternative languages to try, and in what order.
How to configure the browser language in common browsers:
As written above, some browsers allow users to specify a list of languages so that if their first choice is not available they can set alternative languages to try, and determine their order. If-So allows you to choose whether to display the dynamic version for a primary language only, or also for secondary browser languages. This option is extremely useful when you want to grab visitors’ attention with a message in their mother tongue.
The option is useful, since in many cases the browser language condition is used to grab visitors’ attention with a message in their mother tongue language.
Same as with all of If-So’s dynamic triggers, any of the website’s content can be customized. That includes titles, texts, images, calls to action, buttons and more.
Whether you are using a caching plugin or server caching, you can navigate to the plugin settings and enable the "Page Caching Compatibility" option. With the option enabled, dynamic triggers will be rendered in a separate request that will take place after the loading of the cached version.