Privacy & Identity Library
Back to libraryInspect CMP API Markers Before a Banner Rollout
Use the inspector before a banner or consent UX rollout to confirm that the underlying CMP APIs appear present.
Why this workflow matters
Teams use CMP Inspector when they need to confirm that CMP API markers appear in page source before a banner rollout or launch review. Consent UX reviews can miss the simpler failure where the underlying CMP APIs are not loading consistently at all.
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, review API and vendor markers, and use that output to decide whether the rollout is ready for deeper runtime testing. 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 cleaner rollout review where source-level CMP presence is verified before runtime behavior gets debated.
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.