Skip to main content
Version: v1.7.0

IAB TCF v2.2 & v2.3

At Lawwwing, we are committed to implementing the highest standards of data privacy on the internet. As part of this commitment, we follow the guidelines of the IAB Transparency and Consent Framework (IAB TCF) in its version v2.3.

Lawwwing has obtained certification from the IAB as a certified TCF provider (ID: 405):

IAB Lawwwing

Below, we provide information on what the IAB TCF is, its relevance for online publishers, and how you can enable this feature in Lawwwing.

What is the IAB TCF?​

The IAB TCF, or IAB Transparency and Consent Framework, is a set of standards and guidelines developed by the Interactive Advertising Bureau (IAB).

Its purpose is to help the digital advertising industry comply with data privacy regulations, such as the European Union’s General Data Protection Regulation (GDPR).

The TCF allows publishers and advertisers to obtain user consent in a transparent way and provide clear options about how their data is used.

For online publishers, compliance with the IAB TCF is essential for the following reasons:

  • Transparency: Provides a transparent way to obtain user consent and allows publishers to explain how data is used, which increases user trust.
  • Compatibility: By complying with the TCF, publishers can work more harmoniously with advertisers and other parts of the digital advertising supply chain that also comply with the framework.

Why is IAB TCF v2 important?​

IAB TCF v2 is the latest version of the IAB consent framework and offers significant improvements compared to previous versions. Some key improvements include:

  • Compatibility with Google Consent Mode v2: IAB TCF v2 is compatible with Google Consent Mode v2, allowing publishers to communicate user consent status to Google using the IAB consent framework.
  • Improved consent management: Version 2 of the TCF introduces enhancements in consent management, such as the ability for users to give consent for specific data processing purposes.

🔄 Evolution: from v2.2 to v2.3​

IAB TCF v2.2 (currently active)​

  • This version was released in May 2023 as the current standard version of the TCF.
  • It introduced stricter requirements for the use of legitimate interest as a legal basis, more detailed supplier disclosures, and improvements in the user consent interface.
  • v2.2 is expected to remain functional throughout 2025, while industry players prepare for the transition to the next version.

IAB TCF v2.3 — what’s changing​

The v2.3 version is currently in a transition and testing period for CMPs and publishers who want to move ahead. Some key points:

  • Transition period / estimated dates

    • The version is expected to come into force on February 1, 2026 (although the exact date has not yet been officially confirmed).
    • During 2025, v2.2 will continue to be fully accepted as the standard.
    • CMPs and websites can already start implementing and testing v2.3 before the mandatory deadline.

  • Transparency and clarity for users

    • Interfaces will need to show more clearly details such as consent duration, consent string versions, and clearer categorization of purposes (e.g. "personalization" vs "measurement").
    • The use of more user-friendly wording (less legal jargon) will be encouraged, and possibly illustrative resources to help users understand.

  • Standardized interface elements

    • v2.3 may impose stricter guidelines on cookie banner design: minimum font sizes, accessible contrast, standard "opt-out" mechanisms, etc.
    • The goal is a more uniform user experience across different websites and CMPs.

  • Reduced use of legitimate interest

    • In v2.3, certain purposes (e.g., advertising, personalization, or content) can no longer rely on legitimate interest and must explicitly obtain user consent.
    • Vendors will need to prove they have user consent when processing data for those purposes.

  • Stronger publisher controls over vendors

    • Publishers will be able to override the legal bases declared by vendors for certain purposes.
    • Dynamic configuration of data processing will be possible, so that the publisher may require consent even if the vendor claims legitimate interest.

  • Mandatory signals and compliance records

    • "No consent" signals will be mandatory: if no valid consent is given, no data should be processed.
    • CMPs must keep secure records (logs) of consent collection, with traceability, for audits and possible regulatory inspections.

  • Compatibility with the Global Privacy Platform (GPP)

    • v2.3 is designed to better interoperate with the Global Privacy Platform, allowing consent signals to be unified across jurisdictions beyond Europe.

Implementation status at Lawwwing​

✅ Lawwwing has already implemented IAB TCF v2.3, with all technical adaptations needed to support the new requirements (clearer interfaces, vendor controls, enhanced consent management, etc.).

During the transition period, we continue to provide support and compatibility for websites still operating with v2.2, but we recommend migrating as soon as possible to benefit from improvements and be ready for the mandatory switch in 2026.

Do you have questions?

If you need further assistance or have questions, don’t hesitate to contact us and we’ll be happy to help 🙂