4. Language support
Learn how to configure language support and make copy changes in the Loyalty Microsite, including available languages, requesting new translations, and adjusting default text.
About Loyalty Microsite language support
The Loyalty Microsite supports multiple languages, enabling you to offer a localized experience to your users. You can set a default language in the microsite settings, but you can specify a different language using the ?lang=
parameter in the URL.
Currently, supported languages include French (fr), German (de), and Italian (it). To load the microsite in French, for example, you would use the URL format:
https://MICROSITEURL.COM?lang=fr
Adding new languages
If your program requires additional languages beyond those currently supported, you can provide the necessary translations. WLL will supply a file containing all the English language strings used in the microsite, which you can then translate and return to us. Our team will integrate these translations and deploy your microsite in the chosen language(s).
Customizing copy
The translation system also enables you to customize any default text in the microsite. For instance, if you prefer to use the term “credits” instead of “points,” we can apply this change across all relevant instances. To request a copy update, provide a CSV or Excel file with three columns:
Location: Describe where the existing text appears (e.g., “user summary banner”).
Before: Copy and paste the current string exactly as it appears.
After: Enter the desired replacement text.
During the onboarding process, these requests can be made directly to your onboarding manager. After your solution goes live, any further copy changes require a formal change request submitted through your WLL account manager.
FAQs
Does the language change affect the entire microsite?
No, the language change only applies to the hard-coded interface text in the microsite. Resource data like rewards, tiers, and badges do support multiple locales, but these must be set individually within each resource’s details. If a translation is not available for a particular resource in the user’s selected language, the microsite will display it in the microsite’s default language. If a default language is not available, it will fall back to the resource’s own default language.
Do language changes impact any custom fields or profile data?
No, language changes apply only to the microsite’s interface text. Any custom fields or profile data specific to individual users will appear exactly as entered, as the profile schema does not currently support localisation and can only be defined in a single language.
Last updated
Was this helpful?