GA4 Conversions Not Showing in Google Ads? Fix Tracking & Consent Issues Fast

If GA4 shows conversions but Google Ads shows 0, you are likely losing attributed conversions, and your campaigns may be optimizing on incomplete data.

This usually means something is broken in consent, tagging, or attribution signals.

The fastest way to see where tracking fails (before manual guesswork):

Run Free Scan →

Prefer the full story first? Why GA4 and Ads disagree →

1) Identify your case

GA4 shows conversions, but Google Ads shows 0.
GA4 shows conversions, but Google Ads shows partial / inconsistent conversions.
Google Ads shows conversions, but attribution/values are wrong.

Once you know your case, use the decision tree below to isolate where the pipeline breaks.

Not sure which case you're in?

Run a scan and see exactly where your tracking breaks across consent states (first visit, reject, accept).

🔍 Run automated consent & tracking check →

2) Decision tree (fast)

IF conversions fire in GA4 but NOT in Ads → likely consent / attribution issue.
IF there is no Google Ads conversion request at all → implementation / trigger issue.
IF a request exists but Ads shows 0 / no attribution → consent signals / labeling issue.

3) Root causes (most common)

Consent not updating: consent state not updating. Wrong or missing Consent Mode v2 behavior is a top cause, verify defaults, updates, and timing with the full check.
Missing gclid: Ads can't attribute without click IDs in many flows. Test whether gclid survives your landing URL and redirects.
Snippet / defaults wrong: If default denied + update wiring is off, GA4 can still show activity while Ads never gets attributable hits.
Tag firing too early: tracking before consent
Wrong conversion label: request fires but maps to the wrong (or no) conversion action.
Cross-domain issues: consent and click IDs don’t persist across domains/subdomains, so Ads attribution breaks.

4) How to verify (manual)

Use the manual verification guide to test conversion requests and consent state across first visit, reject, and accept.

Step-by-step Google Ads conversion tracking test →

Manual debugging can miss issues, especially consent timing, payload gaps, and what happens before vs after Accept.

Run an automated scan to detect problems across first visit, reject, and accept states, the same flow your real users hit.

Even small tracking issues can lead to underreported conversions, which directly impacts bidding and campaign performance.

In many cases, this results in wasted ad spend or incorrect optimization signals, while dashboards still show "some" activity in GA4.

5) Fixes (what to change)

Fix the consent update call (Accept must trigger a real update). If it doesn’t, start with consent update troubleshooting.
Fix GTM triggers so conversion tags do not fire before consent and do fire after accept.
Fix tagging/labels: ensure the conversion label matches the correct Google Ads conversion action.
If server-side is involved, verify propagation using Server-side GTM + Consent Mode v2.

6) Run a scan (fastest, obvious next step)

If you're not 100% sure which state the browser is in (first visit vs reject vs accept) while conversions fire, manual debugging becomes unreliable. Our scan simulates those states and compares behavior automatically, so you see failures before you trust another dashboard number.

Want a full breakdown of what's wrong + exact fixes?

Generate a detailed report for your setup, concrete findings and next steps you can hand to dev or agency.

Run Free Scan →