IAB TCF v2.3 for publishers: what Google requires, what changed from v2.2, and v2.4
Key takeaways
- The IAB Europe Transparency and Consent Framework (TCF) is a voluntary industry standard that lets a CMP record users' choices per purpose and per vendor in a TC string that ad tech vendors such as Google read.
- TCF v2.2 (May 2023) removed legitimate interest as a legal basis for Purposes 3 to 6 and deprecated the getTCData API command.
- TCF v2.3 made the Disclosed Vendors segment mandatory; Google states it is mandatory for all TC strings generated on or after March 1, 2026.
- TCF Specifications v2.4 were published on 23 July 2026, with a deadline of 23 October 2026 for CMPs to implement the new disclosures on websites.
- Google serves personalized ads only with consent for Purposes 1, 3 and 4, plus consent or legitimate interest for Purposes 2, 7, 9 and 10.

The IAB Europe Transparency and Consent Framework (TCF) is the standard your consent banner uses to tell Google and other ad vendors what each visitor accepted. The CMP shows standardized purposes, records the answers in a TC string, and AdSense reads that string on every ad request. Since March 1, 2026, Google requires TCF v2.3 for every TC string generated on or after that date; older v2.2 strings stay accepted. The v2.4 specification (July 2026) adds disclosure changes for CMPs on top of v2.3.
This page was first written around v2.2, which is why its address still says “v2.2”; the content covers the rules in force in November 2026. Below is what you need as a publisher, not as a CMP developer.
What is the TCF, and who does what?
IAB Europe describes the TCF as “an accountability tool that relies on standardisation to facilitate compliance with certain provisions of the ePrivacy Directive and the GDPR”. It is voluntary and has three types of participants:
| Participant | Role | Example |
|---|---|---|
| Publisher | Runs the site, chooses vendors and purposes, shows the CMP | You |
| CMP | Displays the notice, records choices, writes the TC string, exposes the __tcfapi JavaScript API |
Google’s Privacy & messaging, Didomi, Cookiebot |
| Vendor | Reads the TC string and acts accordingly | Google Advertising Products (ID 755) |
Vendors declare their purposes and legal bases in the Global Vendor List (GVL), which CMPs download from IAB Europe. The technical specifications are maintained by IAB Tech Lab on GitHub under a Creative Commons Attribution 3.0 licence.
Which purposes does the TCF define?
The TCF Policies (Appendix A) define 11 purposes, 3 special purposes, 3 features and 2 special features. Names below are the current standard names.
| ID | Name | Allowed legal basis |
|---|---|---|
| Purpose 1 | Store and/or access information on a device | Consent |
| Purpose 2 | Use limited data to select advertising | Consent or legitimate interest |
| Purpose 3 | Create profiles for personalised advertising | Consent |
| Purpose 4 | Use profiles to select personalised advertising | Consent |
| Purpose 5 | Create profiles to personalise content | Consent |
| Purpose 6 | Use profiles to select personalised content | Consent |
| Purpose 7 | Measure advertising performance | Consent or legitimate interest |
| Purpose 8 | Measure content performance | Consent or legitimate interest |
| Purpose 9 | Understand audiences through statistics or combinations of data from different sources | Consent or legitimate interest |
| Purpose 10 | Develop and improve services | Consent or legitimate interest |
| Purpose 11 | Use limited data to select content | Consent or legitimate interest |
| Special Purpose 1 | Ensure security, prevent and detect fraud, and fix errors | Legitimate interest, no right to object via the TCF |
| Special Purpose 2 | Deliver and present advertising and content | Legitimate interest, no right to object via the TCF |
| Special Purpose 3 | Save and communicate privacy choices | Legitimate interest, no right to object via the TCF |
Features (matching data sources, linking devices, identifying devices from automatically transmitted information) are disclosed but not chosen. Special Features 1 (precise geolocation) and 2 (identifying devices based on actively requested information) need an explicit opt-in.
What does Google need from the TC string?
Google’s publisher TCF integration article sets the thresholds:
| Serving mode | Consent required for Google | Consent or legitimate interest required |
|---|---|---|
| Personalized ads | Purposes 1, 3 and 4 | Purposes 2, 7, 9 and 10 |
| Non-personalized ads | Purpose 1 | Purposes 2, 7, 9 and 10 |
| Limited ads | None | Transparency for Special Purposes 1 and 2, and Google as a vendor |
Google registered Purposes 2, 7, 9 and 10 as “flexible”, defaulting to legitimate interest. If you configure a publisher restriction requiring consent for them, Google uses consent instead. Google is not flexible on Purposes 1, 3 and 4: they always need consent. Google also states that if you do not have consent for Purpose 1, “you should not call Google’s ad tag”. The limited and non-personalized ads guide explains what each mode does with data.
What is inside a TC string?
A TC string is a base64url-encoded bit field. Since v2.3 the specification says it “must contain a Core TC String and the Disclosed Vendors segment” and may contain a Publisher TC segment, joined by dots:
[Core String].[Disclosed Vendors].[Publisher TC]
- Core string: CMP ID, GVL version, policy version, consent and legitimate-interest bits per purpose and per vendor, special feature opt-ins, publisher restrictions, publisher country code.
- Disclosed Vendors: one bit per vendor, 1 if the vendor was shown to the user. Mandatory since v2.3.
- Publisher TC: your own purposes, if you request consent for your first-party use of data.
The specification leaves storage to the CMP (“including any non-cookie storage mechanism”). Scripts on the page read the string through the CMP API, not by parsing cookies. All CMPs must support three commands: ping, addEventListener and removeEventListener. The older getTCData command was deprecated in v2.2.
What changed from v2.2 to v2.3, and what does v2.4 add?
| Version | Date | Main changes for publishers |
|---|---|---|
| v2.0 | Launched 21 August 2019 | New Framework Policies and specifications (the “v2” structure still used today) |
| v2.1 | Launched 19 August 2020 | Cookie duration disclosures (Planet49 ruling) |
| v2.2 | Launched 16 May 2023 | Revised purpose names and descriptions, retention periods for all purposes, legitimate interest removed for Purposes 3 to 6, data categories, number of vendors on the first layer, getTCData deprecated |
| v2.3 | Dated April 2025 in the specification | Disclosed Vendors segment made mandatory to resolve the legitimate-interest ambiguity for special purposes; transition until 28 February 2026 |
| v2.4 | Specifications published 23 July 2026 | New standardTexts field in the GVL with a standard Features explanation, illustrations for each Feature, new name for Special Feature 2; web deadline 23 October 2026, apps and CTV 23 February 2027 |
IAB Europe’s transition article explains the v2.3 problem: under v2.2, a vendor declaring special purposes and purposes under legitimate interest could not tell whether it “was not disclosed in the CMP UI” or “the user had objected”. The Disclosed Vendors bit removes the doubt. Strings created before 28 February 2026 without the segment stay valid; strings created after it without the segment are invalid.
What are Google’s v2.3 dates?
Google’s publisher TCF integration article set out the transition:
| Phase | Dates | What Google does |
|---|---|---|
| Support live | From Google’s announcement | Accepts and processes v2.3 strings |
| Transition period | Until the end of February 2026 | Treats v2.3 strings like v2.2 strings and does not validate the Disclosed Vendors segment |
| Final deadline | March 1, 2026 onward | “TCF v2.3 is mandatory for all TC strings generated on or after March 1, 2026”; new v2.2 strings are no longer supported |
| Older strings | Created before March 1, 2026 | v2.2 strings still supported |
A string that misses the requirement “may cause the associated ad request to be defaulted to Limited Ads”, which Google warns may impact revenue. Google’s troubleshooting article reports such cases as error 1.4, when the Disclosed Vendors segment is “missing, malformed, or does not include Google”. That article words the cut-off slightly differently, accepting v2.1 and v2.2 strings “generated before February 28, 2026”; the practical meaning is the same.
For publishers, Google’s instructions were short: if you use Google’s own CMP, “no action is required”, since Google writes v2.3 strings; if you use another CMP, confirm with the vendor that your properties run its v2.3-compliant version.
What must the first layer of the banner show?
The TCF Policies (Appendix B) list what the initial layer must include when a CMP uses a layered design. Among them:
- that information is stored on or accessed from the device, and that personal data is processed (with the nature of the data);
- that third-party vendors are involved, the number of vendors, and a link to the named list;
- the list of purposes using the standard names or stack names, and the special features used;
- the scope of consent (service-specific, group-specific or multi-device);
- that consent can be withdrawn at any time and how to reopen the CMP;
- a call to action to consent and a call to action to customise choices.
Calls to action must have matching text treatment and a contrast ratio of at least 5 to 1 for the two primary buttons. Users must be able to reopen the CMP from an easily accessible link or icon, such as a footer link. IAB Europe also warns that disclosing “an unjustifiably large number of Vendors” may impact users’ understanding, so trim vendors you do not use.
Where does Google’s Additional Consent fit?
Some ad tech providers on Google’s own Ad Technology Providers list are not registered in the TCF. Google’s Additional Consent (AC) specification carries consent for them in a separate AC string next to the TC string. Google’s own European regulations message supports it, and Google checks it during certification for CMPs that support it. If you only use AdSense with Google demand, you rarely need to think about it, but a broken AC string (errors 8.1 and 8.2) means no additional vendors are considered.
Common mistakes
- Running an old CMP script. Self-hosted copies of a CMP do not get v2.3 or v2.4 updates. Use the vendor’s current script.
- Removing Google from the vendor list to “shorten” the banner. That guarantees error 1.1 for every user.
- Setting Purpose 2 to consent-only without knowing it. It is allowed, but users who refuse it lose non-personalized ads too.
- Calling
getTCDatain custom code. UseaddEventListener; Google’s troubleshooting page suggests CMPs return calls to it within 500 ms. - Mixing the TCF with Google Consent Mode. They are different signals; see Consent Mode v2 and AdSense.
For the broader map of IAB standards (ads.txt, sellers.json, GPP), see the IAB Tech Lab specifications reference. Nothing here is legal advice; the TCF is an industry framework, not a legal safe harbour.
Frequently asked questions
Is TCF v2.2 still accepted by Google?
Only for older strings. Google says it continues to accept TCF v2.1 and v2.2 strings generated before February 28, 2026, but TCF v2.3 is mandatory for all TC strings generated on or after March 1, 2026. A newer string without a valid Disclosed Vendors segment that includes Google is reported as error 1.4 and may fall back to limited ads.
What is Google's vendor ID in the TCF?
Google Advertising Products is vendor ID 755 on the IAB Europe Global Vendor List. Google's troubleshooting article asks publishers to make sure Google is included in the CMP's vendor configuration and receives consent and legitimate interest as required, because a missing or refused Google vendor entry produces error 1.1.
Do I, as a publisher, have to register with IAB Europe?
No. Publishers use the TCF through a registered CMP, which is responsible for generating valid TC strings. Only CMPs and vendors register. If you build your own CMP, it must be registered with IAB Europe and then certified by Google before your EEA, UK and Swiss traffic can receive personalized AdSense ads.
What does the TCF v2.4 update change for my site?
According to IAB Europe, v2.4 adds a standardTexts field to the Global Vendor List with a standard explanation for Features, adds illustrations for each Feature and renames Special Feature 2. CMPs had to show these disclosures on websites by 23 October 2026. If you use a maintained commercial CMP or Google's message, the update is handled by the vendor.
Sources
- TCF - Transparency & Consent Framework · IAB Europe
- IAB Europe Transparency & Consent Framework Policies · IAB Europe
- Transparency and Consent String with Global Vendor List Format (TCF v2 specification) · IAB Tech Lab
- All You Need to Know About the Transition to TCF v2.3 · IAB Europe
- TCF Policies v5.0.b and Specifications v2.4: confirmation of the timeline · IAB Europe
- Publisher integration with the IAB Europe TCF · Google AdSense Help
Related guides
- Google's certified CMP requirement: what AdSense publishers need for EEA, UK and Swiss traffic
Since 2024 AdSense needs a Google-certified TCF CMP for personalized ads in the EEA, UK and Switzerland. Dates, what happens without one, how to check yours.
- AdSense Privacy & messaging: building the European regulations (GDPR) message
Build the GDPR consent message in AdSense Privacy & messaging: every setting, the two- vs three-button layout, testing, troubleshooting and what it cannot do.
- Personalized, non-personalized and limited ads: the three AdSense serving modes compared
How AdSense picks personalized, non-personalized or limited ads from consent signals, what each mode still collects, the ad code switches and the setting to check.
- Consent mode v2 and AdSense: two consent signals, one site
Google consent mode v2 explained for AdSense sites: why AdSense reads the TCF string, not consent mode, and how to keep Analytics and AdSense signals aligned.
- IAB Tech Lab and IAB Europe specifications: what an AdSense publisher needs to know
Which industry specs matter to an AdSense publisher: ads.txt 1.1, sellers.json, SupplyChain, OpenRTB, TCF and GPP, with current versions and what each asks of you.