GA4 and Google Ads will not match perfectly, even in a well-run setup. The useful job is to separate expected structural differences from the implementation issues that are large enough to affect bidding, reporting, or budget decisions.
Some discrepancy is normal
GA4 and Google Ads do not measure conversions in the same way or from the same vantage point.Attribution settings, counting methods, view-through behavior, consent-mode effects, imported conversions, and click identifiers all influence the final numbers.
That means the question should not be "why are these two systems different at all?" The better question is whether the difference is stable and explainable, or whether it changed after a tagging, redirect,consent, or import configuration problem. When the gap widens suddenly, suspectauto-tagging or UTM override conflictsfirst, then check whetherclick-identifier handlinghas changed across destinations.
Check model and lookback settings before assuming data loss
Review GA4 key event counting and Google Ads conversion settings
Confirm imports, auto-tagging, and duplicate tags are behaving correctly
Why the two systems differ
Confirm the platforms are linked correctly
Review the Google Ads link in GA4 and the imported conversion setup in Google Ads. If the wrong key events were imported, or the link is inactive, every later comparison will be misleading.
Review counting methods in both places
Google documents that GA4 key events can use different counting methods, and Google Ads conversion actions can also use different count settings. Compare those deliberately before you compare totals.
Check attribution settings and windows
Look at property attribution settings in GA4 and conversion-action settings in Google Ads. Even when both use data-driven attribution, they may not be operating on the same assumptions or eligible touchpoints.
Validate auto-tagging and landing-page behavior
If gclid is stripped by redirects, broken routing, or page logic, Google Ads traffic can be harder for GA4 to classify correctly. Test the final landing flow, not just the ad URL template.
Review consent-aware and duplicate-tag scenarios
If Consent Mode or Enhanced Conversions are involved, or if separate Google Ads tags and GA4 imports coexist, document exactly how each path contributes to the final count before drawing conclusions.
GA4 vs Google Ads discrepancy action plan
Validate
- Confirm the GA4 property link and imported conversion setup are active and intentional
- Review key event counting in GA4 and conversion count settings in Google Ads
- Compare attribution settings and lookback logic before investigating reporting anomalies
- Test whether auto-tagging identifiers survive the real landing-page flow
- Check whether separate Google Ads tags and imported GA4 conversions overlap
Fix
- Correct the imported conversion selection so Google Ads uses the intended GA4 key events
- Align counting and attribution settings where a closer comparison is needed
- Repair redirects or landing behavior that drops gclid or breaks session attribution
- Remove duplicate conversion paths when the same action is being measured twice
- Document known structural differences so reporting teams stop treating them as unexplained errors
Watch for
- Discrepancies that change sharply after a GTM, landing-page, or consent deployment
- Conversion imports that are technically active but mapped to the wrong website action
- Google Ads traffic arriving without a surviving click identifier
- Stakeholders comparing platform totals without checking whether they represent the same conversion logic
Related guides to read next
GA4 attribution models explained
The attribution context needed before you compare Google Ads numbers to GA4 reporting.
GA4 conversion tracking setup
How to verify the website-side key events that may later be imported into Google Ads.
GA4 source / medium changed to Direct
A common debugging path when click identifiers or landing-page attribution break down.
Ready to audit your GA4 property?
Run a full GA4 audit in under 2 minutes. Free to start.