Implement TCF2 consent banner in the Dailymotion Player

What is TCF2

TCF2 (Transparency and Consent Framework 2.0) is a standard developed by the IAB (Interactive Advertising Bureau) to help companies in the digital advertising ecosystem comply with data protection regulations, such as the GDPR in the European Union.

TCF2 provides a framework that companies can follow to obtain and manage user consent regarding personal data processing in the context of online advertising.

How to implement TCF2

Web

The embedded Dailymotion Player complies with the IAB TCF 2 standards and automatically detects any TCF 2-certified CMP. In such case, it collects consent sent by a Publisher’s TCF 2-certified CMP and does not deploy its independent built-in consent dialogue (i.e. a cookie banner).

Note that Dailymotion is a registered IAB Vendor (n° 573). When available, the Dailymotion Player will always rely on the consent that it receives from a CMP through the standard CMP integration. The CMP integration is currently offered at no additional fees to Publishers. 

Having a single cookie banner contributes to a less disruptive user experience which may improve the consent rate and potentially result in increased revenues. If the embedding website doesn’t use a TCF 2-compliant CMP, we use the Player’s built-in cookie banner as a fallback solution.

Android

Our Android SDK complies with IAB TCF2 standards so it’s easy to access the stored consent string and pass it to the Player.

Use a recognized CMP, generate the consent string and store it in the correct location as specified by the TCF2 IAB specifications.

When creating a PlayerView, we will automatically attempt to access the stored consent string and pass it to the Player.

In case the consent string is missing when creating a PlayerView, you can pass it using our ConsentManager()#loadConsentString(...) method.

val consentManager = ConsentManager()
consentManager.loadConsentString(context = context)