Hi Graham,

This approach did cross my mind, do you see any downside to this approach?

I take it you would need to write something to intercept the request and set the market accordingly?

Thanks

Paul

Hi Paul,
There are various approaches that you could take to set the market accordingly:

The preferred content language is determined by the following rules:

1. If you have defined the host name to be associated with a specific language, that language is used. The setting is specified under Manage Sites in admin view.
2. If there is a language segment in the URL (like http://company.com/en/info), that language is used (en).
3, If you are in the edit view and have selected a specific language site from the Sites section, that language is used.
4. If the requests contain a query parameter or cookie named epslanguage, use the language defined by the query/cookie.
5. If the setting GlobalizationSettingsOptions.UseBrowserLanguagePreferences is true, then the language preference from the web browser is used.
6. Use the language mapped to wildcard host '*' if specified.
7. Fetch the setting from the GlobalizationOptions.UICultureLanguageCode.
8. If nothing else is discovered, use the first enabled language branch as defined in Admin / Language Branches, which means that it can be viewed as the default language.

I think points 4 and 5 relate directly to what you are asking, failing that you could go down the path of intercepting the route, there is some further information about Optimizely routing here:

https://docs.developers.optimizely.com/content-cloud/v12.0.0-content-cloud/docs/routing

and it is also worth mentioning that you can access the content language in various ways as described here:

https://docs.developers.optimizely.com/content-cloud/v12.0.0-content-cloud/docs/determining-languages

I hope that helps you out.

Thanks,

Graham