Clarvivo

Free tool by Clarvivo · no login

Check whether tracking starts before observable consent state

Compare passive browser timing without clicking a banner or claiming a race when no timing is available.

Public page with consent banner

Compare the passive timing of redacted consent commands and recognised tracking requests. It reports unavailable timing as unknown rather than guessing.

This tool answers: Do browser tracking requests appear before the first observable consent state?

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

Why this happens

A CMP can be present and still initialize after analytics or ad tags fire. That ordering creates inconsistent measurement and hard-to-explain consent behavior.

Timing must be treated carefully: no observed marker is not proof of a race, which is why the tool reports it as unknown.

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. Build a redacted timeline

    Consent commands and recognised tracker requests are compared by browser timing.

  2. Preserve uncertainty

    The tool never infers consent solely from tag absence.

Common causes and fixes

Tag code loads before CMP defaults
Direct snippets can race a consent-manager callback.
Late async initialization
A banner script may wait too long to update the dataLayer.

Frequently asked questions

Does it test both choices?
No; validate denied and granted paths manually after this passive audit.
Can it bypass a banner?
No.

Make consent behavior explainable.

Clarvivo keeps browser gaps in context with business outcomes.

Understand consent impact

What this tool reads, and what it keeps