Clarvivo

Free tool by Clarvivo · no login

See the Consent Mode v2 signals a public browser can observe

Audit redacted defaults and tracking markers without clicking consent or collecting visitor data.

Public page with consent banner

Inspect redacted Consent Mode commands and request markers during a passive first visit. The tool does not click a consent choice or infer a state it cannot observe.

This tool answers: Are Consent Mode v2 defaults and browser signals observable on this page?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

Google Consent Mode v2 tells Google tags whether a visitor has consented to analytics and advertising storage, and whether their data can be used for ads (ad_user_data) and personalisation (ad_personalization). For traffic from the EEA, Google requires these signals for measurement and remarketing features to keep working.

Implementations fail in ways that are hard to spot: no default is set before tags load, the consent banner never sends an update command, the CMP isn't integrated with Google's API, or signals are set after tags have already fired. Google Ads and GA4 show consent warnings, but not which page or step is wrong.

This tester loads a page with your consent banner during a first visit and reports what's observable: consent commands in the dataLayer, consent parameters on Google requests, and whether a known CMP was detected.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

  1. We load the page as a first-time visitor

    The page is opened in a fresh isolated browser, so the banner appears as it would to a new visitor. We don't click any consent choice.

  2. We record consent commands

    Consent default and update commands pushed to the dataLayer are captured, with values redacted to their states.

  3. We check Google request parameters

    We look for consent parameters (gcs, gcd and related markers) on Google tag requests, which show what state the tags actually used.

  4. We look for a CMP

    We check for signatures of common consent platforms. Not finding one doesn't prove there isn't one.

Common causes and fixes

No consent default before tags load
The default command must run before Google tags. Place it at the top of the page or use your CMP's Google integration.
Banner doesn't send updates
If accepting doesn't trigger a consent update, tags stay in the denied state for everyone.
v2 parameters missing
Consent Mode v2 adds ad_user_data and ad_personalization. Older implementations only set analytics_storage and ad_storage.
Tags fire before consent is set
If tracking requests go out before any consent state exists, see the Consent Race Condition Checker.

Frequently asked questions

What does Consent Mode v2 add?
Two parameters: ad_user_data and ad_personalization, alongside the existing ad_storage and analytics_storage.
Does the tool accept or reject the banner?
No. It observes the first-visit state only and doesn't infer what happens after a choice.
What are gcs and gcd?
Parameters on Google tag requests that encode the consent state the tag used. Their presence shows Consent Mode is active.
My CMP wasn't detected. Is that a problem?
Not necessarily. Detection covers common platforms. What matters is whether consent commands and parameters are present.
Is Consent Mode required?
For EEA traffic, Google requires consent signals for ads measurement and personalisation features.

Separate consent visibility from actual performance.

Clarvivo combines multiple sources when one browser signal becomes partial.

Understand measurement gaps

What this tool reads, and what it keeps