What is TCF v2.2

In summary, the TCF v2.2 brings several important changes to the digital advertising industry by expanding the scope of the framework, updating the UI requirements for CMPs, introducing policy changes, enhancing accountability and transparency requirements, and updating technical specifications. These updates are designed to give users more control over their consent choices, increase transparency and accountability, and improve the overall user experience. The IAB has given CMPs and publishers until November 20, 2023 to implement the new policies and specifications.

Consent banner changes within TCF v2.2 

To align with the updates in TCF v2.2, the Usercentrics banner will undergo the following modifications:

1. Vendor Count: The Usercentrics CMP will show the combined number of both IAB and non-IAB vendors on the initial layer.

2. Vendor Information Disclosure: Any new information provided by the vendors will be made transparent to the end users. On the Second Layer layer, we will include:

   • Categories of the data collected.

   • Retention periods, specified for each purpose.

   • Links that provide further insight into legitimate interests, where relevant. 

3. Opt-in and opt-out: It's mandatory for all CMPs to provide both opt-in and opt-out options. Notably, the Usercentrics CMP already includes these features.

Open

Open

Vendor list changes

With the launch of TCF 2.2, the new vendor list will be introduced. As vendors add more information to this list, the TCF framework will provide greater transparency and clarity for site visitors. The updated vendor list will be referred to as Version 3 and will be consistent with the TCF Policy Version 4.

You can view the current global vendor list and all its details here.

The latest vendor list brings several changes regarding vendors and their purposes. In particular, it removes "legitimate interest" as a legal basis for advertising and content personalization (purposes 3, 4, 5, & 6). It also introduces a new purpose (purpose 11): "Use limited data to select content."

Migration instructions for TCF v2.2

Standard setup

1. Open the Admin Interface of the Configuration ID where your TCF v2.0 banner is set up.

2. Navigate to Configuration > Legal Specifications > Transparency & Consent Framework (TCF).

3. Click the radio button to switch from TCF 2.0 to TCF 2.2 (see screenshot below).

After selecting “TCF v2.2”, another window will appear with information about the changes that will take place for the migration. You have the option to keep your selected vendors also in the new version of TCF, but we highly recommend that you check if these vendors are still relevant to you.

4. Only after you click on “Publish” in the bottom left corner will the migration begin.

Browser SDK

The TCF v2.2 specification introduces some changes to the vendor information provided that require adaptation.

Removed in v2.2:

• purpose.legalDescription string (replaced with illustrations)

• purpose.policyUrl string (replaced with privacyUrl)

New in v2.2:

Purposes/Features

• purpose.illustrations string[] → replacement for legalDescription

• specialPurpose.illustrations string[] → replacement for legalDescription

• specialFeature.illustrations string[] → replacement for legalDescription

• feature.illustrations string[] → replacement for legalDescription

Vendors

• vendor.legitimateInterestClaimUrl string → vendor url for legitimate interest insights

• vendor.privacyUrl string → replacement for policyUrl

• vendor.dataCategories { id, name }[] → list of data categories

• vendor.dataRetention { id, name }[] → list of data retention

Labels

• dataCategories string -> label for vendor.dataCategories

• dataRetention string -> label for vendor.dataRetention

• legitimateInterestClaim string -> label for vendor.legitimateInterestClaimUrl

Deprecation of the “getTCData” command

TCF version 2.2 deprecates the command “getTCData”. If you are currently using the “getTCData” command in any implementation, it's important to switch to the event listener function. For full details on the event listener implementation, please refer to our documentation: TCF Documentation.

App SDK 📱

If you are using a TCF configuration in your apps or you have a “hybrid setup”(using one configuration for TCF on both web and app), TCF v2.2. is now supported with the Apps SDK v.2.9.0.

PUR model

Web

If you are using a PUR model banner within your Usercentrics CMP, you need to implement the vendor count into your text yourself. To get the vendor count, we provide a new method to fetch the vendor count “UC_UI.getThirdPartyCount()”. Use this method to display the vendor count on your first layer. Note that this is a TCF 2.2 requirement and must be implemented. If you have further questions, please contact us directly.

Apps

If you are integrating a PUR model banner into your mobile app using the Usercentrics CMP, it is essential to include the vendor count within your app. To obtain the vendor count, we offer specific methods for both Android and iOS platforms.

Android

iOS

FAQ

Why do I need to migrate to TCF v2.2?

There are several reasons why you should migrate to TCF v2.2: 

• After November 20, 2023, new TCF strings created under TCF 2.0 will no longer be valid.

• From February 2024, publishers and developers who are using Google services such Google AdSense, Ad Manager, or AdMob, are required to use a Google certified CMP that integrates with the TCF v2.2 when serving ads to users in the European Economic Area or the UK.

• We will deprecate TCF v2.0 in the Usercentrics CMP on the 19th of April, 2024.

• TCF v2.2 includes enhancements that give users more transparency and control over their data preferences, in line with evolving data privacy regulations. 

• Staying current with the latest version ensures compliance with industry standards and builds trust with users and partners alike. 

• TCF v2.2 provides publishers with greater flexibility to communicate user choices to third parties, improving the overall consent ecosystem.

Does migration always trigger a renewal of consents?

Generally, migrating from TCF v2.0 to TCF v2.2 does not require a consent renewal, which means that the consent banner does not automatically need to be re-displayed. A primary reason for consent renewal would be significant changes in your vendors and their purposes. 

We respect the standard settings you apply to your configuration when it comes to resurfacing. With the TCF v2.0 to 2.2 migration we also trigger a resurface, when  a vendor adds an additional purpose to its purpose list.

Let’s look at an example of a vendor change that would trigger a resurfacing:

• Vendor-ID: 15

  • GVL-Version 2:

    • Purposes: 1,2,3,4,5,6,9,10

  • GVL-Version 3:

    • Purposes: 1,2,3,4,5,6,9,10,11

• In this case, the vendor selected within your implementation has added one additional purpose (purpose 11). If you have this vendor implemented, this would require a resurface.

For your convenience, we've provided a list of vendors with updated purposes, which you can view here. Please be aware that the version of the vendor list is indicated at the top of the document, as purpose changes can vary between different vendor lists.

Will existing TCF2.0 strings be valid after November 20, 2023?

Yes, all existing TCF v2.0 strings that were created before November 20, will remain valid after that date, unless you renew the consent. However, keep in mind that this TC string will only consent to vendors based on the TCF v2.0 vendor list. If a user on your website changes or withdraws their consent, they will see the content of the new TCF v2.2 vendor list within the consent banner. 

This way, we always ensure that new consents and changes will be applied based on TCF v2.2. We are aware that this may lead to a lack of transparency regarding a customer's current consent selection. If you are concerned about this lack of transparency, we recommend that you renew your consents. 

What were the consequences of not migrating by November 20, 2023?

If you did not migrate by the required deadline of November 20, 2023, any TC strings obtained under TCF v2.0 are considered to be invalid. This could adversely affect your agreements with advertisers, potentially resulting in a decrease in your ad revenues. 

For customers that did not migrate to TCF v2.2 yet, there is a final deadline for the migration on April 18,

What will the consequence be if I do not migrate before April 19, 2024?

Besides that consequences mentioned above, the following consequences apply:

• We will automatically migrate your setup to TCF v2.2 which will require you to check your configuration and test your setup to make sure everything is still functioning.

• A resurfacing of the banner might be required to collect new updated consent.

• Since the IAB deadline has passed, we are not able to support you with issues related to your TCF v2.0 implementation if you don’t migrate.

Related articles