Consent Mode checker
Test the Google Consent Mode v2 signals on a page.
TCF string decoder
Read any TC string.
Paste a Transparency and Consent Framework (TCF) string to see what it records: the purposes and special features, each vendor's consent and legitimate interest, and any publisher restrictions.
- TCF v2.0, v2.2 and v2.3
- Vendor names from the IAB Global Vendor List
- Decoded in your browser
Free, no account needed
How TCF works
One string, every choice.
The IAB Transparency and Consent Framework stores a visitor's consent and legitimate interest choices in a compact string that advertising vendors read.
The core segment
The consent platform, the dates, the consent language, the policy version and the vendors' consent and legitimate interest bits.
Purposes and vendors
11 standard purposes, 2 special features, and a consent and a legitimate interest bit for each vendor on the IAB Global Vendor List.
The other segments
Disclosed vendors (required in v2.3), allowed vendors (retired) and the publisher segment with the publisher's own purposes.
Reference
The TCF purposes and special features.
The 11 standard purposes and 2 special features the framework defines.
| ID | Name | Description |
|---|---|---|
| 1 | Store and/or access information on a device | Cookies, device identifiers or similar online identifiers can be stored or accessed on your device for the purposes presented to you. |
| 2 | Select basic ads | Ads can be shown to you based on the content you're viewing, the app you're using, your approximate location or your device type. |
| 3 | Create a personalised ads profile | A profile can be built about you and your interests to show personalised ads that are relevant to you. |
| 4 | Select personalised ads | Personalised ads can be shown to you based on a profile about you. |
| 5 | Create a personalised content profile | A profile can be built about you and your interests to show personalised content that is relevant to you. |
| 6 | Select personalised content | Personalised content can be shown to you based on a profile about you. |
| 7 | Measure ad performance | The performance and effectiveness of ads you see or interact with can be measured. |
| 8 | Measure content performance | The performance and effectiveness of content you see or interact with can be measured. |
| 9 | Apply market research to generate audience insights | Market research can be used to learn more about the audiences who visit sites and apps and view ads. |
| 10 | Develop and improve products | Your data can be used to improve existing systems and software, and to develop new products. |
| 11 | Use limited data to select content | Content can be selected based on limited data, such as the content you're viewing or your device type. |
| ID | Name | Description |
|---|---|---|
| 1 | Use precise geolocation data | Your precise geolocation data can be used in support of one or more purposes. |
| 2 | Actively scan device characteristics for identification | Your device can be identified based on a scan of its unique combination of characteristics. |
How it works
Decoded where you paste it.
The string is read in your browser. Only the vendor list version it names is requested, to show vendor names.
-
Step 1: Paste a TC string
Copy it from the euconsent-v2 cookie, your consent platform's API or an ad request. -
Step 2: It is decoded in your browser
JavaScript on this page reads the string's bits. The string is never sent to Kukie.io, logged or stored. -
Step 3: Read the breakdown
Purposes, special features, vendors, legitimate interests and publisher restrictions, each with its state in words.
Questions about TC strings
What is a TC string?
A Transparency and Consent (TC) string is a compact, base64url-encoded record defined by IAB Europe's Transparency and Consent Framework. It stores a visitor's consent and legitimate interest choices for data processing purposes and advertising vendors. A consent platform that is registered with the framework writes it when the visitor answers its banner.
What is the difference between TCF v2.0, v2.2 and v2.3?
TCF v2.0 was the first version 2 release, with 10 purposes and vendor consent. Version 2.2 added purpose 11 ("Use limited data to select content"), tightened the rules for legitimate interest and added the useNonStandardTexts field. Version 2.3, required from February 2026, makes the disclosed vendors segment mandatory, so a vendor can check that it was shown to the visitor.
What are the segments in a TC string?
Up to four, separated by dots: the core segment (always present) with the purposes and the vendors' consent and legitimate interest, the disclosed vendors segment listing the vendors the consent platform showed, the allowed vendors segment (retired in v2.3) and the publisher segment with the publisher's own purposes.
What is the disclosed vendors segment?
A bitfield of the vendors the consent platform showed to the visitor. In TCF v2.3 it is mandatory, and a vendor checks that its ID is set there before it processes personal data, even under legitimate interest.
How do I find the TC string on my website?
Open your browser's developer console on the page and run __tcfapi('getTCData', 2, function (data) { console.log(data.tcString); }), or read the value of the euconsent-v2 cookie. Ad requests also carry it in the gdpr_consent parameter.
What does the decoder show?
Everything the string records: the TCF version, the consent platform, the dates, the consent language, the 11 purposes with their consent and legitimate interest, the 2 special features, every vendor's consent and legitimate interest (with names from the IAB Global Vendor List), publisher restrictions, the disclosed vendors and the publisher segment.
More free tools
Check the rest of the consent setup.
The other free tools look at what a page does before and after a visitor chooses.
Script audit
See every third-party script a page loads before the visitor chooses.
Amazon Consent Signal
How Kukie.io passes consent to Amazon Ads without a TC string.
Manage consent on your own website.
Kukie.io shows a consent banner, holds back known trackers until visitors agree and records every choice. It does not generate TC strings.
Disclaimer
Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.
