How to prepare for TCF v2.0?
TCF v2 will be taking effect as of Q2 this year and you’d better start the process of preparing for this change. This is a big change that will impact your users and vendors in terms of how consent will be read and transmitted across the IAB Framework.
Background: what is TCF v2.0?
Key dates for TCF v2
- March 31, 2020: Start of TCF v2 Beta period
- April 30, 2020: Start of TCF v2 General Availability (GA)
- August 15, 2020: TCF v1 is disabled
Although we will be providing you with the ability to switch on the v2 CMP within your portal, it’s important to review the below action items before switching over as doing this too early may negatively impact your business. This timeline ensures that TCF v2 signals can be generated in the wild, vendors can validate they are receiving and handling them correctly, and everyone can fix bugs / issues that arise.
Key action points to think about as publishers/advertisers
These should be assessed with your key stakeholders and legal teams as you start to think about this.
1. Vendor Audit
- Have your most important revenue partners re-registered for TCF v2?
- Will they be ready for the v2 deadlines?
- If a vendor is not registered with the TCF, can I include them in my CMP?
2. Purposes and Stacks
The whole Framework will be changing its standardized purposes from 5 to 12 in the new version. Purposes can be grouped into “stacks”. Stacks may be used to aggregate initial layer information about two or more Purposes and/or Special Features, see more here. Quantcast recommends an optimized combination of stacks. Have you thought about what stacks you will be using?
3. UX Changes
The IAB policy for V2 will require all purposes/stacks to be displayed on the initial screen, which may impact consent rates.
Recommended IAB Resources on TCF v2
- GitHub: IAB Europe TCF Guidelines
- TCF v2 Technical Specifications API Documentation
- TCF v2 Technical Specifications Consent String & Global Vendor List Format
- TCF v2 Policy Documentation
- TCF v2 Global Vendor List JSON file (useful to check up on vendors who are operationally ready to support TCF v2 signals)
- TCF v2 Stack Combinations
- TCF V2 Webinar