Deadline to switch over to TCF v2.0 extended to August 15

We understand that many publishers’ operations have been impacted by the unprecedented upheaval and disruption caused by the COVID-19 crisis. That’s why the IAB Europe Transparency & Consent Framework (TCF) Steering Group has voted to extend the deadline to switch over to TCF v2.0 to August 15, 2020. 

What does this mean for you? 

Technical support for TCF v1.1 will be extended to August 15 

You can use both v1.1 and v2.0 simultaneously until August 15, if desired, but for a single property we recommend having only one version active.

V1.1 consent strings created before cutoff valid through September 30

In an effort to gradually transition v1.1 to v2.0, any consent strings created under TCF v1.1 before August 15 will be valid through September 30.

Your launch date should be easier to coordinate

Google’s formal implementation of TCF v2.0 will start on August 15, instead of June 30. Your other TCF vendors are likely on track to support v2.0 by the new date; over 400 of the 600 registered for the v1.1 vendor list have already registered for the new vendor list and over 75% have declared themselves operational. See the current GVL v2.0.

For more info, check out our recent webinar “Switching to TCF v2.0: What publishers need to know” for a presentation of the different aspects you need to consider for your migration.