Google Ads Conversions Not Tracking? (Fix Consent & Tracking Issues Fast)

This is one of the most expensive tracking issues in Google Ads. Campaigns keep spending — while conversions are underreported or lost.

If your Google Ads conversions suddenly stopped tracking — your setup is broken.

And the worst part?

Ads keep running while data silently fails:

Google optimizes on wrong signals
Budget gets wasted
Performance drops without explanation

This is what makes the problem dangerous.

Most sites don't realize tracking is broken until performance drops.

Check your setup now:

Diagnose My Tracking →

This is usually caused by consent mode, timing, or attribution issues.

You can debug it manually below — or instantly check your setup:

🔍 Run Free Tracking Scan →

If your Google Ads conversions are not tracking, this is usually caused by consent mode issues, timing errors, or broken attribution signals — not missing tags.

Quick Summary

Google Ads conversions break when:

Tracking fires before consent
Consent state does not update
Consent Mode v2 is missing or misconfigured
Attribution signals are incomplete

Even when ads run normally, conversion data may be missing or modeled incorrectly.

Find exactly why your conversions aren't tracking

Scan your site and detect:

Broken conversion tags
Missing consent signals
Attribution issues blocking Google Ads

🔍 Run Free Scan →

Core guides

How to Check If Google Ads Conversion Tracking Is Working

To check if Google Ads conversion tracking is working:

Open DevTools (Network tab)
Trigger a conversion (form submit or purchase)
Check if a request is sent to Google Ads
Verify consent was granted at that moment
Confirm Consent Mode v2 is active

If any of these fail, conversions may not be recorded. For deeper manual testing, use this conversion tracking test guide.

Manual checks often miss timing and consent issues.

Run a scan to verify everything automatically:

Check My Tracking →

Can Google Ads Track Conversions Without Cookies?

Yes. With Consent Mode, Google Ads can model conversions when cookies are not available.

These are modeled conversions, not fully observed conversions
Accuracy depends on consent signals and implementation quality
Poor setup can make numbers look plausible but unreliable

This is why tracking can appear to work while attribution quality is still broken. Read the full breakdown: Google Ads conversion tracking without cookies.

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.

If your setup was previously stable, consent mode may have stopped working after an update.

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. We fixed a 40% conversion drop from consent never updating. See our case study.

In audits, this is one of the most common hidden issues: campaigns appear to perform, but conversion data is incomplete due to consent or timing problems.

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 why tracking fires before consent (this breaks conversions) →

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.

Check if your consent state is not updating →

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.

Check your Consent Mode v2 setup →

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.

See why conversions fire but aren't attributed →

One of these is likely affecting your site.

Find out which one in seconds:

Run Free Diagnostic →

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 →

For a deeper explanation of how modeled signals behave, see how conversion modeling works.

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.

Find What's Broken →

Unsure whether conversions are fully tracked or partially modeled?

If you're unsure whether your conversions are fully tracked or partially modeled, run a scan to see exactly what's happening across consent states.

Check My Setup →

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: