Use IAB TCF v2.3 support.

The IAB Transparency & Consent Framework is the ad-industry standard for passing consent through to hundreds of advertising vendors at once. If you sell display advertising, run header bidding, or use a Supply-Side Platform (SSP), you almost certainly need TCF.

Why v2.3 is so important: TCF v2.3 was officially released on June 19, 2025, and became mandatory on February 28, 2026. Any TC string generated after that date that does not include the new mandatory disclosedVendors segment is considered invalid by the framework. In practical terms, that means Google Ad Manager, AdSense, AdMob, and other major ad platforms will fall back to “Limited Ads” serving non-personalized ads with significantly lower revenue (often 50%+ below normal). Sites still on TCF v2.2 should migrate immediately.

What changed in v2.3: The disclosedVendors segment, which was optional under v2.2, is now mandatory. It removes ambiguity about whether a vendor was actually shown in the CMP UI to the visitor. This matters most for vendors processing data under Legitimate Interest for Special Purposes, they can now reliably tell whether they were disclosed and, therefore, whether they can lawfully process data.

The good news: TCF v2.3 is a technical update only. Your banner UI does not change, no new data is collected, and visitors do not need to re-consent. ConsentBit handles the upgrade transparently; your existing visitors keep their old TC strings until they next interact with your banner, at which point a new v2.3-compliant string is generated.

To enable in ConsentBit:

1. Go to Cookie-banner -> General.
2. Toggle Enable TCF mode on.
3. Save.

ConsentBit will now generate TCF v2.3-compliant consent strings, including the mandatory disclosedVendors segment, and pass them to all participating vendors automatically.

TC strings created before February 28, 2026 without the disclosedVendors segment remain valid until the visitor next updates their preferences, so there is no immediate revenue cliff for existing visitors. New strings created on or after that date must use v2.3.

TCF v2.3 transparency requirements (carried forward from v2.2): - The first layer of the consent UI must show the total number of vendors seeking a legal basis. - Purposes must be described in plain, easy-to-understand language with concrete examples. - Visitors must be able to reopen the consent UI at any time (the “Cookie Preferences” link covers this). - Legitimate Interest is no longer available as a legal basis for advertising purposes, only Consent.

ConsentBit’s banner templates already meet all of these requirements out of the box.

‍