To start, navigate to or create a native OTT message on a property. In this article, we will use a GDPR TCF v2 native OTT message but the following instructions are applicable to the following regulatory frameworks:
GDPR TCF v2
From the Global Setting tab of the native OTT message builder, expand the Native OTT Global Settings 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 message.
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.
Provide translation to components
With the language settings for the message 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:
Click the component and expand the Content accordion in the Settings pane.
Select a supported language from the Language field.
Input the translation of the text in the Text field.
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.
(Optional) Test OTT/CTV message translations for GDPR TCF v2
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 message that you change your browser language to the supported language and refresh your message. The dynamic language support will be triggered and the vendor list elements will be displayed with the IAB supplied translations.