Dynamic language support (first layer message)

   Permission: Campaign entities

In this article, we will cover how to dynamically present translations of your first layer message to end-users based on their default browser language.


First layer message language settings

To start, navigate to or create a first layer message on a property. In this article, we will use a GDPR TCF first layer message but the following instructions are applicable to the following regulatory frameworks:

  • GDPR TCF
  • GDPR Standard
  • CCPA

Screen_Shot_2021-10-27_at_1.55.47_PM.png

From the Home view of the first layer message builder, navigate to the Settings panel on the right-hand side and expand the Language accordion.

Screen_Shot_2021-05-11_at_2.01.16_PM.png

Field Description
Default Language

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 first layer message.

Supporting Language

Allows you to add all the languages you plan to support with your uploaded translations.

  Note: Ensure that your default language is also added to the Supporting Language field.

Use Browser Default Toggle this feature ON in order to have the first layer message dynamically surface the appropriate translations based on an end-user's default browser language.

 

Screen_Shot_2021-05-11_at_2.18.50_PM.png


Provide translation to components

With the language settings for the first layer message configured, your organization can now upload translations for each text component (and components with text fields such as buttons).

  Note: If your organization includes either of the following components in a GDPR TCF first layer message

  • Vendor List Stacks/Purposes
  • Vendor List Stacks/Purposes with Opt-in Controls

IAB features such as IAB purposes and IAB stacks will have translations automatically supplied by the IAB.

Custom stacks and/or custom purposes will need to have translations supplied by your organization and can be configured in the Vendor List.

Uploading a translation for any text will follow the same process:

  1. Click the component and expand the Content accordion in the Settings pane.
  2. Select a supported language from the Language field.
  3. Input the translation of the text in the Text field.
  4. Repeat as necessary for other supported languages.

1.gif

Continue translating every text component into the supported languages.

  Note: Your organization can save your progress along the way. Upon each save attempt, Sourcepoint will inform of you of missing translations required for your text and button components.

Screen_Shot_2021-05-11_at_3.16.17_PM.png

Was this article helpful?
0 out of 0 found this helpful