Schedule a demo
back button

Back

IAB’s updated Transparency Consent Framework (TCF 2.0): What is the timeline?

April 8, 2020byYannig Roth

Starting April, 2020, the IAB Transparency and Consent Framework (TCF) will transition to its version 2. Vendors, CMPs, and publishers/advertisers will update their websites and mobile apps to support this new version of the TCF in the coming months. This article summarizes some key elements of the version 2 of the IAB TCF and the migration calendar at Didomi.

Update, May 2020: Due to the consequences of the Covid-19 crisis, the IAB Europe, representing buy side, intermediaries and sell side, voted to extend technical support for TCF v1.1 beyond the previously announced date of 30 June to a new date of 15th August 2020.  This is the final extension, as the IAB Europe made clear, beyond which support for TCF’s version 1.1 will be deprecated.

In less than 2 years, the TCF has become the standard for running personalized ad campaigns, measurement, attribution, etc. in compliance with the GDPR. It has been adopted by all the major players and IAB-compliant CMPs like Didomi. Incorporating feedback from European data protection authorities, consumer groups, and the ad tech industry, the IAB Europe and the IAB TechLab developed a new iteration of the TCF to provide more choices and information to end users.

The key additional features of the IAB TCF version 2 are:

  • More granular purposes to offer more choices to end users
  • Flexible support for legitimate interest, allowing users to exercise their right to object more easily
  • Stacks / categories to group purposes
  • Control of allowed legal basis by publishers through publisher restrictions
  • Out-of-band legal basis for vendors
  • Improved CMP API for sharing consent between CMPs and vendors.

TCF’s version 2 and the Didomi Consent Management Platform (CMP)

Over the years, Didomi has been a strong supporter of the IAB TCF and an active developer of the standard at the IAB Techlab and the IAB Europe. We will be supporting the IAB TCF v2 specifications, following the calendar issued by the IAB Europe (see below for the calendar). Supporting the TCF version 2 at Didomi will bring changes to the Didomi Console (for managing categories of purposes and v2-specific features) and the Didomi SDKs.

The Didomi Console will be updated to allow you to enable the TCF version 2 in consent notices:

 

It will also allow managing categories of purposes (“stacks” in the TCF version 2):

 

 

We are also updating our consent notices to offer better information and choices to the user, and align with the new policies of the TCF version 2. In notices, a complete list of purposes or categories will be displayed and kept up-to-date to ensure that the user is getting a complete information at all times:

 

 

In the Preferences / Purposes section, users will now be able to give consent and exercise their right to object:

 

 

Users will be able to make similar choices for vendors, with the option to object to their data processing based on legitimate interest:

 

What is the timeline?

Please note that this calendar is the current IAB-approved calendar. It might be subject to changes as COVID-19 is making it harder for companies (vendors, CMPs, and publishers alike) to adopt the IAB TCF v2. The important dates for clients of the Didomi CMP are:

  • April, 6th 2020 – TCF v2 option added to the Web SDK and Didomi Console

The TCF v2 will be available for testing by our clients to validate their configuration and integrations with vendors. The TCF v2 will not be automatically enabled and existing consent notices will still use the TCF v1. We do not recommend clients migrating to the TCF v2 until May, 1st as vendors will still be in beta testing until the end of April.

  • April 2020 – Beta test month

Beta testing month during which vendors are expected to fine tune their TCF v2 implementation with production traffic. We recommend our clients work with their vendors to test the integration at that point. Didomi will actively work on fine tuning our TCF v2 implementation during that month so expect new features and fixes throughout the month.

  • May 2020 (Exact date TBD) – TCF v2 option added to the Mobile SDKs

The TCF v2 will be available for testing by our clients to validate their configuration and integrations with vendors. The TCF v2 will not be automatically enabled and existing consent notices will still use the TCF v1.

  • June, 30th 2020

End of the TCF v2 transition period and deprecation of the the TCF v1 support. Consent notices for websites and apps that have not migrated to the TCF v2 will be automatically migrated.

Register for Jawad’s webinar

You can find out more in our support pages, which extensively cover the TCF V2.0, the main changes, the migration calendar and the features that will be impacted. You may also want to register to our upcoming webinar (Tuesday April 14th at 3PM CEST):

Update, May 2020: Due to the consequences of the Covid-19 crisis, the IAB Europe, representing buy side, intermediaries and sell side, voted to extend technical support for TCF v1.1 beyond the previously announced date of 30 June to a new date of 15th August 2020.  This is the final extension, as the IAB Europe made clear, beyond which support for TCF’s version 1.1 will be deprecated.

Related articles

July 24, 2020byYannig Roth

5 reasons why NOW is the right time to adopt TCF v2, the IAB’s updated Transparency and Consent Framework

A lot has been said and written about TCF v2, and how to prepare the transition from v1 to v2. However, there are still some publishers who did not participate in the first version of the framework asking themselves whether it’s worth joining now. While TCF is on the path to becoming the prevailing standard…

Read more

IAB

tcf

TCF v2

July 15, 2020byYannig Roth

Google joining TCF v2… Here’s what it means for publishers

The IAB Tech Lab and IAB Europe released the second version of the Transparency & Consent Framework (TCF v2), marking a big win in terms of industry traction, as Google has announced that it will integrate the framework by August 15th 2020. Now that Google Ad Manager (Google’s Supply Side Platform, or SSP) is joining the TCF,…

Read more

CMP

Consent

IAB

TCF v2

May 13, 2020byYannig Roth

Didomi’s CMP has been approved as TCFv2-compliant (migration cut-off date now is August 15th)

We have announced yesterday that our Consent Management Platform (CMP) has successfully passed the IAB Europe’s CMP Compliance Programme (see the full list here). Many clients have started to transition to the TCF’s version 2 already, and all IAB members will have to update their websites and mobile apps to support it until the summer 2020.

Read more

CMP

compliance

IAB

TCF v2

July 3, 2020byYannig Roth

5 keys to a successful TCF v2 transition

On August 15th, the Interactive Advertising Bureau (IAB) will end its support for the Transparency and Consent Framework (TCF) v1.1, paving the way for the entire industry to adopt TCF v2 as its new standard. Are you wondering what this means if you are a publisher in the online advertising space? 

Read more

CMP

IAB

TCF v2

July 20, 2020byYannig Roth

What are the requirements of a TCF v2 compliant consent notice?

On a website or in a mobile app, the notice is the first and main consent UI that users interact with. That’s where most users get informed on purposes and vendors that consent is collected for, and how users will make a choice to give or deny consent. As a result, the content of a consent…

Read more

CMP

Consent

GDPR

TCF v2