Conversion tracking not working? How to spot it in hours

When conversion tracking is not working, the ads rarely look broken: clicks and sessions hold steady while conversions fall toward zero, or step down on the same day in every campaign. That pattern points to the site or the tags, not the ads. Confirm it within the hour: complete a test conversion, watch it in Tag Assistant or Events Manager, and compare platform conversions with your orders or leads.

Key takeaways

• Tracking breaks are silent, and automated bidding learns as if the unrecorded conversions never happened.
• A drop that starts on the same day in every campaign and every platform is almost never the ads.
• Your own orders or leads are the fastest test: if they held, only the measurement failed.
• While you fix it, protect Smart Bidding with a data exclusion instead of changing targets or budgets.

Why is broken conversion tracking so expensive?

Because nothing tells you it broke, and everything downstream keeps acting on the wrong numbers. The ads keep serving, the budget keeps spending and the platform shows what looks like a performance collapse.

Automated bidding, whether Smart Bidding in Google Ads or Meta’s delivery optimizing to a conversion event, sees conversions vanish and adjusts: it can bid down, leave auctions that worked or shift spend to whatever still records conversions. You follow the same bad data and cut budgets or pause ads that were working.

The fix is usually small: a trigger, a URL, a consent setting. The cost is the delay: a day of bad data if found the next morning, weeks if found at the monthly report.

What does broken conversion tracking look like in the data?

It leaves one of four signatures in your daily clicks, sessions, conversions and conversion value.

Hard break: conversions fall to zero

Clicks and sessions hold while conversions fall to zero or near it, in every campaign on the same day. It is the signature of a tag that stopped firing or a thank-you page that moved.

Partial break: conversion rate steps down

Conversion rate drops in one clear step, not a slide, and stays there. If every campaign stepped down on the same day, the cause is on the site: an action stopped, a form lost its tag, or a consent change reduced what tags record. If only one campaign stepped down, look at its landing page, final URL or conversion goal.

Duplication: conversions jump

Conversions jump on steady clicks, to a conversion rate the account has never had. Value per conversion tells you why. If the same purchase is counted twice, conversions and value double together and value per conversion stays flat. If a new action without a value, such as a page view, became a conversion, value per conversion falls.

Divergence: the platforms and the site disagree

Ad platforms, GA4 and your backend never match exactly, since each has its own attribution, windows and dates. What matters is whether they move together: when Google Ads conversions hold while GA4 key events fall, or the reverse, measurement changed on one side.

The same-day, every-campaign rule

A drop that starts on the same day in every campaign and every platform is almost never the ads. Google Ads and Meta run separate auctions for different audiences and do not lose buyers on the same Tuesday in the same proportion; what they share is your site and its tags. The exceptions are real events on the site, such as an outage or a failing checkout, and your backend separates them: if orders fell too, the drop is real.

Pattern	Likely cause	Where to check
Clicks steady, conversions near zero everywhere from one day on	Tag removed or not firing; new thank-you URL	Conversion action status; Google Tag Manager versions; a test conversion
Conversion rate steps down the same day everywhere	Site-wide change: a form lost its tag, a consent change	Backend vs platform by day; segment by conversion action
Ads steady, GA4 or backend falling, or the reverse	Tracking changed on one side	GA4 Realtime and DebugView; Events Manager
Meta conversions fall, Google Ads steady	Pixel or Conversions API problem	Events Manager: event activity and Test events

What usually breaks conversion tracking?

Usually a change made for another reason, often by someone who never opens the ad account.

• A Google Tag Manager publish or a site cleanup that removed a tag or pixel, renamed a trigger or changed a variable the conversion tag needs.
• A new thank-you URL. A conversion that fires on a page URL stops the day that URL changes.
• A form or checkout plugin update that replaces the confirmation page with an inline message or changes the events the tag listens for.
• A consent banner or Consent Mode change that reduces what tags record.
• A domain change, or a checkout or booking step moved to another domain the tag or click identifier doesn’t follow.
• Expired server-side access. Meta’s Conversions API, offline conversion imports and other server connections stop when a token expires or whoever set them up loses access.
• An edited conversion action: switched to secondary, recounted or replaced. Nothing broke on the site, but the numbers move as if it had.

How do you confirm tracking is broken in under an hour?

Check your backend first, then reproduce a conversion yourself and see where it stops.

1. Compare with the backend. Count orders or CRM leads for each day since the drop: if they held, tracking failed; if they fell too, the problem is real.
2. Find the action that went quiet. In Google Ads, segment by conversion action and check each action’s status in the conversions summary; in Meta, check each event’s activity in Events Manager.
3. Complete a test conversion with Google Tag Assistant connected, or Google Tag Manager in Preview mode, and check that the conversion tag fires on the confirmation step with the right value. Without an ad click, the test won’t appear as a Google Ads conversion: you are checking the tag, not the column.
4. Watch it arrive. GA4’s Realtime report and DebugView show whether the event reaches the property; Test events in Events Manager shows whether Meta’s pixel and Conversions API receive it.
5. Find what changed that day in the Google Tag Manager version list, the site’s release or plugin log and Change history in Google Ads.

Worked example: the Tuesday conversions stopped

Example: a lead generation account runs three Google Ads campaigns on $1,200 a day. On a Tuesday, with clicks steady, conversions fall from about 40 a day to 3.

Campaign	Clicks per day	Conversions before (rate)	From Tuesday (rate)
Search – Brand	300	15 (5.0%)	1 (0.33%)
Search – Generic	500	15 (3.0%)	1 (0.20%)
Performance Max	400	10 (2.5%)	1 (0.25%)
Total	1,200	40 (3.33%)	3 (0.25%)

Conversion rate before: 40 ÷ 1,200 clicks = 3.33%
Conversion rate after: 3 ÷ 1,200 clicks = 0.25%

CPA before: $1,200 ÷ 40 = $30
CPA reported after: $1,200 ÷ 3 = $400

Every sign points to tracking: three campaign types with different audiences fell by 90% or more on the same day, while clicks and GA4 paid sessions held.

The checks take twenty minutes. The CRM shows 39 leads on Tuesday, a normal day. The three remaining conversions are calls from ads; the form action has recorded nothing since Tuesday morning. A form plugin update on Monday night now sends people to /thanks/ instead of /thank-you/, and the trigger only matched URLs containing “thank-you”.

The fix is one trigger condition. The cost is the delay: two weeks unnoticed means 14 × $1,200 = $16,800 of spend judged on a $400 CPA instead of $30, by you and by Smart Bidding.

What should you do with bidding while you fix it?

Fix the tag, then tell automated bidding to ignore the broken days, and leave targets, budgets and structure alone in the meantime.

Smart Bidding learns from recent conversion data. Seeing conversion rate fall by more than 90%, it can treat your traffic as worth less, and the effect can outlast the fix. Google Ads’ data exclusions, set up with your bid strategies, tell Smart Bidding to ignore conversion data from the dates when tracking was wrong. They don’t restore conversions in reports; they keep those days out of bidding.

• Don’t pause campaigns that still convert. If the backend shows normal orders or leads, pausing cuts real revenue over a reporting problem. Pause only if the site itself is broken.
• Avoid edits that restart learning. On Meta, significant edits send an ad set back into the learning phase, which needs about 50 optimization events within 7 days after the last significant edit to exit.

How do you catch the next break in hours, not weeks?

Check conversion rate by campaign every day, against each campaign’s own normal, and watch for a step that starts on the same day in several campaigns.

A monthly report turns a two-week break into a “weak month”. A daily check catches it the next morning, if each campaign is compared with its own history: a brand campaign at 5% and a generic one at 3% each have their own normal. Add a weekly check of platform conversions against backend orders or leads, and ask the site team to warn you before they publish.

In Google Ads, Borealis does this every day: it compares each campaign’s conversion rate with its own normal and flags a break in the next morning’s email, once there is enough volume to trust the rate. Checking ad conversions against GA4 key events, to catch divergence, is coming soon with GA4 monitoring.

If the drop turns out to be real, see the guide to a sudden drop in Google Ads conversions for volume, traffic and landing page causes, and why your CPA went up for the cost side.

Frequently asked questions