Conversions dropped overnight. How do I tell if it's a tracking break or a real drop in demand?
Look at the shape of the drop and check a signal that does not depend on your tracking. A tracking break is usually instant, near-total, and confined to one conversion action or one channel while sessions, phone calls and booked jobs continue normally. A real demand drop is gradual, shows up proportionally across channels, and is visible on the schedule board too.
The shape of the drop does most of the diagnostic work
Demand moves like weather. It slopes. It has weekly seasonality, it responds to temperature and to competitors, and it almost never falls off a cliff on a Tuesday afternoon for one campaign while everything else holds.
Measurement breaks look different. They start at a specific hour, they take one metric to zero or near zero, and they usually correspond to something a human did: a site deploy, a consent banner update, a tag container publish, a template change on the thank-you page. If you can draw a vertical line through the chart and it lines up with a change log entry, you have your answer before you look at anything else.
Check something that lives outside the tag
The fastest confirmation is an independent count. Your phone system knows how many calls came in. Your field service software knows how many jobs were booked. Your inbox has the form notification emails. None of those depend on the browser tag that may have broken.
If those independent counts held steady while reported conversions collapsed, you have a measurement problem, not a business problem. If they fell together, the business problem is real and the tag is fine. This is the same reconciliation discipline that integration work exists to provide, and it is why an operational system of record matters more than a dashboard.
The usual suspects, roughly in order
- A deploy dropped the tag. New page template, new thank-you URL, or a caching layer serving an older head section.
- The consent banner changed. A new default or a new vendor category can silence tags for a large share of visitors overnight.
- The conversion action was edited. Someone changed the counting setting, the attribution window, or marked the action as secondary.
- A redirect started stripping parameters. Traffic still arrives, but the click identifier does not, so nothing can be matched back.
- The number pool ran dry. Call tracking hands out a fallback number that belongs to no session, and those calls stop being attributed.
Build the alarm before the next one
The durable fix is a daily comparison of platform-reported conversions against the count of records actually created in your CRM, expressed as a ratio. Ratios are far more sensitive than raw counts because they hold steady through seasonality and break loudly when plumbing fails.
We wire that comparison into daily intelligence briefs so a broken tag surfaces as a sentence the next morning rather than as a bad month at the quarterly review. Anything you only look at monthly, you will discover a month late.
Topics: diagnostics · tracking · conversions · tag management
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.