> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/releases-and-announcements/migrations/iab-tcf-2.4-migration.md). # 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](#iab-tcf-2.4-updates) * [Deadlines and rollout ](#deadlines-and-rollout) * [Migrate to IAB TCF 2.4 (web)](#migrate-to-iab-tcf-2.4-web) ### 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:

Requirement Description

Mandatory

Requirement	Description
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.`

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.

{% hint style="info" %} **IAB TCF resources** Visit the links below for official communication from the IAB regarding TCF 2.4: * [IAB Tech Lab announcement](https://iabtechlab.com/updates-to-tcf-to-support-policy-version-5-0-b-are-open-for-public-comment/) {% endhint %} ### Deadlines and rollout Review the table below for deadlines and rollout plans per consent notice type for IAB TCF 2.4:

Consent notice	Compliance Deadline	Rollout
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) {% hint style="warning" %} **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. {% endhint %} 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.

{% hint style="info" %} Between October 6th and October 21st, your organization can freely switch a consent notice between IAB TCF 2.3 and IAB TCF 2.4. {% endhint %} Click **Save** when finished.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.didomi.io/releases-and-announcements/migrations/iab-tcf-2.4-migration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.