If TCF is enabled, the player automatically detects and uses the user’s Consent String. In most cases, no additional player configuration is required.
When using common Consent Management Platforms (CMPs) such as Cookiebot or other TCF-compatible solutions, it is usually sufficient to add 3Q GmbH as a vendor in the CMP configuration. Once configured, the player automatically reads the consent information provided by the CMP and applies it accordingly.
If required, the user’s consent string can be passed directly to the ad server by including the following placeholder in the Player Configuration. It will be passed automatically if you are integrating Ads. More information: Ad Integration macros.
The consent string can be defined explicitly in the player configuration:
<script>const player = new js3q({ playoutId: '5c3b0910-8850-11e7-9273-002590c750be', container: 'player', consentString: 'place consent string here', autoplay: true});</script>
This is typically only necessary for custom or non-standard integrations.
