How AnalyticsProof works

The site works. The tracking doesn't. And nobody notices.

A deploy, a GTM edit or a new cookie-banner version can silently drop the purchase from GA4. The page looks fine; the report is just off for a week. AnalyticsProof walks your key journeys on a schedule, like a customer, and shows exactly what changed.

Walk through your site once, in our browser. Nothing to install: no code, no GTM change.

Demo: in the Record journey dialog the user walks a test shop. They accept cookies, open a coffee, add it to the cart and order. Five steps appear on the right, then “Journey saved.”

Platforms Web: journeys and consent Android apps: recorded in a remote Android emulator HbbTV: smart-TV apps

Setup

Nothing to install

No code on your site, no new tag in GTM. You record the journey in our browser.

Environments

Production and test sites

Password-protected is fine. Test the purchase without real orders or payments.

Country

We scan from where you need

The browser gets the language, time zone and IP address of the chosen country. The cookie banner shows up as it does for your visitors.

What we check, and what we don't

Stated up front, so you know what you can rely on.

We check

  • Which events reach the dataLayer at every step, and with which parameters
  • Parameter data types, e.g. that value is a number, not text
  • What is sent to GA4, Google Ads, Meta and other tools
  • Whether tools store cookies and visitor IDs before consent and after a reject
  • Google Consent Mode: the default state and the update after the banner choice

We don't check

  • Values. We don't read or store prices, order numbers or email addresses.
  • How GA4 or Google Ads process the data and what the reports then show
  • Legal assessment. We give you technical evidence; the conclusion is your lawyer's.

What actually keeps clients up at night

Nobody buys “dataLayer monitoring”. They buy answers to questions they can't answer today.

“Why has GA4 revenue been down a third since Tuesday?”

A deploy broke the purchase event. Without monitoring you find out from the report.

Head of Analytics · e-commerce

“Does nothing really go out after a cookie reject?”

The banner has the button, yet GA4 and ad tools keep tracking visitors. Nobody checks that by hand on a regular basis.

DPO · legal

“Who broke it, and when?”

The agency in GTM, developers in a release, the banner vendor in a new version. The run history shows the day it changed.

Marketing · site owner

“Stop the broken version from shipping at all.”

A check right in the pull request, on the preview. The developer sees the problem before merging.

Development team · Professional

For DPOs and legal

A scan result is a record: what we saw, when, and from where.

  • A PDF report for every scan

    Verdict, score, tools and evidence: the first request and the stored identifiers. Send it to your lawyer or your banner vendor.

  • We don't store values

    We compare event and parameter names and their types only. Personal data from forms or orders never reaches us.

  • The scanner runs in the EU

    We run the browser in a data centre in the EU and connect it through the country you choose.

AnalyticsProofCompliance Scan Report
zrnko.example
3 findingsAdvertising assessment: Non-Compliant50 %
Google Ads
Non-Compliant
Google Analytics 4
Non-Compliant
Meta Pixel
Non-Compliant
Google Tag Manager
Compliant

Where results go

Wherever your team actually is.

Email

A journey-run summary with a link to the result.

All plans

Slack

Alerts to a channel via webhook.

Starter and up

GitHub

A check and a comment on the pull request.

Professional and up

API

Start scans and read results from your own tools.

Starter and up

Frequently Asked Questions

Q1

Do I have to install anything on my site or in GTM?

No. You record the journey in our remote browser and we replay it the way a real visitor would. Nothing is added to your site.

Q2

Won't the tests create real orders?

Record the purchase journey on a test environment with a test payment method, password-protected if you like. On production you can end the journey before the order is placed.

Q3

What if a redesign breaks the recorded journey?

When a button moves or is renamed, we try to find it again and give you the fix to approve. If the journey stops early, you see at which step, and it doesn't count as a finding on your site.

Q4

How often do you test?

Free: every 2 weeks. Starter: daily. Professional: daily at a set hour. Manual runs from Starter.

Q5

Will it slow my site down?

No. One browser visits your site like one visitor, and nothing runs on it between tests.

Q6

What do the verdict and the score mean?

The verdict states how many findings we proved. The technical score sums up the consent checks, meaning the banner, the reject, Consent Mode and cookies, as one percentage.

Have your measurement monitored every day.

A free project, no credit card. One web compliance scan a month; you switch on daily monitoring and the other scan types when you need them.

Create a free project