Overview
Text and HTML assets support localization, so you can keep a version of an asset for each region/language code. For details, see Localization asset in the RPI Reference guide.
When RPI Realtime serves localized content, it uses the visitor's region/language code, such as en-US. By default, it takes the code from the visitor's browser, using the first language the browser asks for.
If you store a visitor's preferred region/language code yourself, you can tell RPI Realtime to use it instead. Set RegionLanguageCodeParameter to the name of the visitor profile parameter that holds the code.
Configure the region/language code parameter
Add this value under realtimeapi, using your own parameter name:
realtimeapi:
RegionLanguageCodeParameter: ''
|
Setting |
Description |
|---|---|
|
|
The name of the visitor profile parameter that holds the visitor's region/language code, such as |
If the parameter is empty for a visitor, RPI Realtime uses that visitor's browser language instead.
Generate your overrides
When you have the values above, go to the Helm Assistant Configure tab. Refer to Managing Helm chart updates for more information about adding values to your overrides.yaml. For a complete list of realtimeapi keys, see the Helm Assistant Reference tab.