Clarvivo

Free tool by Clarvivo · no login

See what changed in tracking between two page versions

Paste a baseline and comparison URL—such as staging and production, or before and after a release. We open each public page independently and show the tracking signals that appeared, disappeared or changed.

Baseline URL

Paste the equivalent before-and-after, staging-and-production, or old-and-new URLs. We compare the public tracking stack and page signals without submitting forms or using credentials.

This tool answers: What tracking signals changed between these two versions of my page?

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

Why this happens

Tracking failures often begin with a harmless-looking release: a container moved, a consent script changed order, a redirect was added, or a theme update removed a tag. By the time a weekly report drops, the only evidence may be a changed total.

A before-and-after comparison turns that vague suspicion into a concrete diff. It cannot prove account-side attribution or server events, but it can show whether the browser-side foundations changed at the moment the deployment did.

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. Scan both pages separately

    Each supplied public URL is guarded and opened in an isolated browser. We do not carry cookies, credentials or form state from one version to the other.

  2. Compare observable tracking signals

    The result compares detected tracker families, account identifiers, named events, redirect outcomes, document metadata and browser errors rather than treating a visual match as a tracking match.

  3. Explain missing evidence carefully

    A tag absent from this scan may be consent-gated or interaction-driven. The result reports the condition and recommends the narrowest follow-up test instead of claiming every unseen event is removed.

Common causes and fixes

A tag or container was removed during a deploy
A template or consent-script change can leave the page visually intact while removing GA4 or ad-platform requests entirely.
The measurement ID changed
A new or duplicate account ID can redirect data into another property or count events twice. Compare identifiers before assuming a traffic change is real.
A redirect or browser error changed page timing
New redirects and JavaScript errors can change when a tag runs or stop the code that dispatches it.

Frequently asked questions

Can I compare staging and production?
Yes, provided both are public http or https pages. The URLs are scanned independently and cannot use private hosts, credentials or non-standard ports.
Does this submit forms or test checkout?
No. It compares the public page-load surface only. Use a controlled test environment for interaction-dependent conversions.
Why might a tag be absent even if it is installed?
Consent settings, user interactions, regional rules or a blocked request can defer a tag. The comparison reports what was observed in the scan, not a claim about every possible visitor state.
Can it compare yesterday with today?
Use two stable URLs or a staging-and-production pair. Historical comparisons need stored scan snapshots, which are not part of this first release.

Do not wait for a report to discover a tracking regression.

Clarvivo keeps acquisition and revenue signals visible over time, so deployment changes can be checked against the outcomes they affect.

Monitor tracking against revenue

What this tool reads, and what it keeps