Tracking Watch by Metric Owl

Your tracking, tested like a customer. Every night.

Marc Alexander built Tracking Watch to do what he used to do by hand in every audit: open the site, accept, reject, add to basket, check out, refresh, and check every tag along the way. Now it runs in minutes, before launch and every night after.

  • 110+UK websites tested
  • 3cookie choices on every journey
  • 1,500+problems found so far
  • 0test visits in your reports

From the consultant behind the tracking at Halfords Knight Frank WorldFirst VisitBritain Hertility Health

Watch it find the problems.

47 seconds of a real run on Hollow Oak, a demo candle shop that's broken on purpose, sped up twice. The captions are what Tracking Watch reported.

How it works.

  1. 01

    It visits like a customer.

    A real browser opens your site on a laptop, a phone and a tablet. It browses, searches, adds to basket and goes through checkout, the way your customers do.

  2. 02

    It makes every cookie choice.

    Each journey runs three times: before anyone touches the banner, after “Accept all” and after “Reject all”. Tracking should only follow a yes.

  3. 03

    It records everything, and sends nothing.

    Every request to GA4 and the ad platforms is captured, then answered by the test browser itself. Your reports and ad accounts never see a test visit.

  4. 04

    It checks every event against your spec.

    Each event is checked field by field: the right values, sent once, with no email addresses. Then it refreshes the order confirmation, to make sure the sale isn't counted twice.

  5. 05

    It checks its own findings.

    Before anything serious is reported, it's tested again in a fresh browser. Each finding says whether it was proven, likely or needs checking, with the evidence and the fix.

  6. 06

    Then it does it all again tonight.

    Monitored sites are tested every night from a server in London. You hear about it only when something new breaks, with Marc's note on what to do.

Why it's different.

Cookie scanners list cookies. Monitoring tools watch real visitors, so they can't test a site nobody has visited yet. Tracking Watch tests the journeys themselves, before launch, and a person reads every result.

Cookie scannersLive-traffic monitorsTracking Watch
Tests a new site on staging, before launch✕✕ needs real visitors✓
Checks what happens after “Reject all”Lists cookiesOnly for visitors who reject✓ every journey
Checks each event against your spec✕✓ once traffic arrives✓ field by field
Refreshes the confirmation page to catch double-counted sales✕✕✓
Finds personal data sent to GA4 or ad platforms✕Sometimes✓ masked in the report
A specialist reads every finding and gives the fix✕✕✓ Marc

Free tool

Test your own site, free.

Paste a page address. The free tracking checker shows what a first-time visitor sends before agreeing to anything: a quick taste of what Tracking Watch checks in full.

Built, not bought

One consultant, his own testing.

After ten years of GA4 and Tag Manager work, from Halfords to Knight Frank, Marc kept finding the same problems: tags firing before consent, sales counted twice, email addresses reaching GA4. Each one was found by hand, once, and could quietly come back with the next release.

So he wrote Tracking Watch to check all of it, the same way, every time. It also reads Figma designs to write the tracking spec before anything is built, then tests the build against that spec.

  • Real browserChromium, with Safari's cookie rules simulated
  • Londonnightly runs from a UK server, for a UK visitor's view
  • Proven, likely or checkhow sure each finding is, stated
  • Plain Englishwho fixes it, how, and how long it takes

See a real report.

From a run on Tracking Watch's demo shop, which is broken on purpose. Nothing here is a real company.

Management summary: grade D, 40 out of 100, with a one-minute overview and a scorecard
The management summary, for the people who need the headline
Scorecard: each area's score out of 100 and the findings behind it
Each part of the setup scored, with what cost the points
Key insights: the business effect of the findings
What it means for the business: risk, lost data, wasted spend
Roadmap: what to fix and when, with who and how long
What to fix first, who does it and how long it takes
Two findings in detail, each with why it matters, the evidence, the fix and how to check it
Every finding with its evidence, the fix and how to check it

Download the full report (PDF, 48 pages) Download the summary (PDF, 8 pages)

What do people ask about Tracking Watch?

Do we need to install anything?

No. Tracking Watch visits your site from outside, like a customer, so there's no snippet or plugin. For a staging site behind a login it needs a test account, and if your firewall blocks automated browsers, a header your developers can allow.

Does testing touch real customers, orders or our data?

No. Every request to GA4 and the ad platforms is recorded and then answered by the test browser itself, so nothing reaches your accounts or skews your reports. On a live site, journeys stop before anything that would place an order or contact anyone. Test orders only happen on staging, in your payment provider's test mode.

Can we buy Tracking Watch as software?

Not at the moment. It's how Marc works: every run is read by him, and every alert comes with what it means and how to fix it. That is what makes it more than another dashboard.

Which tools does it check?

GA4 and Google Tag Manager first, plus Google Ads, Meta, Microsoft Ads, LinkedIn, TikTok, Pinterest and others, server-side tagging, Consent Mode v2 and the main cookie banners, including OneTrust, Cookiebot and CookieYes.

Does it work for apps?

Yes. Web apps are tested in the browser behind a sign-in. Native apps are tested from a recording of the app's own traffic on a test phone, against the same spec.

Last updated

Ask about Tracking Watch.

Tell Marc about your site or app, and whether it's live or still being built. He'll say which way of using Tracking Watch fits.

GA4 monitoring from £150 a month.

Prefer to talk first? Choose "20-minute intro call" in the form.
Or email [email protected].

Marc replies personally, usually within one working day.