Dynamic Language Support for First Layer Message
Admin access or Domain access to property (property group) with feature access to message/scenario partition set management.
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 v2 First Layer Message but the following instructions are applicable to the following regulatory frameworks:
    GDPR TCF v2
    GDPR non-TCF v2
    CCPA
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.
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
The Supporting Language field 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.

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).
If your organization includes either of the following components in a GDPR TCF v2 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. Click here to learn more.
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.
Continue translating every text component into the supported languages.
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.
Last modified 5mo ago