Dynamic language support (privacy manager)

   Permission: Campaign entities

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


Privacy manager language settings

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

  • GDPR TCF
  • GDPR Standard
  • CCPA

Screen_Shot_2021-11-05_at_4.33.09_PM.png

From the Home view of the privacy manager 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 privacy manager.

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 privacy manager dynamically surface the appropriate translations based on an end-user's default browser language.

 

Screen_Shot_2021-05-12_at_3.09.21_PM.png


Provide translation to components

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

  Note: Generally, IAB specific components will have translations automatically supplied by the IAB (i.e. your organization will not need to provide your own translations). The exceptions are as follows:

  • Custom stacks/purposes (provided by your organization via the Vendor List)
  • TCF v2.1 cookie duration text (provided by Sourcepoint in limited languages)

Please click here for advice on checking provided vs non-provided translations.

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.

gif.gif

Continue translating every text component into the supported languages. This will also included aspects of the PMTCFv2Inline or PrivacyManagerTCFv2 components.

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-12_at_3.39.27_PM.png


(Optional) Test privacy manager translations for GDPR TCF

Generally, IAB specific components will have translations automatically supplied by the IAB (i.e. your organization will not need to provide your own translations). Two notable exceptions are:

  • Custom stacks/purposes (provided by your organization via the vendor list)
  • TCF v2.1 cookie duration text (provided by Sourcepoint in limited languages)

We suggest that once translations are uploaded for all text elements in your privacy manager that you change your browser language to the supported language and refresh your privacy manager. The dynamic language support will be triggered and the vendor list elements will be displayed with the IAB supplied translations.

Screen_Shot_2021-05-12_at_4.12.40_PM.png

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