Conversion signal monitoring

Know when your tracking
stops behaving like it should.

CookieChest watches the tracking signals that matter and compares them with the healthy baseline. When something changes, you get an alert with enough context to start investigating — not a dashboard you have to remember to check.

Signal status reportacme-agency.com · Today 09:00
Site availability200 OK — 1.2s response
Consent bannerLoaded, Consent Mode V2 active
GTM container14 tags firing correctly
GA4 streamEvents flowing post-consent
Pre-consent signalsGA4 fires before consent — needs review
Google Ads conversionsNo data received for 4h 12m
For agencies

Find out before your client does.

A Friday release breaks a tag. A consent plugin changes behaviour. Google Ads stops receiving conversions. The awkward Monday-morning client email should not be your monitoring system.

Monitoring is built for teams where a silent tracking failure has a real commercial or client-retention cost.

The Monday morning email

Friday afternoon a developer pushes a release. By Monday your client emails: “leads have dropped — what’s happening?” You scramble to check tracking. Three days of conversion data are already gone.

Smart Bidding starves

Consent Mode misfires after a CMP update. Google Ads can’t see conversions. Smart Bidding starves the campaign — and even after you fix it, performance takes a fortnight to recover.

What 99% uptime looks like

A dev pushes an untested update. GTM stops firing. We catch it inside 6 hours — not the next retainer review. One incident like that pays for itself many times over.

WHAT WE'VE FOUND
69%

of UK sites had GA4 silent after consent on first scan

We scan UK sites across multiple sectors and consent platforms — all running paid advertising. The majority had GA4 failing to fire when the visitor accepted cookies. Most of the agency reporting they pay for, quietly broken on the day we found it.

What Monitoring answers

Monitoring asks one simple question: has the healthy behaviour changed?

Is the site responding normally?
Is the consent banner present and behaving as expected?
Is the GTM container still loading and firing?
Are GA4 signals still flowing?
Has consent behaviour moved outside the expected pattern?
Have important conversion signals disappeared or materially changed?

What happens when something changes

You get an alert that tells you what changed, when it was detected and what signal triggered it. The aim is to shorten the gap between “tracking broke” and “someone noticed”.

CookieChest Alerts
Today, 14:22
RED ALERT

GA4 conversions silent on client-site.com

What we found

GA4 conversion tag stopped firing after consent on client-site.com.

When

Working at our 06:00 scan. Silent at our 14:00 scan. Something changed in that window — worth checking deploys, CMP edits, or tag manager changes.

Full audit trail and scan history attached.

View full audit trail →

Monitoring does not prove the baseline is correct

This distinction matters.

Monitoring can tell you that consent rejection has stayed at 95% for five months. It cannot, by itself, prove that 95% was ever correct.

Monitoring protects a known-good baseline from silent change. If you are not confident the implementation or baseline is right in the first place, that is an Assurance problem.

How it works

1

Establish what healthy looks like

We configure the checks around the site and the signals worth protecting.

2

Monitor continuously

CookieChest compares current behaviour with the expected baseline and watches for meaningful deviations.

3

Get alerted

When something changes enough to matter, you get the alert and context needed to investigate.

Monitoring that earns its keep the first time something breaks.

Tell us what you need to protect and what a silent failure would cost you. We'll take it from there.

Catch tracking failures before your client does

Tell us about your portfolio and what a silent failure would cost you. We'll take it from there.