Extension Pro
CMP Configuration Checker
Check supported CMP signals, consent APIs and Google consent commands. Compare detected configuration with cookies and requests on the deployed page.
ConsentScope Pro checks supported signals from the consent setup exposed by a page. It helps you distinguish a detected CMP, an available consent API and readable Google consent commands before investigating how individual services respond.
The checker observes the page, not the private administration console. It cannot confirm which draft a team intended to publish or whether every region receives the same configuration. Keep the public URL and test conditions alongside its findings.
A missing signal can mean an unsupported integration or an observation limit. A detected signal can coexist with a script that ignores consent. Use the result to decide what to verify next.
Separate the four questions in a consent investigation
| Question | Evidence to inspect | Where to follow up |
|---|---|---|
| Did a consent interface load? | The page and detected CMP indicators | CMP script delivery and browser errors |
| What choice is available or saved? | The interface and supported consent signals | CMP configuration and SDK integration |
| Did Google receive the intended state? | Readable consent commands where available | Google Tag Assistant |
| Did optional services obey it? | Requests, cookies and storage in the test | Application and tag-manager loading paths |
A result from one row should not answer another by assumption. A TCF API can be present while a custom analytics script starts independently. A banner may be absent because a visitor already has a saved preference, not because the CMP failed to install.
Check publishing and environment differences
Ask the configuration owner which domain or settings identifier should be deployed. Compare it with the public page, not just a preview. Record whether you tested staging or production and whether caching could serve an older configuration. That information often explains why two reviewers see different results.
When a reported issue affects only one route, compare its template and service inventory with a working route. When it affects one region or language, verify that specific variant. Do not edit a global consent rule to solve a symptom observed under unknown test conditions.
Example: API found, consent commands missing
Suppose the check finds an IAB TCF API but no readable Google consent commands. The next step is to establish whether Google tags are present and how consent reaches them. A GTM integration may use an interface that this check does not expose. 'No commands detected' should remain an observation until that integration has been examined.
Use the TCF decoder for supported TCF details and the Consent Mode checker for the four Google fields. Neither result removes the need to inspect what the relevant service actually does after rejection.
Build a repeatable configuration review
Keep a short record of the URL, deployment, starting preference, action and observed signals. Then add the request or storage evidence that supports any reported failure. If detection is incomplete, note the manual verification method instead of silently treating the missing fields as a pass.
Use the vendor-specific OneTrust, Cookiebot, Didomi, Complianz or Usercentrics procedure to finish the review. A reviewed snapshot can preserve the observed context for the configuration owner.
How it works
Load the target page in a clean session with the intended language and region.
Run the CMP configuration check and record the supported signals it reports.
Change a consent preference and compare the visible state with requests and storage.
Verify uncertain findings in the CMP's tools or Tag Assistant, then retest the public deployment.
Key benefits
Integration context
Identify supported consent signals available on the page.
Targeted investigation
Separate missing detection from confirmed implementation behavior.
Repeatable checks
Compare the same deployment before and after a change.
Who is it for
CMP administrators
Compare public-page signals with the intended published configuration.
Developers
Debug why certain scripts still load despite consent rejection.
DPOs
Add empirical CMP testing to your recurring compliance review.
Frequently asked questions
Does it inspect my CMP account?
Does not detected mean not installed?
Does a detected TCF API prove Google Consent Mode is correct?
Unlock CMP Configuration Checker with ConsentScope Pro
Extension Pro provides lifetime access to the paid browser features. Monitor and Agency are separate subscriptions for cloud monitoring. Compare the plans for your workflow.
View Extension Pro