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 breaks during releases. A redesign drops the GTM container from one template, a new consent banner changes when tags load, a CMS migration loses the ecommerce events, or a performance pass defers the analytics script past the point where it captures the landing page. Nobody notices until the weekly report looks strange.

The fastest way to catch it is to compare: the same page before and after, or staging against production. But comparing tracking by eye means opening developer tools on both, filtering network requests and trying to remember what was there last time.

This detector loads both URLs in the same way and compares their public tracking surface: scripts, tags, events, consent settings and forms. You see what was removed, what was added and what changed.

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. Paste two URLs

    A baseline and a comparison: before and after a release, staging and production, or the old and new version of a template.

  2. We capture each page the same way

    Both pages are loaded in isolated browsers and we record the tracking scripts, tag IDs, events and consent signals each one exposes.

  3. We diff the two snapshots

    Removed scripts, tags and event definitions are reported first, because lost coverage is the most damaging change. Additions and configuration changes follow.

  4. We flag page and form changes

    If the page structure or its forms changed significantly, that's noted too, since form changes often break lead tracking.

Common causes and fixes

Tag manager missing on a new template
Redesigns often add new templates that don't include the GTM snippet. Make the container part of the base layout.
Script loading deferred too late
Performance work that delays analytics until interaction loses bounced visitors and their sources.
Consent configuration changed
A new banner or CMP update can change defaults from granted to denied, or stop firing update commands.
Ecommerce or form events renamed
Platform upgrades rename data layer events. Triggers listening for the old names stop firing.

Frequently asked questions

Can I compare staging with production?
Yes, as long as both URLs are publicly reachable. Password-protected staging sites can't be scanned.
Does it compare the full GTM container?
It compares what's observable in the browser: loaded scripts, tag IDs, fired events and consent signals. Paused or unpublished tags inside GTM aren't visible.
What counts as a change?
A tracking script, tag ID or event that's present on one page and not the other, or a changed consent setting.
Is a new script always good?
Not necessarily. New coverage is listed so you can check it's intended, not a duplicate tag.
How often should I run it?
After every release that touches templates, consent, checkout or forms.

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