IAB TCF consent string
A coded record of which ad vendors and purposes the person agreed to in the EU consent banner.
In one line
Can see which ad vendors you agreed to in the EU cookie banner
A coded record of which ad vendors and purposes the person agreed to in the EU consent banner.
Stored in the euconsent-v2 cookie and read through __tcfapi. TCF v2.3 requires the disclosedVendors segment, and strings without it were invalid from Feb 28 2026. Consent is valid for up to 13 months.
What it can and can't do
What the user does: You tap Accept, Reject, or Manage choices on a cookie banner
It can
- Check which ad vendors and purposes you said yes to
- Pass your choices along to the ad partners it works with
- Remember your answer for up to 13 months
- Show the banner again if the record is missing or out of date
It cannot
- Count a choice you never made as your consent
- Use a record that lacks the vendor list; since Feb 28 2026 those strings are invalid
- Keep your choices past 13 months without asking again
- Tell vendors you agreed when you picked Reject all
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | :Cookie and JS API, any browser |
| Edge | Supported | 1 | Not listed | :Cookie and JS API, any browser |
| Firefox | Supported | 1 | 2004-11-09 | :Cookie and JS API, any browser |
| Safari | Supported | 1 | 2003-06-23 | :Cookie and JS API, any browser |
| Safari on iPhone | Supported | 1 | 2007-06-29 | :Cookie and JS API, any browser |
| Chrome on Android | Supported | 1 | Not listed | :Cookie and JS API, any browser |
| Samsung Internet | Supported | 1 | 2013-04-27 | :Cookie and JS API, any browser |
How a site asks for it
| API | window.__tcfapi('getTCData', 2, cb); euconsent-v2 cookie |
| How access is granted | prompt |
| What the user sees | CMP cookie banner |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | euconsent-v2 cookie up to 13 months |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Consent string
Shape: string
How often: per consent change
No individual data fields. The signal is the access itself.
Technical limits
- Covers 11 purposes and 3 special purposes plus vendor IDs
- Needs a registered CMP
- Not a legal proof by itself
The story
What it is
A saved note of which ad companies and purposes you said yes or no to on a cookie banner.
For you
You see it as the cookie banner in Europe, with a button to accept, reject or manage choices. After you tap, the site stores a coded note of your answers. Ad companies on the page read that note instead of asking you again.
For makers
Publishers and ad vendors need proof that a person agreed before personal data is used for ads. The string travels with every ad request, so each buyer knows what it may do. It also keeps a paper trail for regulators.
Where you see it
| Type | Example | Apps |
|---|---|---|
| news | A European newspaper shows a banner, then passes your choices to every ad vendor on the page so only allowed ones load. | The Guardian |
| ads | In a real-time ad auction, the exchange reads the string first and drops bidders that were not approved. | Google Ad Manager, Prebid |
| games | A free browser games portal shows a consent banner on first visit and only runs personalised ads between rounds if you agreed. | Poki, CrazyGames |
| video | A streaming site plays a generic pre-roll ad instead of a targeted one when you reject the banner. | None named |
| analytics | A measurement tag waits for the consent note before it fires, so rejected visitors are not counted individually. | Google Tag Manager |
| shopping | A web shop only loads retargeting pixels from vendors you ticked, so you do not see its ads follow you around. | None named |
| enterprise | A compliance team keeps logs of consent strings to show a regulator that a visitor really said yes. | None named |
Risks
- Banners with pushy design
- Consent claims that regulators have challenged
What the platform says
- IAB Europe: Transparency and Consent Framework. The industry standard that lets sites, ad vendors and consent banners share one record of what a person agreed to.
Good uses and abuse
Legitimate uses
- Documenting consent
Known abuse
- Weak consent flows (CNIL and Belgian DPA rulings on TCF)
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2020-08, all: TCF v2.0 launched
- 2023-05, all: TCF v2.2 removed legitimate interest for some purposes
- 2026-02, all: TCF v2.3 with disclosedVendors mandatory from Feb 28 2026
Related capabilities
Related
- Global Privacy Platform string. Can carry your privacy choices for US states and other regions to ad partners
- Global Privacy Control (GPC). Can tell every site that you opt out of sale and sharing of your data
Sources
How well checked: Based on official documentation.