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

Consent Mode failures often look like an unexplained analytics drop. The key distinction is whether a consent state is actually set before tags use it.

A passive scan cannot impersonate every visitor choice, so it reports observed commands and unknowns rather than inventing a consent result.

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. Observe redacted commands

    We record consent state keys, never personal values or CMP choices.

  2. Check request markers

    Consent-related request parameters provide a second browser-side signal.

Common causes and fixes

Defaults are absent
Tags initialize without an explicit consent state.
CMP updates too late
The intended state arrives after measurement starts.

Frequently asked questions

Does it click Accept?
No. It remains passive.
Does it prove compliance?
No. It is a technical measurement check, not legal advice.

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