The IAB Europe Transparency & Consent Framework (TCF) keeps evolving to meet regulatory expectations and improve transparency for users.
The latest version, TCF 2.3, was officially announced on June 19, 2025, with updates that clarify vendor disclosure and strengthen accountability across the digital advertising ecosystem.
Here’s what’s changing, what it means for you, and how to get ready.
What is TCF 2.3?
TCF 2.3 is the latest version of the IAB Europe Transparency and Consent Framework.
It’s the industry standard that helps publishers and advertisers operationalize with the GDPR and the ePrivacy Directive when processing personal data for digital advertising:
- It gives Consent Management Platforms (CMPs) like iubenda a standardized way to inform users and capture consent (or objections) for advertising.
- It makes sure consent signals are communicated consistently across the advertising supply chain, from your site to every vendor you work with.
What changes from the previous version?
TCF 2.2 (launched in May 2023) focused on implementing changes required by the Belgian Data Protection Authority and improving user-friendly descriptions. TCF 2.3 now tackles a different challenge: vendor disclosure ambiguity.
Mandatory “Disclosed Vendors” segment
The main change in TCF 2.3 is that the “Disclosed Vendors” section is now mandatory in all TC strings. Previously, it was optional.
– Clear binary signal: The Disclosed Vendors segment provides a simple indicator (1 = disclosed, 0 = not disclosed) specifying whether a vendor was shown to the user.
– Updated TC string structure: The string format now follows the following pattern [Core segment].[disclosedVendors segment].[Publisher TC].
– No more ambiguity: Vendors can now confirm whether they were properly disclosed to users before processing data.
Why this change?
Under TCF 2.2, some vendors faced uncertainty in scenarios where it wasn’t clear whether they’d been disclosed to the user.
For example, when a CMP registered a user objection under Legitimate Interest, a vendor couldn’t always tell whether they’d actually been shown to the user. This distinction matters because vendors must be disclosed to users as part of meeting transparency obligations before processing data, including for Special Purposes.
By making the Disclosed Vendors segment mandatory, TCF 2.3 removes this ambiguity. This means cleaner signals across your advertising stack and fewer issues with vendor data processing.
| TCF 2.2 | TCF 2.3 |
| “Disclosed Vendors” segment is optional | “Disclosed Vendors” segment is mandatory |
| Ambiguity for vendors processing under Legitimate Interest for Special Purposes | Clear binary signal confirms vendor disclosure status |
| TC string may or may not include disclosed vendors | TC string structure requires: [Core].[disclosedVendors].[Publisher TC] |
| Vendors interpret signals without certainty | Vendors can confirm disclosure before processing |
What’s the timeline for implementation?
Here are the key dates to keep in mind:
June 19, 2025: TCF 2.3 officially announced and technical specifications released.
October 2025: Google confirmed its systems can accept and process TCF 2.3 strings.
🚨 February 28, 2026: Mandatory deadline. All CMPs and vendors need to support TCF 2.3. Support for new TCF 2.2 strings ends on this date.
Good to know: TC strings generated on or after February 28, 2026 must follow TCF 2.3 specifications. TCF 2.2 strings created before that date will still be valid.
If you use Google AdSense, Ad Manager, or AdMob in the EEA, UK, or Switzerland, you’ll need TCF 2.3 support by February 28, 2026.
Google has confirmed its systems can accept and process TCF 2.3 strings. If you miss the deadline, your ad requests may default to Limited Ads serving, which typically means lower revenue.
The good news? With iubenda, no need to worry. We’ve got you covered.
What does this mean for iubenda customers?
If you’re using iubenda’s Privacy Controls and Cookie Solution, you’re all set. Our CMP already handles TCF 2.3 requirements.
Here’s what’s next for you:
- If you’re ready now: Set
tcfVersion = 2.3in your configuration to start using TCF 2.3 signals immediately. This is a good choice if you want to test the new signals with your ad stack before the mandatory date.
- Prefer a hands-off approach? Let us handle it: We’ll automatically switch your signals to TCF 2.3 after the February 28, 2026 deadline. You don’t need to do anything.
✔️ No banner changes needed: TCF 2.3 is a technical update. Your consent banner interface stays exactly the same.
✔️ No new data collection: This update doesn’t introduce new categories of personal data or expand data processing purposes.
✔️ Your users won’t notice: The change happens behind the scenes. The new TC string automatically generates the next time someone interacts with your consent notice.
- Mobile apps and CTV: for this type of implementation, you may need to update to the latest version of our SDK. We’ll share detailed guidance closer to the deadline.
- Make sure to review your vendor list and confirm your vendors are registered on the updated Global Vendor List.
Frequently Asked Questions
Do I need to show my consent banner again?
No. TCF 2.3 changes how consent is signaled technically, not the user-facing interface. In standard scenarios, you don’t need to re-collect consent from your visitors.
What happens to my existing TCF 2.2 consent strings?
TCF 2.2 strings created before February 28, 2026 remain valid. Only new strings generated on or after that date need to follow TCF 2.3 specifications.
Will TCF 2.3 affect my ad revenue?
Not if you’re ready by the deadline. If your CMP isn’t updated in time, platforms like Google may default to Limited Ads serving, which could reduce revenue. With iubenda, you’re covered: switch now with tcfVersion = 2.3 or let us handle it automatically.
Does TCF 2.3 change anything about legal bases or purposes?
No. TCF 2.3 doesn’t change the legal bases available to vendors or the purposes defined in the framework. It focuses specifically on improving how vendor disclosure is communicated.
I use Google’s products. Do I need to do anything extra?
No. As long as you’re using iubenda’s TCF 2.3 signals by the deadline (either by switching now or letting us handle it automatically), you’ll meet Google’s requirements.
Over to you
Questions about TCF 2.3 or your setup? Reach out to our support team at info@iubenda.com.