Last updated: 9 November 2026.
TCF stands for the Transparency and Consent Framework, an industry standard run by IAB Europe. It gives websites, apps, consent management platforms (CMPs) and advertising technology vendors a common way to tell users how their data will be used for advertising, record their choices, and pass those choices along the ad supply chain. The current version is TCF v2.3.
Looking for the French language test? The TCF (Test de connaissance du français) is a French proficiency exam and has nothing to do with this framework. This page covers the advertising consent standard.
TCF at a glance
| Question | Answer |
|---|---|
| Who runs it? | IAB Europe sets the policies. IAB Tech Lab maintains the technical specifications |
| Current version | v2.3, released June 2025 and mandatory for new consent strings since 1 March 2026 |
| Who uses it? | Publishers and app developers, registered CMPs, and ad tech vendors serving EU, EEA and UK users |
| Main parts | Policies, registered CMPs, the Global Vendor List and the TC string |
| Legal status | A voluntary industry standard. Using it does not by itself make you GDPR compliant |
How TCF works
-
A registered CMP shows the consent banner. It lists the purposes data will be used for and the vendors that want to use it, taken from IAB Europe's Global Vendor List.
-
The user makes choices. They can accept, reject, or choose purpose by purpose and vendor by vendor, and object where a vendor relies on legitimate interest.
-
The CMP encodes the choices in a TC string. This is a compact, standardised text string stored on the user's device and made available to scripts on the page through the CMP's API.
-
Vendors read the TC string. Ad tech vendors receive it, for example in programmatic ad requests, and should only process data for the purposes and legal bases the user allowed.
The key components
-
Policies: the rules every participant agrees to follow, including how purposes must be described and how CMPs must present choices.
-
Registered CMPs: consent tools that IAB Europe has validated to generate TC strings. Only registered CMPs can take part.
-
Global Vendor List (GVL): the public list of registered vendors, with the purposes each one uses, the legal basis it relies on and how long it stores data.
-
Purposes and features: standard definitions, such as storing information on a device, building a profile for personalised ads or measuring ad performance, so every CMP describes them the same way.
-
The TC string: the encoded record of the user's choices. Under v2.3 it has a core segment, a mandatory disclosed vendors segment listing the vendors actually shown to the user, and an optional publisher segment.
TCF versions
| Version | When | Main changes |
|---|---|---|
| v1 | 2018 | First version, launched around the start of the GDPR |
| v2.0 | 2020 | More purposes, support for legitimate interest and the right to object, and publisher controls over vendors |
| v2.2 | 2023 | Legitimate interest removed as a basis for personalised advertising and content, plainer purpose descriptions, and the number of vendors shown on the first layer |
| v2.3 | Released 19 June 2025, mandatory from 1 March 2026 | The disclosed vendors segment becomes mandatory, so vendors can tell whether they were actually shown to the user |
TC strings created before 28 February 2026 without the disclosed vendors segment remain valid. Strings created after that date without it are treated as invalid, and CMPs did not need to show the banner again just for the move to v2.3.
Is TCF GDPR compliant?
TCF has been tested in the courts, and the answer is that it can be used lawfully, but participants carry real GDPR responsibility for it:
-
February 2022: Belgium's data protection authority found that the framework breached the GDPR, fined IAB Europe €250,000 and ordered changes.
-
7 March 2024: the EU Court of Justice ruled (case C-604/22) that a TC string can be personal data when it can be linked to a person, for example through an IP address, and that a standard-setting body like IAB Europe can be a joint controller.
-
14 May 2025: the Belgian Market Court upheld the fine. It confirmed that the TC string is personal data and that IAB Europe is a joint controller for processing TC strings within the framework, but not for the downstream ad processing that happens under the OpenRTB protocol.
-
7 January 2026: the same court annulled the Belgian authority's 2023 approval of IAB Europe's remedial action plan, so the authority has to decide on it again.
For publishers and vendors, the practical point is that TCF is a tool, not a safe harbour. You are still responsible for having a valid legal basis, collecting genuine consent and respecting users' choices in your own processing.
Do you need TCF?
You will usually need TCF if you show programmatic or third-party advertising to users in the EEA, the UK or Switzerland. Google, for example, requires publishers using its advertising products for those users to use a Google-certified CMP that integrates with the TCF.
If your site doesn't run third-party ads, you usually don't need TCF. You still need consent for non-essential cookies, but a standard cookie consent banner is enough. If you use Google Analytics or Google Ads, also look at Google Consent Mode v2, which tells Google's tags what the user chose and works alongside a consent banner with or without TCF.
How to implement TCF as a publisher
-
Choose a registered CMP that supports v2.3, and check it is Google-certified if you use Google's ad products.
-
List only the vendors you actually work with. Showing hundreds of vendors you don't use makes consent less meaningful and the banner harder to use.
-
Set publisher restrictions if you want to limit which purposes or legal bases vendors can use on your site.
-
Design the banner fairly. Make rejecting as easy as accepting and avoid pre-ticked boxes. Regulators treat manipulative designs as dark patterns.
-
Check the TC string. Decode a string from your live site with IAB Europe's tools and confirm the disclosed vendors segment is present.
-
Check what loads before consent. ComplyDog's free cookie checker scans any page and lists the cookies set on load and the third-party services contacted, so you can confirm ad tags wait for a choice.
What vendors must do
-
register on the Global Vendor List and declare their purposes, legal bases and storage periods accurately,
-
read the TC string on every request and only process data the user has allowed,
-
act on the disclosed vendors segment, especially when relying on legitimate interest, and
-
pass consent signals on correctly to their own partners.
TCF and the Digital Omnibus
The EU's proposed Digital Omnibus would change the cookie rules, adding consent exemptions for some low-risk uses and requiring a single-click option to refuse. Consent would still be needed for advertising, so TCF is likely to remain the main way the ad industry handles it. The proposal is still being negotiated and nothing has changed yet. See our guide to the ePrivacy Directive for the rules that apply today.
FAQ
What does TCF stand for?
In privacy and advertising, TCF stands for the Transparency and Consent Framework, IAB Europe's standard for collecting and passing on users' advertising consent choices. The same letters are also used for the Test de connaissance du français, a French language exam.
Is TCF mandatory?
No law requires TCF. It is an industry standard, but in practice publishers that show programmatic ads to EEA and UK users often need it, because ad partners such as Google require a TCF-integrated CMP.
What is a TC string?
A TC string is the encoded record of a user's choices under TCF. It tells vendors which purposes and vendors the user allowed. Courts have confirmed it can be personal data.
What is the latest version of TCF?
TCF v2.3, released in June 2025. Its disclosed vendors segment has been mandatory for new TC strings since 1 March 2026.
Is TCF the same as Google Consent Mode?
No. TCF is an industry-wide framework for passing consent signals to many ad tech vendors. Google Consent Mode tells Google's own tags how to behave based on the user's choice. Many sites use both.