English
Deutsch
PolskiSave tool
A 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: Which Advertising Providers a Cookie Banner Discloses and How to Check Data Privacy
- Reading Stored Cookie Consent Choices: Understanding the TC String Data Privacy
- TCF Feature 3: When Google May Use the IP Address to Identify a Device Data Privacy
- TCF Explained: How Cookie Banners Pass Consent Choices to Advertising Services 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
- GTM Container Cleanup Checker: Orphaned Tags, Triggers and Variables
- SaaS Support Capacity Planner
Related articles
- TCF 2.3: Which Advertising Providers a Cookie Banner Discloses and How to Check
- TCF Explained: How Cookie Banners Pass Consent Choices to Advertising Services
- TCF Feature 3: When Google May Use the IP Address to Identify a Device
- Reading Stored Cookie Consent Choices: Understanding the TC String
- How to Implement Google Consent Mode v2
- Google Consent Mode: What Data Is Sent When Cookies Are Rejected
- Controlling Cookie Consent for Microsoft Ads: Consent Mode with JavaScript and GTM
- Showing Different Cookie Banners by Country: Setting Up Regional Rules in Usercentrics
- Analytics 2027: What the EU Cookie Reform Means Technically for Web Tracking
- Reporting Advertising Conversions from the Server with Floodlight: Checking Consent and Attribution