TCF v2.3: The latest version of the Transparency and Consent Framework

The Interactive Advertising Bureau (IAB) announced earlier this year the upcoming release of the latest iteration of its Transparency and Consent Framework, the TCF v2.3.

‍

What’s new, what do you need to update, and will it impact your advertising stack in any significant way? We cover it all in this article.

‍

Background and context about the Transparency and Consent Framework (TCF)

The TCF is a voluntary accountability standard created by the Interactive Advertising Bureau (IAB) to help digital advertising and publishing stakeholders adhere to GDPR requirements and standardize user data collection and management. 

‍

The framework provides a standardized way for Consent Management Platforms (CMPs) to inform users and capture consent or objections regarding personal data processing.

‍

Here’s an example of a typical TCF scenario:

The TCF is a constant work in progress, introducing technical changes and updates to improve and build on previous versions as the industry and technology evolve. The TCF v2.3 is no exception, providing updates in response to changing regulatory demands and the need for more transparent vendor disclosure and consent signals.

‍

Introduction to TCF v2.3: What is new from the TCF v2.2?

The main goal of TCF v2.3 is to clarify vendor disclosure and improve transparency for users and vendors. What changes from TCF v2.2? The TCF v2.3 aims to address vendor disclosure ambiguity and provide more explicit consent signals to users.

‍

Looking at it in closer detail, the new version of the framework: 

‍

• Introduces a mandatory Disclosed Vendors segment in all TC strings, providing a binary signal to the end user indicating vendor disclosure status.
• Clarifies vendor disclosure ambiguity, especially for vendors processing data under Legitimate Interest for Special Purposes.
• Strengthens user transparency and control over data processing by imposing stricter requirements on consent management platforms and vendors.

‍

The update is the result of extensive industry consultation and collaboration among IAB Tech Lab, IAB Europe, and data protection authorities and carries significant implications for digital advertising, requiring companies to adapt to new requirements and ensure compliance.

‍

Check out the following table for a complete side-by-side breakdown between the TCF v2.2 and TCF 2.3.

‍

Side-by-side comparison of TCF v2.2 vs v2.3

Implementation deadline and next steps: How Didomi can help

Companies must review and update their technical specifications, consent management platforms, and vendor lists to ensure compliance with TCF 2.3, which is expected to become mandatory on February 1, 2026, according to IAB and the IAB Tech Lab:

‍

​​February 1st, 2026 (TBC) – All CMPs and Vendors will be required to update their implementation to support v2.3

- Rowena Lam, Sr Director, Privacy & Data at IAB Tech Lab (Source: IAB Tech Lab)

‍

The Global Vendor List format will be updated at that time to reflect the new requirements, and companies must ensure their vendors are listed correctly.

‍

We at Didomi are actively involved in the new framework. We are pleased to announce that our Consent Management Platform (CMP) is now fully compliant with the latest version of the framework.

What should you do next, and what does this mean for Didomi clients?

If you’re using a competing CMP, make sure the platform is TCF v2.3-compliant. If not, check out our easy migration process. If you are not using a CMP, we strongly encourage you to consider implementing one. Explore our comprehensive CMP comparison list to discover the ideal solution for your needs.

‍

For Didomi customers, this update will roll out automatically ahead of the IAB’s February 1, 2026, deadline. We’re anticipating the change early and will provide customers with access before the official enforcement date.

‍

There’s no action needed in your console, and it won’t trigger any new data collection. The update is entirely transparent for both you and your users. The new TCF string will automatically generate the next time someone views the notice or provides consent. In short, you’ll stay compliant and ready well before the deadline, with no extra effort required.

‍

Learn more about the TCF v2.3 in our technical documentation and on the IAB website. To reach out to our team of experts, book a call at your convenience:

‍

{{talk-to-an-expert}}