Why Google Ads Conversions Break (And Why It’s Hard to See)
Google Ads conversion tracking rarely fails because of one obvious mistake. In most cases, ads keep running, traffic keeps coming in, and leads or purchases still happen - but conversion data quietly stops flowing back to Google.
This is what makes the problem dangerous. Everything looks fine on the surface, but Google Ads is optimizing on incomplete or missing signals. Budgets get wasted, performance drops, and nobody can explain why.
The root cause is almost always the same: consent, timing, or tracking configuration issues that are invisible unless you know exactly where to look.
Check What’s Breaking Your Conversion Tracking
Run a free diagnostic scan to see exactly where consent or tracking is breaking Google Ads measurement on your site.
Run Free Scan →The 4 Ways Google Ads Conversions Break
After analyzing many broken setups, most Google Ads conversion issues fall into one (or more) of these categories:
In some cases, conversion discrepancies are caused by attribution differences rather than broken tracking.
Note: Across dozens of live scans, we've found that most sites fire tracking before consent - even when a banner is present. These aren't theoretical issues; they're measured problems in production websites.
1. Tracking Fires Before Consent
Google tags load immediately, before users grant consent. Requests get blocked or downgraded, and conversion signals never reach Google.
Learn more →2. Consent State Never Updates
Users click “Accept,” but Consent Mode is never updated. Google continues to treat users as non-consented, blocking modeling and conversions.
Learn more →3. Consent Mode v2 Is Missing or Misconfigured
Consent Mode v2 is required for proper conversion modeling and is strongly recommended for modern Google Ads setups. Many sites think they have it, but key parameters are missing or loaded too late.
Learn more →4. Conversions Fire, But Aren’t Attributed
Forms submit, purchases complete, but conversions fire before consent or without proper linkage - so Google Ads may not credit the campaign.
Learn more →How Conversion Tracking Actually Breaks (Step-by-Step)
Most conversion issues are not caused by missing tags, but by the sequence of events between page load, consent, and conversion firing. This is the simplified flow Google Ads expects - and where things usually fail.
Flow breakdown: The conversion tracking process starts when a user clicks a Google Ad and lands on your website. After the consent banner loads, tracking must not fire before consent is granted (otherwise requests are blocked). If Consent Mode v2 is present and consent state is properly updated when users accept, tracking scripts load and conversion events can fire successfully. Missing any step results in lost, suppressed, or ignored conversions.
Note: This diagram shows the client-side flow. With server-side tracking (e.g. Stape, GTM Server-Side), conversions may be sent from your server to Google Ads and won't appear in the browser - the flow above doesn't apply the same way.
Consent Mode v2: With Consent Mode v2, Google may load tags in an anonymized state before consent (cookieless pings). Our scan distinguishes these from actual tracking payloads and does not treat anonymized pings as "tracking before consent."
This is why conversions can fire in GA4 or GTM preview but never appear in Google Ads. Ads requires valid consent, timing, and attribution signals - all at the same time.
Note: Google Ads reporting delays and attribution windows are not considered tracking failures.
This is exactly what the diagnostic report highlights, with concrete fixes. View sample report →
What About Server-Side Tracking?
If you use server-side Google Tag Manager (e.g. Stape, GTM Server-Side), conversions may be sent directly from your server to Google Ads. They won't appear in the browser, so the client-side flow above doesn't apply the same way. That's expected and valid.
Our scan detects server-side setups and adjusts: we don't flag "no conversion observed" as a failure when server-side tracking is detected, and we explain in the report that conversions may be sent from the server. We also check whether consent is properly propagated to the server (e.g. do server-bound requests change after accept vs reject).
For a full guide on server-side GTM and Consent Mode v2 (what changes, how consent must propagate, common Stape mistakes, and how to verify), see our Server-Side GTM + Consent Mode v2 setup guide.
How the consent scan works → (including server-side detection and consent propagation).
Consent Banners Are Often the Hidden Culprit
Many sites technically have a consent banner, but it doesn’t actually block tracking or update consent states correctly. This creates silent measurement failures that are hard to detect.
Why GA4 Often Looks “Fine” While Ads Are Broken
One of the most confusing scenarios is when GA4 appears to work, but Google Ads shows zero or partial conversions.
This happens because GA4 can record events locally or in debug mode, while Google Ads requires properly consented, attributable signals to optimize campaigns.
Read why GA4 and Google Ads often disagree →How to Diagnose and Verify Your Setup
The hardest part isn't fixing Google Ads conversion tracking - it's knowing what's actually broken. Manual checks miss timing issues, consent state mismatches, and blocked requests. Here are step-by-step guides to verify your setup:
Manual Verification Guides
- How to Check Google Consent Mode v2 (Step-by-Step) →
Learn how to manually verify Consent Mode v2 in DevTools, dataLayer, and network requests.
- How to Test Google Ads Conversion Tracking After Consent →
Step-by-step guide to verify conversion tracking works correctly after users accept consent.
- Why Google Ads Shows 0 Conversions But GA4 Shows Events →
Understand why conversions appear in GA4 but not in Google Ads, and how to diagnose the issue.
💡 A diagnostic scan simulates real user consent flows and shows exactly where tracking breaks.
Run Free Scan →FAQ
- Why do Google Ads conversions stop tracking?
- Usually consent, timing, or configuration: tracking fires before consent, Consent Mode defaults are wrong, or the consent update never runs. Ads keep running but conversion data stops flowing to Google.
- Can Google Ads run while conversion tracking is broken?
- Yes. Ads and traffic continue; the break is in measurement. Google may use modeled conversions or incomplete data, so optimization degrades without an obvious error.
- How do I check if my site has consent or tracking issues?
- Run a browser-based scan that simulates first visit, reject consent, and accept consent. Check whether tracking fires before consent and whether Consent Mode v2 is set correctly. Our free scan does this.
- What are the main ways conversions break?
- Tracking before consent, consent state not updating when users accept/reject, Consent Mode v2 misconfigured (e.g. default not denied), and cookie banner parity (Accept and Reject doing the same thing).
Deep dives: