Why Your Conversion Tracking Is Inaccurate (And How to Fix It)

Inaccurate conversion data is one of the most expensive problems in Google Ads: campaigns keep spending, but bidding and optimization learn from the wrong signal.

This page is intentionally action-oriented: identify the symptom pattern, map it to the likely cause (consent, duplicates, attribution differences), and verify with a scan + test.

Symptoms (what you see)

• GA4 vs Ads mismatch: GA4 shows conversions but Ads is lower (or 0)
• Sudden drops: conversions fall after a CMP/theme/tag update
• Inflated conversions: duplicates or double-counting across tags/actions
• Unstable reporting: some users track, others don't (often consent/state related)

If GA4 shows conversions but Ads doesn't, start with GA4 conversions not showing in Google Ads.

Why it happens (common causes)

• Consent Mode issues: defaults/updates wrong; tags fire before consent or never get permission
• Duplicate tags: multiple conversions fire for one action (GTM + gtag, multiple containers, duplicated rules)
• Attribution differences: different models/windows/definitions between GA4 and Ads
• Missing signals: gclid/click IDs lost; cross-domain; redirects strip parameters

For the full framework of failure paths, read why Google Ads conversions break.

Fix checklist

1. Verify consent behavior: test first visit → reject → accept; confirm updates are sent and timing is correct
2. Eliminate duplicates: ensure the conversion fires once per action; audit multiple tags/containers/actions
3. Validate attribution configuration: compare windows/models and "include in conversions" settings
4. Test end-to-end firing: ensure the conversion request includes expected identifiers and fires consistently