Anomaly Detection GA4 & Analytics Google Ads

How to detect broken conversion tracking

April 22, 2026 · 9 min read

Broken conversion tracking means your ad platforms are spending money without knowing what works. When a pixel stops firing or a conversion event disappears, Smart Bidding loses its optimisation signal, attribution data becomes unreliable, and budget gets wasted on campaigns that appear to have stopped converting, even when the underlying business is fine. The fastest way to detect it is to monitor conversion counts continuously and alert when they deviate from their expected pattern.

Broken conversion tracking means your ad platforms are spending money without knowing what works. When a pixel stops firing or a conversion event disappears, Smart Bidding loses its optimisation signal, attribution data becomes unreliable, and budget gets wasted on campaigns that appear to have stopped converting, even when the underlying business is fine. The fastest way to detect it is to monitor conversion counts continuously and alert when they deviate from their expected pattern.

Why does conversion tracking break?

Conversion tracking is fragile by design. It depends on a chain of components, tags, consent layers, browser APIs, platform configurations, and a failure in any single link breaks the entire chain. These are the most common causes, roughly in order of frequency.

Site redesigns and CMS migrations

This is the single most common cause of broken tracking. When a site moves from one CMS to another (WordPress to Shopify, for example), or when a developer rebuilds a checkout flow, tracking tags are frequently left behind. The new pages load a fresh template that does not include the Google Tag Manager container, the Meta pixel, or the Google Ads conversion snippet. Everything else on the site works fine, so the breakage is invisible to everyone except the marketing team, and usually only when they check the data days later.

Tag manager changes and conflicts

Google Tag Manager is powerful but fragile at scale. A common failure mode: a developer publishes a new GTM container version that overwrites or disables a conversion tag. Another: two GTM containers load on the same page and conflict, causing one or both to fail silently. A third: a trigger condition is changed (e.g., "fire on all pages" becomes "fire on pages matching /checkout/") and the conversion tag no longer fires on the actual conversion page because the URL pattern does not match.

iOS and browser privacy updates

Apple's App Tracking Transparency (ATT), introduced with iOS 14.5 in 2021, significantly reduced the ability of the Meta pixel to track conversions from iOS devices. Safari's Intelligent Tracking Prevention (ITP) limits cookie lifetimes, which affects attribution windows. Firefox and Brave block third-party tracking by default. Each browser and OS update can further erode tracking coverage. These are not sudden breaks, they are gradual, cumulative losses that show up as a steady decline in reported conversions even when actual business outcomes have not changed.

With GDPR and ePrivacy regulations, most European sites now use a Consent Management Platform (CMP) to collect user consent before firing marketing tags. When consent mode is misconfigured, for example, when the CMP blocks Google Analytics or Meta tags even after consent is granted, or when the default consent state is set to "denied" and the update never fires, tracking drops to zero or near-zero for affected users. Google's Consent Mode v2 (required since March 2024 for EEA traffic) adds another configuration layer that can fail silently.

Pixel removal or ID changes

It sounds too simple to be common, but it happens regularly: someone removes the Meta pixel code during a site cleanup. Or a Google Ads conversion action is deleted and recreated with a new ID, but the tag on the site still references the old ID. Or an agency loses access to a client's Google Ads account and the conversion action is recreated under a different account, invalidating the existing tag. The tag fires, but the platform does not recognise the event because the pixel ID or conversion action ID no longer matches.

Server-side and API tracking failures

As client-side tracking has become less reliable, many teams have moved to server-side tracking via the Conversions API (Meta), Google Ads Enhanced Conversions, or GA4 Measurement Protocol. These are more robust but introduce new failure modes: API keys expire, server endpoints change, data formatting errors cause events to be silently rejected, and server-side deduplication logic can miscategorise events. When server-side tracking breaks, there is no browser console error to debug, the failure is only visible in the conversion count data.

How do you detect a broken pixel manually?

Manual detection works, but it requires discipline and time. Here are the standard tools and the process for each.

Google Tag Manager Preview and Debug mode

GTM's Preview mode lets you browse your site and see which tags fired (and which did not) on each page. For conversion tracking, navigate to the conversion page (e.g., the thank-you page after a purchase) and confirm that the Google Ads conversion tag, the GA4 purchase event tag, and the Meta pixel purchase event all fired. Check the trigger conditions and the data layer values to ensure the correct transaction data is being passed. This is the most reliable manual method but requires access to GTM and a real (or simulated) conversion to test.

GA4 DebugView

GA4's DebugView shows events arriving in real time from devices with debug mode enabled. Install the Google Analytics Debugger Chrome extension, enable debug mode, and complete a conversion on your site. If the conversion event (e.g., purchase, generate_lead) appears in DebugView with the correct parameters, GA4 tracking is working. If it does not appear, the event is not firing or is being blocked.

Meta Events Manager and Test Events

Meta's Events Manager shows pixel events received in the last 24 hours. The Test Events tab lets you send test traffic and confirm events arrive in real time. If your Meta pixel is firing, you will see events appear within seconds. If not, check the pixel helper Chrome extension for errors on the page.

Google Tag Assistant

The Google Tag Assistant (now part of the Tag Assistant Companion extension) validates Google tags on any page. It shows whether the Google Ads conversion tag, GA4 tag, and Google Ads remarketing tag are present and firing correctly. It also flags configuration issues like duplicate tags or mismatched IDs.

Checking platform conversion counts

The simplest manual check: log into Google Ads, Meta Ads Manager, or GA4 and look at conversion counts for the last 7 days. Compare to the previous 7 days and the same period last month. If conversions have dropped significantly and there is no corresponding change in traffic, spend, or business operations, tracking is likely broken. This works, but it requires someone to remember to check, to check each platform separately, and to know what the expected conversion count should be.

The problem with manual detection is not that it doesn't work, it's that it depends on someone doing it. In practice, teams check after a client complains, after a monthly report reveals the damage, or after someone happens to notice a zero in a dashboard. By then, days or weeks of data have been lost.

How do you detect a broken pixel automatically?

Automatic detection solves the discipline problem. Instead of relying on a human to check conversion counts regularly, a monitoring system watches them continuously and alerts when something deviates from the expected pattern.

Anomaly detection on conversion counts

The most effective approach is to apply anomaly detection directly to conversion count data. The system ingests 30-90 days of historical conversion data for each platform and builds a baseline that accounts for day-of-week patterns, trends, and natural variance. Each day (or more frequently), it compares the live conversion count against the expected range. When conversions fall below the lower bound, for example, when a metric that normally records 40-60 daily conversions suddenly records 3, the system triggers an alert.

This method catches complete tracking failures (conversions drop to zero) and partial failures (conversions drop by 50% because tracking breaks on mobile but not desktop, or on one browser but not others). It also catches gradual degradation from privacy changes or consent mode issues, where conversion counts decline over weeks rather than collapsing overnight.

Cross-platform correlation

A more advanced detection method is to monitor the same conversion event across multiple platforms and alert when they diverge. For example, if GA4 records 50 purchases but Google Ads records 2, the discrepancy strongly suggests a Google Ads tracking issue rather than a genuine business change. Similarly, if Shopify records orders but GA4 shows no purchase events, the GA4 tag is likely broken. Go Insights monitors multiple platforms simultaneously, which makes this kind of cross-reference possible without manual comparison.

Why monitoring beats manual checks

The advantage of automated monitoring is speed and consistency. A monitoring tool checks every platform, every account, every day, it does not take holidays, forget to check, or get distracted by other priorities. When a site redesign breaks the Meta pixel on a Friday afternoon, the tool alerts within hours rather than on Monday morning (or the following Monday, or the end of the month). For agencies managing 10-50 client accounts, the difference between catching a tracking break on day one and day seven is often thousands of dollars in wasted spend and weeks of lost attribution data.

What should you check when conversions drop?

When you receive an alert (or notice) that conversions have dropped, work through this checklist before assuming the worst. Not every conversion drop is a tracking problem, some are genuine business changes.

1. Is the tag still on the page?

Open your conversion page (checkout confirmation, thank-you page, lead form success page) in Chrome with the GTM Preview panel or Meta Pixel Helper active. If the tag is not present on the page, check whether the page template changed, whether GTM is still loading, or whether a CMS update removed the container snippet.

2. Is it firing on the correct page?

Tags can be present on the site but not firing on the right page. Check that the trigger in GTM matches the current URL of the conversion page. A common issue: the URL changed from /checkout/thank-you to /order-confirmation and the trigger still looks for the old path.

If you are using a CMP, check whether the tag is being blocked by consent mode. Open the browser console and look for consent-related messages. Check whether the CMP is correctly updating consent state after the user accepts. Test with consent granted to see if the tag fires normally. If it does, the issue is consent configuration, not the tag itself.

4. Is it one device or browser?

Check conversion data by device (mobile vs. desktop) and by browser. If conversions dropped only on iOS, an ATT or ITP change may be responsible. If conversions dropped only on Chrome, a Chrome extension conflict or an update to Chrome's tracking prevention may be involved. If conversions dropped on all devices and browsers equally, the issue is more likely a tag removal or server-side failure.

5. Did anything change on the site?

Ask the development team whether any deployments happened in the 24 hours before conversions dropped. Check the GTM container version history for recent publishes. Check the CMS for theme or plugin updates. In the majority of cases, the tracking break correlates with a specific deployment or configuration change, finding that change tells you exactly what to fix.

6. Is the conversion action still active in the platform?

In Google Ads, check that the conversion action is still listed under Tools > Conversions and that it has not been removed, paused, or replaced. In Meta, check that the pixel ID in your tag matches the pixel ID in Events Manager. Mismatched IDs are a common cause of zero-conversion scenarios where the tag appears to fire correctly but no conversions are recorded.

7. Is it actually a tracking problem?

Not every conversion drop is broken tracking. Check your ecommerce platform (Shopify, WooCommerce, etc.) or CRM for actual orders/leads during the affected period. If real business outcomes also dropped, the cause is upstream: reduced traffic, a broken checkout, a pricing error, or a campaign that stopped serving. If real outcomes are stable but reported conversions dropped, tracking is almost certainly the problem.

Frequently asked questions

How quickly can you detect broken conversion tracking?

It depends on your conversion volume. For accounts recording 20 or more conversions per day, anomaly detection can reliably flag a tracking break within 24 hours. For lower-volume accounts (fewer than 5 conversions per day), it may take 2-3 days before the deviation is statistically significant. Manual checks using GTM Preview mode or Meta Events Manager can confirm a break in minutes, the challenge is remembering to check.

Can broken tracking affect Smart Bidding?

Yes, significantly. Smart Bidding strategies like Target CPA and Maximize Conversions rely on conversion data to optimise bids. When conversion tracking breaks, Smart Bidding has no signal and typically enters a learning period. During this time, CPCs can spike as the algorithm searches for signals, or the campaign may reduce spend dramatically because it has no data to bid on. Restoring tracking does not immediately fix bidding, expect 1-2 weeks of learning period after the fix.

Does server-side tracking eliminate tracking breaks?

Server-side tracking (Meta Conversions API, Google Ads Enhanced Conversions, GA4 Measurement Protocol) is more robust than client-side tracking because it does not depend on the browser, cookies, or consent managers. However, it introduces its own failure modes: API keys can expire, server endpoints can change, and data formatting errors can cause events to be silently rejected. Server-side tracking reduces the frequency of breaks but does not eliminate them, monitoring is still necessary.

What percentage of ad spend is wasted due to broken tracking?

There is no universal number, but industry surveys suggest that 5-15% of advertisers have at least one tracking misconfiguration at any given time. For individual accounts, the cost depends on how long the break goes undetected. A $500/day account with broken tracking for 7 days before detection wastes approximately $3,500 in unattributed spend, plus the indirect cost of Smart Bidding degradation, which can persist for weeks after the fix.

Should I set up both client-side and server-side tracking?

Yes, if your technical setup supports it. Running both provides redundancy: if client-side tracking breaks due to a CMS change or consent issue, server-side tracking continues to record conversions. Most platforms (Meta, Google) support deduplication so events are not double-counted. The combination also gives you a built-in cross-check, if client-side and server-side counts diverge significantly, one of them is broken.

Try Go Insights on your data

Set up in 5 minutes. No credit card required.

Start free