IAB TCF 2.4 migration
In this article, we will cover upcoming changes to the Didomi Consent Management Platform to support the IAB TCF 2.4 framework.
IAB TCF 2.4 updates
The update to IAB TCF 2.4 introduces the following updates for organizations who utilize the framework in their consent notices:
Mandatory
Introduce standard text to IAB features that helps the end-user understand how the feature differs from purposes and why they do not offer end-user controls. IAB features are the following:
Match and combine offline data sources
Link different devices
Receive and use automatically-sent device characteristics for identification
The standard text for features are pulled directly from the IAB Global Vendor List (GVL) and cannot be edited by your organization.
Mandatory
The IAB special feature Actively scan device characteristics for identification will be renamed to Identify devices based on information actively requested.
Optional
Vendors declaring only special purposes may be removed from the vendor legitimate interest section of the tcString, as their disclosure is already communicated through the mandatory disclosed vendors section introduced in TCF v2.3.
Note: Didomi will not be implementing this change and vendors who are only declaring special purposes will still be populated in the vendor legitimate interest section and disclosed vendors section of the tcString.
Deadlines and rollout
Review the table below for deadlines and rollout plans per consent notice type for IAB TCF 2.4:
Web
October 23, 2026
Starting October 6th, your organization can begin migrating web consent notices manually. On October 21st Didomi will automatically migrate all consent notices to IAB TCF 2.4 to ensure compliance ahead of the deadline.
Mobile / CTV
February 23, 2027
Organizations can begin migrating mobile and CTV consent notices around the end of October.
Migrate to IAB TCF 2.4 (web)
Note: All new and existing consent notices will default to IAB TCF 2.4 on October 21, 2026. Prior to this date, your organization can migrate between IAB TCF 2.3 and IAB TCF 2.4.
In order to migrate an existing consent notice to IAB TCF 2.4, click Consent notices on the left-hand panel.
Navigate to a consent notice that has the IAB TCF enabled on the list and click the Edit icon inline with the consent notice name.
Select the Customization and click the Integrations sub-tab.
Navigate to the Advertising tab on the subsequent page and expand the IAB Transparency & Consent framework accordion.
Select the TCF Version 2.4 radio button in the IAB TCF accordion.
Click Save when finished.
Last updated