Privacy & Identity Library
Back to libraryCheck CMP Markers After a Tag Manager Change
Use CMP inspection when a tag-manager or template change may have altered CMP loading behavior.
Why this workflow matters
Teams use CMP Inspector when they need to confirm that CMP markers and scripts still appear after a tag-manager or template change. Infrastructure and template edits can silently break CMP loading before anyone reaches runtime consent tests.
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 source or fetched page, review the detected APIs and script hosts, and isolate any missing CMP markers before deeper QA begins. 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 useful check catches source-level CMP drift before the issue becomes a wider privacy or bidder complaint.
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.