IAB TCF Consent Decoder
Paste a TC string (or a URL with gdpr_consent=, a cookie, a bid request with user.consent, or a GPP string — it is extracted automatically) to see CMP metadata and CMP name, purpose consents and legitimate interests, special features, publisher restrictions, disclosed / allowed / publisher segments and staleness warnings. Load the Global Vendor List for the exact vendorListVersion to get vendor names, declared legal bases, "consented but not in GVL" flags, a per-vendor explanation of what is allowed, and a purpose × vendor matrix (C / LI / R) with CSV export. Parse addtl_consent (Google ATP) strings and re-encode edited purposes, special features and vendors with TCString.encode.
- CMP
- id 7 (load the vendor list to resolve the name)
- CMP version
- 3
- Consent screen
- 1
- UI language
- EN
- Publisher country
- DE
- Scope
- service-specific (publisher)
- Created
- 2026-09-01 00:00 UTC · 17 days ago
- Last updated
- 2026-09-10 00:00 UTC
- TC string version
- 2
- Vendor list version
- v177
- Policy version
- 5
- Purpose-1 treatment
- no
- Non-standard texts
- no
- Out-of-band signalling
- not supported
- Custom purposes
- 0
- Segments
- core · disclosed vendors · publisher TC
Related tools
IAB GPP Decoder
Decode and edit Global Privacy Platform strings — US National and state sections with plain-English legends, TCF EU, gpp_sid checks.
OpenRTB Inspector
Validate & annotate OpenRTB 2.6 BidRequest and BidResponse JSON.
sellers.json Inspector
Fetch any exchange's sellers.json by domain, validate it against the IAB spec, cross-check a publisher's ads.txt against it, and resolve OpenRTB supply chains.
ads.txt / app-ads.txt Validator
Fetch any domain's ads.txt or app-ads.txt, validate it against the IAB 1.1 spec, follow SUBDOMAIN pointers, and cross-check every line against exchange sellers.json files.
How to use IAB TCF Consent Decoder
- 1Paste the TC string — or a whole ad-request URL, cookie string, GPP string or OpenRTB bid request; the consent string is extracted automatically.
- 2Read the Overview for CMP, GVL and policy versions, scope, creation date and any validity or staleness warnings.
- 3Click "Load vendor list" (or enable auto-load) to fetch the exact GVL version through the relay and resolve vendor names and declared purposes.
- 4Use the Vendors tab to search by name or paste ids like "32, 755, 91", and click a vendor for a per-purpose explanation of what it may process.
- 5Open the Matrix tab for the purpose × vendor grid (C / LI / R), filter by vendor and export CSV; use the Editor to toggle signals and copy a re-encoded string.
About IAB TCF Consent Decoder
Paste a TC string (or a URL with gdpr_consent=, a cookie, a bid request with user.consent, or a GPP string — it is extracted automatically) to see CMP metadata and CMP name, purpose consents and legitimate interests, special features, publisher restrictions, disclosed / allowed / publisher segments and staleness warnings. Load the Global Vendor List for the exact vendorListVersion to get vendor names, declared legal bases, "consented but not in GVL" flags, a per-vendor explanation of what is allowed, and a purpose × vendor matrix (C / LI / R) with CSV export. Parse addtl_consent (Google ATP) strings and re-encode edited purposes, special features and vendors with TCString.encode.
IAB TCF Consent Decoder is part of FizzKit — a collection of focused developer and ad-tech tools. This tool uses the FizzKit relay to fetch public URLs on your behalf (so browser CORS rules do not get in the way); fetched content is returned to your browser and not stored.