TCF v2.3 is coming – are you ready for the February 2026 deadline?

If you’re working with programmatic, Microsoft Ads, or any EU traffic — this matters.
IAB Europe has set February 28, 2026 as the compliance deadline for implementing TCF v2.3.
At first glance, it may look like a minor update.

𝗧𝗖𝗙 𝘃𝟮.𝟯 𝗶𝘀 𝗰𝗼𝗺𝗶𝗻𝗴 – 𝗮𝗿𝗲 𝘆𝗼𝘂 𝗿𝗲𝗮𝗱𝘆 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗙𝗲𝗯𝗿𝘂𝗮𝗿𝘆 𝟮𝟬𝟮𝟲 𝗱𝗲𝗮𝗱𝗹𝗶𝗻𝗲?
It’s not.
𝗪𝗵𝗮𝘁’𝘀 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴?
TCF v2.3 introduces a mandatory “Disclosed Vendors” segment in the TC string.
In simple terms:
More clarity.
More transparency.
More precision around which vendors are disclosed in consent strings.
For new TC strings created after the deadline, this segment must be included.
What you should know
Microsoft ad systems can already process TCF v2.3 strings.
Valid TCF v2.2 strings created before February 28, 2026 will still be accepted.
Systems can process both 2.2 and 2.3 during transition.
But going forward, new strings must include the disclosedVendors segment.
Why this matters beyond “technical compliance”
Consent infrastructure is no longer just a legal checkbox.
It directly affects:
campaign delivery
audience eligibility
programmatic performance
cross-platform activation
If your CMP migration is delayed, your media operations could be impacted.
𝗔𝗰𝘁𝗶𝗼𝗻 𝘀𝘁𝗲𝗽
If you haven’t already:
✔ Contact your CMP
✔ Confirm their TCF v2.3 migration timeline
✔ Ensure vendor IDs are properly configured
✔ Avoid last-minute compliance stress
Privacy regulation isn’t slowing down.
It’s becoming more structured.

Better to prepare early than troubleshoot in Q1 2026.

Are you already planning your TCF v2.3 migration — or is this the first time you’re hearing about it?