Key Takeaways
- IAB Europe's 2025 TCF Compliance Report found that consent management platforms supporting web, mobile, and connected TV simultaneously grew from just 4.8% to 6.6% of all registered CMPs during the year — meaning more than 93 in 100 registered CMPs still don't cover all three environments.
- IAB Tech Lab's TCF Policy v5.0.b amendments, released for public comment May 29, 2026, set a two-tier compliance deadline: mid-October 2026 for web, and mid-February 2027 for native app environments, which includes both mobile and CTV.
- The policy changes aren't cosmetic: CMPs must implement new multi-device consent handling aligned with CNIL guidance, display standardized feature-explanation text and illustrations in their UI, and support a renamed Special Feature 2.
- If your current CMP only added CTV support recently, or hasn't confirmed v5.0.b compliance at all, you're one deadline behind if you assumed "TCF support" already meant "CTV-ready."
- IAB Europe's April 2026 programmatic CTV guide counted only 18 CMPs validated for CTV against 466 vendors registered to support CTV environments on the Global Vendor List — a gap between vendors expecting CTV consent signals and platforms actually able to deliver them.
If you're running ads on a CTV app and assumed your CMP already handles TCF the same way it does on your website, check that assumption before mid-February 2027. The TCF Policy v5.0.b amendments arrived on May 29, 2026 with a compliance clock attached, and the honest state of the market is that most registered CMPs still don't fully support the environment your ad inventory increasingly depends on.
What TCF v5.0.b actually changes
IAB Europe and IAB Tech Lab published the v5.0.b policy amendments for public comment on May 29, 2026, moving the framework from version 5.0.a. The comment period closed a month later, on June 29, 2026, and the Global Vendor List and its translations were updated with new standard text and illustrations in mid-July 2026 to reflect the changes.
Three substantive changes are in this version, not a routine point release:
Multi-device consent handling. The amendments align TCF's multi-device consent model with guidance from France's CNIL, the data protection authority that has pushed hardest on cross-device tracking scrutiny in the EU. For CMPs and publishers running the same user across a phone, a laptop, and a CTV app, this changes how a consent choice made on one device should (and shouldn't) be inferred on another.
Standardized CMP UI requirements. Under v5.0.b, CMPs must display the standard feature-explanation text alongside each feature's standard name, plus the full standard user-friendly text, in their consent interface. This removes a legacy workaround some CMPs had been using and tightens what "showing" a feature to a user actually requires.
A renamed Special Feature 2. The amendments rename Special Feature 2 to "Identify devices based on information actively requested" and clarify its guidance. If your CMP configuration references this feature by its old name or description, that reference needs updating.
None of these changes are CTV-specific in isolation. What makes them a CTV story is the deadline structure attached to them.
The deadline that actually matters for CTV: mid-February 2027
TCF v5.0.b sets two compliance dates, not one, and the gap between them is the part easy to miss if you're only tracking "the TCF deadline" as a single line item:
| Environment | Deadline | What it covers |
|---|---|---|
| Web | Mid-October 2026 | Standard website CMP implementations |
| Native app (mobile & CTV) | Mid-February 2027 | Mobile apps and connected TV apps |
If your organization runs consent on a website and a CTV app, you have two separate deadlines to hit, not one. A publisher who gets their web CMP compliant by October and assumes the CTV side inherits that compliance automatically is wrong: native app environments, CTV included, get four additional months, but they are not exempt, and "additional time" is not the same as "already covered."
This distinction matters more for CTV specifically than for mobile, because of where the market actually stands.
Why the 6.6% number is the real story here
IAB Europe's 2025 TCF Compliance Report tracked how many registered CMPs support web, mobile, and CTV simultaneously, and found that share grew from 4.8% to 6.6% over the course of the year. That's real growth, roughly 38% relative increase, but it starts from a small base: even after that growth, fewer than 7 in 100 registered CMPs cover all three environments a modern publisher is likely to need.
IAB Europe's April 2026 programmatic CTV guide sharpens the picture further: only 18 CMPs are validated specifically for CTV, against 466 vendors on the Global Vendor List that are registered to operate in CTV environments. That's a wide gap between the number of ad-tech vendors expecting to receive a valid CTV consent signal and the number of CMPs actually built and validated to send one.
For a publisher, this gap translates into a concrete risk: if your current CMP hasn't been validated for CTV, or added CTV support only recently without confirming it against v5.0.b specifically, you may be assuming coverage that doesn't exist yet. Waiting until closer to February 2027 to find out is the expensive way to learn this.
How this connects to what CTV already makes hard
CTV consent has been a persistently underserved corner of the TCF ecosystem for reasons that predate v5.0.b, and the new deadline doesn't erase those existing constraints. Apple's tvOS imposes a 1MB UserDefaults storage limit that's often too small for a standard IAB vendor list, a constraint covered in more technical depth in our iOS vs. tvOS consent management comparison. Android TV, separately, has been subject to its own TCF v2.2 CTV enforcement track since mid-2024, distinct from the mobile Android enforcement timeline, as detailed in our Android TV vs. mobile consent guide.
Those platform-specific constraints don't go away under v5.0.b. What changes is that a CMP now also has to prove, by a specific date, that it handles the new multi-device consent model and UI requirements correctly inside those same constrained environments. A CMP that has been quietly under-resourcing its CTV implementation to work around the tvOS storage ceiling or the separate Android TV enforcement track now has a second, independent deadline forcing the issue.
A vendor-evaluation checklist for CTV publishers
If you publish to a CTV app and are trying to decide whether your current setup is actually ready, work through this before assuming yes:
- Confirm CTV validation status directly, not by inference. A CMP supporting "TCF" generally is not the same claim as a CMP validated for CTV specifically. Ask for the validation status, not a general compliance statement.
- Check whether your vendor has committed to a v5.0.b timeline. The policy comment period closed June 29, 2026; any CMP serious about the February 2027 deadline should already have an internal timeline for the multi-device consent, UI text, and Special Feature 2 changes.
- Ask what happens to your existing CTV consent configuration during the transition. Multi-device consent handling changes could affect how consent choices carry (or don't carry) across a user's devices, which is a functional change, not just a policy footnote.
- Weigh switching cost against waiting cost. With only 18 CMPs currently validated for CTV against 466 registered CTV vendors, publishers who wait until late 2026 to evaluate alternatives may find fewer validated options moving quickly, not more.
- Verify your storage and enforcement constraints are still respected. Confirm your CMP's v5.0.b implementation still fits inside tvOS's storage limits and still tracks Android TV's separate enforcement requirements, rather than solving the new policy requirements in a way that reintroduces an old platform-specific failure.
Publishers who've already implemented Secure Privacy's Cookie & Consent Solution get a structural advantage here: the platform's compliance scanner re-crawls cookies, trackers, and consent configuration on a monthly cycle and updates itself automatically as it detects changes, which is a materially different posture going into a policy deadline than a CMP that only gets checked when someone remembers to look. Consent collected across web, mobile, and custom flows also logs through the same universal consent management system, so a multi-device consent model change doesn't mean rebuilding separate logging per platform.
Frequently Asked Questions
What is TCF Policy v5.0.b?
TCF Policy v5.0.b is a set of amendments to the IAB Europe Transparency and Consent Framework, released for public comment on May 29, 2026. It introduces multi-device consent handling aligned with CNIL guidance, new standardized UI text and illustration requirements for CMPs, and a renamed Special Feature 2.
When do CMPs need to comply with TCF v5.0.b?
There are two deadlines. CMPs must comply in the web environment by mid-October 2026, and in native app environments, which includes both mobile and CTV, by mid-February 2027.
How many CMPs actually support CTV right now?
According to IAB Europe's 2025 TCF Compliance Report, only 6.6% of registered CMPs support web, mobile, and CTV simultaneously, up from 4.8% the year before. IAB Europe's April 2026 programmatic CTV guide separately found just 18 CMPs validated specifically for CTV, against 466 vendors registered to operate in CTV environments.
Does the mid-February 2027 deadline give CTV publishers more time than web publishers?
It gives a later deadline, not more safety margin. The four extra months exist because native app and CTV environments involve additional technical constraints, not because CTV compliance is a lower priority. Publishers still need to hit that date, and the current low rate of CTV-validated CMPs means many will be evaluating or switching platforms under time pressure if they wait.
If my CMP already supports TCF, does it automatically support CTV under v5.0.b?
Not necessarily. General TCF support and validated CTV support are different claims. Confirm your CMP's specific CTV validation status and its committed timeline for the v5.0.b multi-device consent and UI requirements, rather than assuming broad TCF compliance covers the CTV-specific deadline.
Why does CTV have separate technical challenges beyond TCF policy?
Apple's tvOS imposes a 1MB UserDefaults storage limit that often can't hold a standard IAB vendor list, and Android TV has followed its own separate TCF v2.2 CTV enforcement track since mid-2024, distinct from mobile Android's timeline. TCF v5.0.b's requirements apply on top of these existing platform constraints, not instead of them.
If your CTV consent setup hasn't been checked against the v5.0.b requirements yet, see how Secure Privacy's Cookie & Consent Solution handles multi-environment consent logging and monthly compliance re-scanning before the February 2027 deadline turns into a scramble.
