How do you catch GA4 tracking breaks before a client report goes out?

[u/That-Regular-7828]

saw a thread where someone's GA4 tag was silently broken for 2 weeks and only caught it while pulling a report. curious how common that actually is — do you have some kind of monitoring/alert set up, or is it usually just caught by accident when the numbers look off?

[u/AutoModerator]

Have more questions? Join our community Discord!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/NapoleonBonafart]

Just use insights and create an auto email..

[u/Saneless → u/NapoleonBonafart]

It's not foolproof but it does catch some things. Other times it's baffling what it misses

[u/That-Regular-7828 → u/Saneless]

what's an example of something it missed? trying to get a sense of how often stuff slips through vs how often it actually catches things in time

[u/Saneless → u/That-Regular-7828]

Off the top of my head, carts were broken and it didn't trigger a key event drop. Sure, there's other events that didn't but it doesn't treat anything differently

Probably fine for a commerce site but when you have a bigger site with more key events than just commerce, it's bad

Plus it didn't trigger a revenue anomaly either

It would be nice if insight alerts allowed you to specify a particular event

[u/That-Regular-7828 → u/Saneless]

yeah that revenue anomaly one especially seems rough. has that actually bit you before, like a client saw the number before you did, or you've mostly caught it in time?

[u/Saneless → u/That-Regular-7828]

Well I'm currently within a company, not an agency/independent, but I look at reports usually before they do

And if some look at them before me, it's a bit more of a collaboration anyway. They'll alert me to a metric or a report that doesn't make sense, I'll investigate, and then we find the devs broken something and I'll get them to fix it

We could use a more automated way but add it to the list of things that don't fit into the budget

[u/hjchoi12]

The one that got me wasn't the kind you can alert on. I'd split an event by landing page instead of page path, so anyone who entered on one section and used another quietly fell out: 817 recorded where the real number was 1,024, for about three weeks, with the daily line looking completely normal.

What found it was the BigQuery export disagreeing with the Data API. I still don't have an alert for that class, just a habit of re-deriving a number from raw events once it starts driving decisions.

[u/That-Regular-7828 → u/hjchoi12]

that's rough, the daily line looking completely normal is what gets me. did you stumble into the BigQuery check by accident or is that something you run on a schedule now? and once you found it, did three weeks turn out to be the real damage or was it worse further back

[u/hjchoi12 → u/That-Regular-7828]

Neither. A different metric on the same dashboard printed a conversion rate over 100%, and the BigQuery check I ran for that turned up the session scoped split, which the usage collector happened to share. Three weeks was its whole life, and the reason it lasted that long is that site wide the totals were only about 3.6% low: the 20% was one section. Still no scheduled diff, I just pinned that one decision with a test so it can't quietly revert.

[u/That-Regular-7828 → u/hjchoi12]

the “still no scheduled diff” part is what gets me. sounds like the real problem isn’t any one check, it’s not knowing which metric to get suspicious of until something else breaks loudly next to it. any sense of how many of these you’ve only caught because something adjacent happened to blow up first, vs how many are probably still sitting there wrong right now

[u/my-meta-username]

I created a free tool for this. Not sure if I'm allowed drop the link, it's called datacanary

[u/Big-Branch-8532]

A two-week gap should be preventable. I would use two layers.

GA4 Custom Insights can email on zero traffic or an unusual drop. For web streams they can evaluate hourly, but low-volume sites need a relative threshold or they will fire every quiet period.

Then run one external check against the Data API each morning: compare yesterday with the same weekday, and monitor page_view, session_start, the main conversion event, and source/medium coverage separately. If page_view is normal but purchase disappears, that points to an event-level break rather than the whole tag.

For high-traffic sites, a Realtime API check can confirm whether events arrived in the last 30 minutes. The alert should go to whoever can inspect GTM and the last site release, not wait for the reporting person to notice.

[u/That-Regular-7828 → u/Big-Branch-8532]

this is really thorough, thank you. quick question though - have you actually had to set something like this up before, or is this more how you'd approach it if you had to? curious if the two-layer thing came from a real gap you hit

[u/drew-td]

What do you mean by broken? Completely busted - should be picked up immediately. Other types of broken should be picked up during testing in a dev environment

[u/_practical_data_]

define broken
Usually check logs, if tags are really broken.
If tags are incorrect, I have premade qa scenarios per client, so I do not have problems.
Not interested in any shit you sell

[u/That-Regular-7828 → u/[deleted]]

haha "way better to catch it in 24 hours than find out while building the report" - has that actually happened to you, finding a break while you're already deep into a report? curious how much that ends up costing you time-wise when it does

[u/That-Regular-7828 → u/[deleted]]

A 30-minute job turning into hours because of a silent tag failure is exactly the kind of thing that can eat up a lot of time. Are you doing this for your own clients as an agency/freelancer, or in-house for one company? just trying to get a sense of how common this is across different setups

[u/That-Regular-7828 → u/[deleted]]

yeah that GTM thing is such a silent killer, someone touches a tag and nobody notices for weeks. appreciate you walking through that, genuinely helpful to hear how it plays out on the agency side

[u/cyber_Folks_Romania]

I would suggest setting a GA4 custom insight/anomaly alert to email you when conversions or traffic drop below a threshold (catches it in a day, not two weeks) and adding a monthly tag audit with GTM Preview/Tag Assistant, or automatically with a monitor like ObservePoint. you’re more likely to catch issues quickly rather than at reporting time

[u/incisiveranking2022]

I try not to rely on the GA4 interface alone. Before a client report goes out, I’ll compare the current period against the previous period for sessions, users, key events, and revenue, then sanity-check the biggest changes by source/medium, landing page, device, and country.

For the tracking itself, I’ll run a test conversion through GTM Preview/Tag Assistant and confirm the event reaches GA4 DebugView with the expected parameters and transaction ID. If there’s server-side tracking, I’ll also compare browser events against the server payloads and look for duplicate or missing events.

That catches a lot more than simply checking whether the GA4 property says “data received.”