This article lists each IAB Europe Transparency & Consent Framework (TCF) update, what changed, and what you need to do. The current update is first. Older updates follow.
Current update
TCF v2.4:
IAB Europe published TCF v2.4 and an updated Global Vendor List (GVL) on July 23, 2026. Usercentrics supports TCF v2.4. TCF v2.4 introduces updates to the TCF user interface and terms:
TCF v2.4 updates the TCF user interface and terms. Each Feature now includes standard text and an IAB illustration. Special Feature 2 has been renamed to “Identify devices based on information actively requested.” Publishers can also keep users' consent choices across devices.
These changes do not affect the consent signal, CMP API, or existing consent strings. Users do not need to see the consent banner again.
What do I need to do?
For Web CMP (V2/V3), no action is required. TCF v2.4 is already supported.
For the Web SDK, update to version 4.64.0 before October 23, 2026. Older versions do not include the TCF v2.4 changes.
For Mobile and CTV SDKs, the deadline is February 23, 2027. We will provide a separate notice when the required release is available.
For more information, see the IAB Europe CMP & Vendor Notifications.
Previous updates
TCF v2.3:
TCF v2.3 introduced the required Disclosed Vendors segment in the Transparency & Consent (TC) string. The transition ended on February 28, 2026.
If you use our CMP for a website through script or API implementation:
No action required. Once released, all newly generated consent strings will automatically comply with TCF v2.3, including the Disclosed Vendors segment.
If you use our Browser SDK for a website:
You need to update your Browser SDK before February 28, 2026 to ensure all consent signals remain compliant. This SDK will be available on November 12, 2025.
If you use our CMP for a mobile application:
You need to update your App SDK to version 2.24.0 before February 28, 2026 to ensure all consent signals remain compliant. The updated SDK is already available for download:
Some customers have recently received communication from Microsoft regarding upcoming changes to IAB Europe’s Transparency & Consent Framework (TCF) v2.3 and the February 28, 2026 deadline. This article clarifies when action is required and what it means for your setup.
Microsoft TCF v2.3 notification – Do I need to take action?
Do I Need to Switch to TCF?
It depends on how you use Microsoft services.
You likely need TCF if you:
- Monetize website traffic through advertising (publisher model)
- Serve personalized ads to users in the EU/EEA/UK within ecosystems that require TCF consent signals
You likely do NOT need TCF if you:
- Use Microsoft Advertising only as an advertiser (running campaigns)
- Use Microsoft Clarity for analytics only
- Do not monetize website traffic through ad networks
If you use Microsoft Advertising as an advertiser and do not operate under TCF, we recommend enabling Microsoft Consent Mode (UET integration) in your CMP configuration. This ensures that consent signals are properly passed to Microsoft Advertising without requiring a TCF setup