The IAB’s Transparency and Consent Framework (TCF) version 2.0 for enhanced support of GDPR is scheduled to take effect April 1, 2020. This is a major update from TCF version 1.1.
The key changes are:
- More defined ‘purposes’.
- More flexibility for the legal bases used by vendors.
- Different in-page JavaScript API.
References
- IAB Europe’s TCF v2.0 Homepage
- TCF Policies
- TCF v2.0 Consent String Format
- Prebid Support for Enforcing TCF v2.0
Consult with your legal counsel before determining how to utilize Prebid features in support of your overall privacy approach.
The following is a summary of how various Prebid components will support TCF v2.0 and the estimated availability dates:
Prebid.js
Support for TCF2 is broken into several phases:
| Phase | Description | Est. Availability |
|---|---|---|
| 1 | DONE – Support a ‘deviceAccess’ flag. Publishers can parse the TCF string on their own and configure Prebid.js appropriately. | Released with v3.12 |
| 2 | DONE – Update the [GDPR ConsentManagement module(https://docs.prebid.org/modules/consentManagement.html) to read TCF v2.0 strings and forward to bid adapters. | Released with v3.12 |
| 3 | DONE – Support a ‘default GDPR scope’ flag to allow control over scenarios where the CMP doesn’t respond in time. | Released with v3.13 |
| 4 | DONE – Add a new ‘GDPR Enforcement Module’ to support parsing TCF v2.0 strings and enforcing Device Access. | Released with v3.14 |
| 5 | Update the GDPR ConsentManagement module to support parsing TCF v2.0 strings and enforcing Purposes 2 and 4 | Apr 30, 2020 |
Prebid Server
| Phase | Description | Est. Availability |
|---|---|---|
| 1 | DONE – Support parsing the TCF v2.0 string and enforcing Device Access. | PBS-Go v0.105.0, PBS-Java v1.32 |
| 2 | Support parsing TCF v2.0 strings and enforcing Purposes 2, 4, 7 and Special Feature 1 | Apr 30, 2020 |
Prebid SDK
| Phase | Description | Est. Availability |
|---|---|---|
| 1 | DONE – Support the ‘deviceAccessConsent’ flag and passing TCF v2.0 strings to Prebid Server. | SDK v1.5 |