Consent Cookie Inspector
Parse cookie strings for common consent and privacy signals such as euconsent-v2, addtl_consent, US Privacy, and GPP cookies so teams can see which consent artifacts are actually present.
See which consent cookies are actually present before you start debugging partner behavior.
What you can do here
- Audit cookies after a CMP rollout.
- Confirm whether a page is carrying euconsent-v2 or GPP.
- Review privacy signals before partner QA.
Before you start
- Paste a cookie string or cookie dump.
About Consent Cookie Inspector
The Consent Cookie Inspector parses cookie dumps or header strings and highlights common consent artifacts such as `euconsent-v2`, `addtl_consent`, US Privacy strings, and GPP cookies.
Use it when you need a fast answer to which privacy signals are present in a cookie string without manually scanning every pair.
Best uses for Consent Cookie Inspector
- Audit cookies after a CMP rollout.
- Confirm whether a page is carrying euconsent-v2 or GPP.
- Review privacy signals before partner QA.
How to use Consent Cookie Inspector
- Paste a cookie string or cookie dump.
- Review which known consent cookies were found.
- Use the summary to decide whether TCF, US Privacy, or GPP debugging comes next.
What to paste in
- Paste a cookie string or cookie dump.
What you should see
- Detected consent cookies and a short explanation of what each one represents.
Example checks
These are simple checks you can run when you want a real sample and a clear result to compare against.
Paste a cookie string or cookie dump.
Why run it: Audit cookies after a CMP rollout.
What to look for: Detected consent cookies and a short explanation of what each one represents.
Consent Cookie Audits Before Bidder and CMP Debugging
Why cookie presence is the right first question
Privacy debugging often becomes complicated before the team answers the simplest question. Which consent cookies are actually present? If `euconsent-v2`, GPP, US Privacy, or additional-consent cookies are missing or unexpected, every downstream bidder or CMP investigation starts from shaky assumptions.
A consent cookie inspector is useful because it turns a raw cookie string into a readable inventory of known privacy artifacts. That is often all teams need to decide which deeper decoder or runtime workflow comes next.
This is a different job from a full cookie-attribute audit. The focus is not on SameSite or Secure here. The focus is on which privacy signals exist at all.
How cookie inspection supports privacy tickets
During post-CMP reviews, partner QA, and region testing, the cookie layer is one of the fastest ways to anchor the investigation. If the expected privacy artifact is missing, that points to one class of problem. If it exists but carries a surprising value, that points to another.
That first-pass clarity reduces wasted effort. Instead of jumping straight into partner blame or runtime network traces, teams can establish the privacy-cookie baseline in minutes.
It also gives support and privacy teams a better handoff artifact. A cookie inventory is easier to share and easier to interpret than a raw cookie dump.
Why this improves the privacy cluster
A strong privacy cluster should have tools for source-level CMP checks, cookie-level signal checks, and string-level decoding. Consent Cookie Inspector is the middle layer in that stack.
That makes the section more coherent for users and for search engines. Each tool answers a distinct debugging question instead of overlapping awkwardly.
Operationally, that layered approach is what makes privacy debugging repeatable instead of chaotic.
Troubleshooting
What to look for
- Detected consent cookies and a short explanation of what each one represents.
Common issues
- Cookie presence alone does not prove runtime consent behavior is correct.
- The tool is a first-pass inspector, not a full privacy-state validator.
Best practices
- Paste raw input so the tool can apply formatting consistently.
- If output looks wrong, validate the input for missing commas or tags.
- Use the example buttons above to sanity-check formatting and behavior.
Related tools
More tools in the privacy / tcf category.
- TCF String Decoder - Decode IAB TCF v2 consent strings into human-readable metadata, purposes, and vendor consent arrays. Paste a TC string from a CMP or euconsent-v2 cookie, and instantly see what it contains for QA, troubleshooting, and compliance checks. Everything runs client-side for privacy.
- Cookie Inspector - Parse and analyze Set-Cookie headers or page cookie dumps to surface security, scope, and privacy issues with remediation guidance. Useful for privacy, security, and ad ops teams to quickly understand cookie risks and fixes.
- Cookie Sync Visualizer - Fetch a page and list likely cookie-sync or ID-match partners based on sync-like endpoints found in HTML resources. This is a useful first pass for privacy, identity, and header bidding investigations when you need to see which third-party domains look involved in sync behavior.
- US Privacy String Decoder - Decode IAB US Privacy strings into readable notice, opt-out, and LSPA flags for CCPA and US state privacy debugging.
Related reading
More specific pages for the exact jobs this tool supports.
Inspect Consent Cookies Before Partner Debugging
A privacy-signal workflow for auditing cookie presence before deeper QA begins.
Check Consent Cookies After a CMP Rollout
A rollout workflow for checking privacy cookie presence.
Inspect Consent Cookies on Consent-Denied Pages
A consent-state workflow for privacy cookie audits.
Review TCF and GPP Cookies Before Bidder Testing
A bidder-QA baseline workflow for privacy cookie presence.
Check Consent Cookie Mix After a Region Test
A geo-test workflow for privacy cookie comparison.
Audit Consent Cookies Before a Partner Escalation
A partner-escalation workflow for privacy cookie evidence.
Decode US Privacy Strings During CCPA QA
A concise privacy workflow for reading CCPA-style consent flags quickly.
Check CMP Markers Before a Privacy Rollout Review
A source-level CMP workflow for rollout reviews and post-migration audits.
Frequently asked questions
Is it free to use?
Yes. Core tools are free and accessible without signup.
Does it upload my data?
This tool runs locally in your browser. Data you paste or files you upload stay on your device and are not uploaded.
What if I spot a bug?
Please reach out via the Contact page with a reproduction example.
What input formats work?
You can paste document.cookie output, a Cookie header, or one cookie per line.
Does it fully decode TCF or GPP?
No. It identifies and summarizes known cookie artifacts so you know what deeper decoder to use next.
Why is this useful before bidder QA?
It confirms whether the page is even carrying the privacy signals the auction or identity workflow expects.
Helpful links
Standards & references
Official specs that inform how this tool interprets data.