Privacy & Identity Library
Back to libraryCheck CMP Markers on a Template With Broken Consent
Use the inspector as a first step when one page template appears to have broken consent behavior.
Why this workflow matters
Teams use CMP Inspector when they need to confirm whether a problematic template even contains the CMP markers the rest of the site relies on. Template bugs often get misread as broad privacy issues when the source-level CMP markers are only missing on one template.
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 problematic page source, review the API and vendor markers, and compare the output with a healthy template. 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
The best result is a narrower privacy investigation that starts from what the broken template actually includes.
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.