Permission: Campaign entities
In this article, we will cover how to dynamically present translations of your custom message to end-users based on their default browser language.
Custom message language settings
To start, navigate to or create a custom message on your property.
From the Home view of the custom message builder, navigate to the Settings panel on the right-hand side and expand the Language accordion.
Defines the language that will appear by default for your end-users. That is, if the end-user's browser default language is not supported and a language translation is not provided, the end-user will see all content in your default language.
Use the provided dropdown menu to select your default language for the custom message.
Allows you to add all the languages you plan to support with your uploaded translations.
Note: The default language is also added to the Supporting Language field.
|Use Browser Default
|Toggle this feature ON in order to have the custom message dynamically surface the appropriate translations based on an end-user's default browser language.
Provide translation to components
If you have added additional languages to the Supporting Language field (other than the default language), you will have the option to upload component translations in bulk via csv file.
Expand the Bulk Upload Translation accordion and use the provided dropdown menu to select all of the message components you wish to translate.
Click Download CSV file when finished.
In the subsequent modal, Sourcepoint will surface the assigned component names and allow your organization to edit any of these names before downloading the csv template. These names should be unique and is used by the Sourcepoint system to map translations to the correct component.
Click Update & Download.
The csv template for your selected components will be downloaded to your machine and the component names will be updated to reflect your edits.
The csv template will list out the components of your custom message, the copy for each component in your default language, and spaces to add translations for each component in your supporting language(s).
Add translations for each component in the appropriate cell.
Note: You will notice that the default language for text components will have the html tags. While you do not have to include the html tags in your provided translations for supported languages, it may be useful to utilize these tags to maintain inline links.
Navigate back to the custom message builder and click Upload transition file.
Once the csv template is uploaded, a modal will confirm the translations that were added, replaced, and that are still missing.
Select your supported language from the Preview message dropdown menu to view the translated components in the custom message builder.
Note: Components with missing translations will use the default language in the preview.