Map what’s firing
An evidence-backed read of the major tags and pixels on your live site, and the requests they make.
Enter a site.
See what your tracking is doing.
Scan the live page for analytics and ad tags, duplicate events, and consent problems. Every finding includes the evidence.
See the evidence.
Every check that ran is shown — what passed, what failed, and what could not be verified.
How it works
Proof that keeps up.
Don’t take your tracking on faith. MeasureProof keeps a tracking baseline and protects you by catching changes before they reach your numbers.
Observe · Remember · Compare · Prove
Set the baseline
That read becomes your baseline: the reference every check compares against.
Watch for changes
Re-run on a schedule. When something visible changes, you know first.
Show the evidence
See what moved and what it can affect — never more than the evidence proves.
Proof Watch
A scan gives you a baseline. Watch keeps it current.
Run the same checks on a schedule and see what changed, what still passed, and what could not be verified.
Run on a single site or a roster of client sites.
Explicit opt-in · Unsubscribe anytime
Tracking Report
11 verified
1 change
Still verified
11 of 12 validations held on Monday’s run.
- GA4 configuration tag — firing once on load
- Single GTM container, GTM-XY••Z
- Consent signal present before tags fire
1 change
A Meta Pixel that wasn’t there last week is now firing on /pricing.
+ pixel 8841•••• · /pricing · first seen Mon 09:00
+ pixel 8841•••• · /pricing · first seen Mon 09:00
Common questions.
Will the scan show up in my analytics?
It can. A scan loads your page in a real browser, so analytics and ad tags that fire during the scan may record it. A scan uses one or more page loads: a supported consent banner or a retry can add another. The browser has no cookies or history and arrives from our scan region, so some sites treat it differently.
Do you need access to my GA4 or GTM?
No. A scan needs a URL and nothing else. There is no sign-in to grant, no read-only user to add, no container to publish. Everything in the report comes from what your live page sent to the network. Anything that would require the inside view is named as exactly that rather than guessed at — the Method page sets out the full boundary.
How is this different from Tag Assistant or GA4 DebugView?
Those show you one session that you are driving, on demand, while you watch. A scan is an unattended read of what a first-time visitor’s browser receives, recorded as evidence. Proof Watch is what reruns it on a schedule and compares each run against a saved baseline. Debug tools answer “is this working right now while I look at it.” A scan under watch answers “what changed since last week, and can you prove it.”
What if my site blocks the scan?
Some sites — bot-protected e-commerce in particular — refuse the request before any tracking loads. When that happens the report records a coverage gap and says so. A blocked page is never reported as a clean one.
What do you keep?
The minimized observation behind the report — the findings, the tracking inventory, the consent evidence, and the checks that passed, so a clean baseline is still a receipt you can keep. Raw browser capture is discarded: cookies, auth headers, request bodies and full URLs are dropped before anything is stored, and request evidence is retained only in redacted form. Measurement IDs are partially masked wherever a report can be shared. See the privacy policy and security model.
Can I scan client sites?
Yes. A scan needs only a public URL, so it runs on any site you are responsible for — one at a time, or as a roster under watch. Nothing is installed and nothing on the site changes.
We publish exactly what we check — and what we don’t claim.
Read how MeasureProof works →