Tracking and data anomaly detection, so a break never goes unnoticed.
Whisper watches three things for each site: the published GTM container, your key pages in a real browser, and your GA4 numbers. When a tag stops firing, the container changes or a number leaves its usual range, you get an alert with what it saw and the likely causes.
- Watch the checkout and tell me if anything breaks.
- Why did purchases stop last night?
I caught this in the 03:14 check. Orders still arrive in the store, so sales are fine and the tracking is what broke. These are the scenarios worth checking, most likely first.
- A theme update at 02:50 removed the dataLayer push from the order page.Most likely
- The consent banner now blocks the purchase tag for every visitor.Possible
- Container version 58 went live without the purchase trigger.Less likely
An alert you can act on.
You see what stopped, when it stopped and what the browser showed at that moment, with the causes ranked.
- The console and the hits from the failed check
- Store orders next to tracked events
- Each key page, passed or failed
- Purchase events in GA4
- Orders in the store
- Not recording
- Home pagePassed
- Product pagePassed
- Add to cartPassed
- CheckoutPassed
- Order pageNo purchase
Eyes on your tracking, day and night.
Key pages on a schedule
Home, product, cart, checkout and order pages are loaded and checked for you.
Console and network
It reads the dataLayer, console errors and the hits that leave the browser.
Alerts that say what happened
What stopped, when, and on which page. No vague warnings.
Likely causes, ranked
It compares with the last good run and lists the scenarios worth checking first.
Data anomaly detection
Every morning it compares yesterday's GA4 numbers with their usual range and flags what dropped or spiked.
A fix when it can
If the cause is in Tag Manager, it prepares the fix and asks for your approval.
You only step in at the end.
- 1Whisper
It watches
Scheduled checks on the pages that matter, in a real browser.
- 2Whisper
It detects
It notices when an event stops, a tag fails or the console shows an error.
- 3Whisper
It alerts and explains
You get what it saw and the likely causes, most likely first.
- 4You
You decide
Open the investigation, approve the fix or mute the check.
From the break to a fix before the morning.
This is the night from the example above. You wake up to an explanation and a fix, not to a week of missing data.
- 03:02Last purchase event recorded in GA4.
- 03:14The scheduled check finds no purchase event on the order page.
- 03:15Alert sent with three likely causes.
- 03:21Cause confirmed: the theme update removed the dataLayer push.
- 03:40A workaround in Tag Manager waits for your approval, with a note for your developer.
- Events that stop arriving
- Console errors on key pages
- Tags that no longer fire
- Missing dataLayer values
- Consent behaviour
- New container versions
- Sudden drops against store orders
One chat for the rest of the work.
Questions about monitoring.
How often does it check?
It depends on your monitoring plan: from once a day up to every few hours for the published container and key pages, and more often for a while after a new version goes live. GA4 numbers are checked every morning.
What is data anomaly detection?
It compares each day's numbers, such as sessions, purchases or key events, with their usual range. A drop or a spike outside that range raises an alert, so a tracking break shows up the next morning, not at the end of the month.
Where do alerts arrive?
By email and in the app. You choose who gets them for each site.
Will I get noise?
It alerts on things that stopped or changed against the last good run. You can mute a check or a site at any time.
What happens after the alert?
It keeps investigating, confirms the cause when it can and prepares a fix if the problem is in Tag Manager.
Put a site under watch.
Add a site, pick the pages that matter and let Whisper keep an eye on them.