Privacy & Identity Library
Back to libraryAudit CMP Source Before a Privacy Escalation
Use CMP inspection when a privacy escalation needs basic evidence about CMP APIs, vendors, and script hosts before it goes external.
Why this workflow matters
Teams use CMP Inspector when they need to gather source-level CMP evidence before escalating a privacy implementation issue. Escalations are weaker when they jump straight to behavioral claims without first confirming what the page source shows.
The search intent behind this topic is usually very specific: someone has a real debugging task in front of them and needs a practical workflow rather than a generic tool list. CMP Inspector is the anchor tool for this page because it addresses the core evidence needed to move the issue forward.
How to investigate it
Open CMP Inspector first and inspect the page source or fetched URL, summarize the CMP APIs, vendor markers, and script hosts, and use that output as baseline escalation evidence. Supporting tools such as Consent Cookie Inspector and TCF String Decoder help once the first clue is visible.
The goal is not just to get an answer on screen. The goal is to produce a clean explanation that can be shared with engineering, ad ops, or an external partner without re-running the entire investigation from scratch.
What good output looks like
A strong audit gives the privacy escalation a factual starting point before runtime or legal discussion widens.
This is also where niche pages win SEO more often than broad phrases. People searching for this exact troubleshooting scenario want a focused answer tied to a real operational problem. A page like this converts that intent directly into a tool workflow instead of asking the reader to infer which utility to open.
Run the privacy checks next
These tools help when the issue is in consent strings, cookie state, CMP presence, or privacy-signal handling.
CMP Inspector
Inspect page source or a public URL for CMP API markers, common CMP vendors, consent-cookie names, and script hosts before deeper privacy debugging starts.
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.
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.
Keep moving through privacy debugging
Use the next links when you need to connect this page with the rest of the consent and CMP workflow.