English
Deutsch
PolskiA TC string from the euconsent-v2 cookie or from the __tcfapi response is decoded here bit by bit, inside this browser. Nothing is sent anywhere.
TCF v2.2 Consent String Decoder
Articles that explain this
- TCF 2.3 Disclosed Vendors Segment: What It Contains and How to Read It From a TC String Data Privacy
- Reading a TC String: What Sits in the 213 Header Bits Data Privacy
- TCF Feature 3: When Google May Use the IP Address to Identify a Device Data Privacy
- TCF Explained: What It Is, Why It Matters and Which CMPs Are Certified Data Privacy
OTHER TOOLS
- Consent Mode v2 Decoder
- Tracking and Consent Scanner for a Live Page
- Usercentrics DataLayer Event Simulator
- GA4 gcd Parameter Decoder
- Email Tracking Pixel and Remote Content Auditor
- GA4 PII Checker
- Connection Mirror: What the Server Sees
- Privacy Sandbox and Fingerprint Surface Detector
- Shop vs. GA4 Revenue Reconciliation
- GA4 Property Configuration & Snapshot Comparator
RELATED ARTICLES
- TCF 2.3 Disclosed Vendors Segment: What It Contains and How to Read It From a TC String
- Reading a TC String: What Sits in the 213 Header Bits
- TCF Explained: What It Is, Why It Matters and Which CMPs Are Certified
- TCF Feature 3: When Google May Use the IP Address to Identify a Device
- How to Implement Google Consent Mode v2
- How Cookieless Pings Work in Google Consent Mode
- Microsoft Ads Consent Mode: Implementation via JavaScript and GTM, Differences From Google
- Tutorial: Configuring Geolocation Rules in Usercentrics
- GA4 Consent Mode v2: The gcd Parameter, CMP Race Conditions and Server-Side Debugging
- Germany’s Consent Management Regulation: What a Recognised Service Must Do and What Stays Voluntary