Are Google Ads and GA4 telling you different stories?

Google Ads and GA4 use fundamentally different attribution architectures — Google Ads is click-centric and attributes conversions to the date of the ad click using Google's logged-in identity graph, while GA4 is event-centric and attributes to the date of the conversion event using cookie-based session data. Google Ads can count every conversion from a single click (multiple purchases), includes view-through and modeled conversions by default, and uses cross-device matching via Google sign-in data that GA4 cannot access. The result is that Google Ads consistently reports 15–50% more conversions than GA4 in most accounts. The Tracking Mismatch Audit splits your discrepancy into its structural components (view-through, cross-device, modeled, timing) so you can see which cause is driving your specific gap.

Five structural causes: (1) timing — Google Ads attributes on click date, GA4 on conversion date; (2) view-through — Google Ads counts view-throughs by default, GA4 does not; (3) cross-device — Google's logged-in data catches conversions GA4's cookies miss; (4) modeling — Google Ads fills consent-mode gaps with higher-fidelity modeling than GA4; (5) attribution models — Google Ads uses data-driven attribution per conversion action, GA4 uses cross-channel DDA. A 15–35% baseline delta is normal; above 50% indicates a tracking problem, not just structural difference. The Tracking Mismatch Audit quantifies each cause's contribution to your gap so you can separate 'normal' from 'broken'.

Yes — 20–30% sits squarely within Kissmetrics' benchmarked 'baseline delta' of 15–35% across most accounts, attributable entirely to the structural differences between the two platforms. Below 15% usually means either conversions are being under-counted somewhere or you've disabled view-through and cross-device in Google Ads. Above 40% signals a real tracking problem — duplicate firing, incorrect event setup, consent mode misconfiguration, or a GCLID stripping issue. The Tracking Mismatch Audit tells you whether your gap is structural (normal) or diagnostic (fixable).

Work through the five-step diagnostic in order: (1) verify GCLID is reaching your site unstripped (check network requests on your thank-you page), (2) confirm your conversion event fires exactly once per conversion and only on the correct URL, (3) ensure GA4 and Google Ads are both tagged via GTM with no duplicate triggers, (4) configure consent mode v2 consistently across both platforms, (5) reconcile attribution model settings. Most large discrepancies (above 40%) trace to steps 1–3. The Tracking Mismatch Audit runs each diagnostic automatically against your site and flags the specific failure points rather than giving generic advice.

Use native Google Ads conversion tracking as your primary bidding signal — it has higher fidelity via Google's logged-in identity graph, captures view-through conversions Smart Bidding needs, and is better calibrated for consent mode. Import GA4 conversions as secondary (non-Primary) actions for reporting and lifetime value analysis, not for bidding. Running GA4-imported conversions as your primary bidding signal typically degrades Smart Bidding because GA4 under-reports conversions Google Ads can see, training the algorithm on a weaker signal. The Tracking Mismatch Audit verifies your Primary/Secondary conversion configuration and flags mis-assignment.

Neither as a single source of truth — report both with a stated reconciliation note, or use your CRM/order management system as the revenue number and Google Ads / GA4 only for attribution and channel share. Reporting Google Ads numbers to leadership without context risks them discovering the GA4 gap and trusting nothing; reporting GA4 numbers under-attributes your paid channel and makes Google Ads look weaker than it is. The professional answer is a blended reporting framework: revenue from backend, attribution share from data-driven models across both platforms. The Tracking Mismatch Audit produces this reconciliation view so stakeholder reporting is defensible.

It's a design decision rooted in each platform's purpose — Google Ads is an auction optimisation system that needs to attribute to click date so Smart Bidding can retroactively score which clicks generated conversions, while GA4 is a behavioural analytics platform that needs transaction-date counting to produce accurate weekly/monthly reports. The practical consequence is that conversions with long consideration cycles (B2B, high-ticket ecommerce) show up in Google Ads weeks earlier than in GA4, making monthly comparisons misleading unless you align the reporting window. For a campaign driving 30-day consideration cycles, Google Ads' January number includes conversions GA4 will only show in February. The Tracking Mismatch Audit accounts for this temporal offset when calculating your true discrepancy rate.

Consent Mode v2 widens the Ads-vs-GA4 gap significantly in high-privacy markets — when users deny tracking consent, both platforms lose direct signal, but Google Ads has a larger modeling pool (cross-site logged-in behaviour, global advertiser conversion patterns) so its modeled recovery is stronger than GA4's. In Germany where consent rates average 35%, Kissmetrics reports up to 65% of Google Ads conversions come from behavioural modeling while GA4 reports substantially fewer. This means accounts in GDPR-heavy jurisdictions see 40%+ discrepancies that are structural, not fixable. The Tracking Mismatch Audit flags consent mode configuration issues separately and estimates the modeling-driven share of your gap.

Healthy range: 15–35% with Google Ads reporting higher; concerning range: above 40% or either platform reporting higher on a flipping basis month-to-month. The range scales with account characteristics — heavy PMax use pushes the gap higher (more view-through), shorter consideration cycles push it lower, and strong cross-device user behaviour (users starting on mobile and converting on desktop) pushes it much higher. If GA4 is ever reporting more conversions than Google Ads, something is broken — this happens when duplicate GA4 events or a broken Google Ads tag is under-firing. The Tracking Mismatch Audit produces your expected gap range based on your account's characteristics and flags deviations.

Attribution drift is the growing gap between Google Ads-reported and GA4-reported conversions over time, caused by cumulative tracking degradation — new tags deployed without removing old ones, URL parameter changes that strip GCLID, consent mode rollouts, iOS privacy updates, or new conversion actions with different firing rules. A 20% gap drifting to 40% over six months is almost always a sum of small changes rather than one big break. The fix is a full tracking audit every 6 months regardless of whether anything 'feels' broken. The Tracking Mismatch Audit establishes a baseline gap per campaign and plots drift over time so you spot degradation early.

Two common root causes: (1) your Google Ads conversion tag is firing twice per purchase — typically when the GA4 import and the Global Site Tag both run and both pass data to Google Ads; (2) one-per-click vs every-conversion setting — if set to 'Every' for a lead form that can be submitted multiple times per visitor, a single visitor creates multiple conversions in Google Ads while GA4 counts the session once. Both inflate Google Ads numbers by 40–100% and badly mis-train Smart Bidding. The Tracking Mismatch Audit runs a deduplication check against your conversion actions and identifies which specific configurations are creating the double-count.

Build a three-tier reconciliation: Tier 1 — backend revenue from your order system as the single source of truth for total sales; Tier 2 — GA4 as the source of truth for channel attribution share and behavioural engagement metrics; Tier 3 — Google Ads as the source of truth for campaign-level bidding signal and cost per attributed conversion. Do not blend them into a single number. Report the reconciliation framework explicitly so stakeholders understand why numbers differ. The Tracking Mismatch Audit produces a reconciliation template populated with your specific account's numbers and flags the campaigns where the Ads-vs-GA4 gap is distorting ROAS reporting.