GDPR and TCF 2.0

Javascript SDK and iFrames

If the Player is embedded in a GDPR-compliant Environment and the Frontend uses a TCF 2.0 enabled CMP, there is nothing to change. The Player will detect TCF 2.0 Functionality automatically and uses Consent Strings and Settings accordingly.

The automatic TCF 2.0 Detection is available in the SDK for Javascript, but also in any Form of iFrame Integration.

Nevertheless, if the Frontend does not use a CMP or is not TCF 2.0 compliant, but needs some kind of Consent Strings for Ad Purposes, the Javascript SDK and also the iFrame Service supports this.

For the Javascript SDK, please use the "setUserConsentString" Method:

pagePlayer Management

For iFrames, please add the "consentString" Parameter to the iFrame URL:

pageEmbed Codes

Device Storage

Depending on various Configurations and Features, the Player SDK may store Data in Cookies, localStorage, sessionStorage and IndexedDB. If an active TCF Configuration is active on Page, the Player SDK will respect the Removal of Storage Rights by this Framework and immediately stop using Cookies (and remove all exisiting ones).

For further Details, 3Q offers an in-depth Device Storage Overview in accordance with IAB/TCF Guidelines here:

Native Players

For native Players please use the Override Parameter "consentString" for applying the received Consent String to the Player.

pagenexxPLAY for iOSpagenexxPLAY for Android

VAST Macros

Unimportant which SDK is used, Consent String and GDPR Compliance is mostly only needed in Environments, where Ad Providers depend on these Strings - in this Case, the Ad VAST URLs must also contain the necessary Macros.

pageVAST Macros

Last updated