Why your Google Ads and GA4 conversion numbers don't match

First, attribution date. Google Ads credits a conversion to the date of the ad click that led to it; GA4 credits the date the conversion happened. A conversion from a click eleven days ago appears in a different day's row in each platform. Over a month this mostly washes out; over a week it does not.

Second, attribution model and scope. Google Ads attributes only to ad interactions, across its own network, within its own lookback window. GA4 attributes across all channels — organic, direct, email, referral — so any conversion GA4 assigns to another channel simply will not appear in the Ads number.

Third, what's being counted. Google Ads counts conversions, which can include multiple per click depending on the conversion action's counting setting. GA4 counts key events per session. These are different units of measurement, and no configuration makes them the same one.

For a well-implemented account with a single primary conversion action, expect Google Ads to report somewhat more conversions than GA4 attributes to paid search — commonly five to fifteen percent — and expect that relationship to be stable month over month.

Stability is the diagnostic, not the size. A consistent 12% gap you can explain is a healthy account. A gap that swings between 4% and 60% by month is telling you something is broken, regardless of the average.

Duplicate firing. The same user action triggers two events — a GTM tag and a hard-coded gtag call, or a thank-you page view alongside a form submission event. Conversions inflate by an unknown and variable factor.

Broken cross-domain measurement. The user moves from your site to a booking platform, payment processor, or subdomain, and the session breaks. GA4 records a new session from a referral; the conversion loses its paid attribution entirely.

Unverified conversion actions. Someone marked a soft engagement — a phone-number click, a PDF download — as a primary conversion, and Smart Bidding is optimizing toward it. The count is high, the quality is unknown, and the CRM disagrees with both platforms.

Call tracking double counts. A call platform reports a conversion, and a click-to-call event fires for the same call. Both reach the ad platform.

Consent Mode and modelling. Where consent is denied, GA4 may model conversions while Ads counts differently. Whether this matters depends on your jurisdiction and traffic mix, but it should be a known factor rather than a surprise.

Start with an inventory: every system that counts a conversion, and what precisely it counts. Most organizations have four — the ad platform, GA4, call tracking, and the CRM or booking system — and have never written the four definitions side by side.

Then trace the highest-value conversion path end to end, in a real session with debug tooling open: user action, data layer, GTM trigger, tag fire, platform receipt. Duplicate firing and broken linkage are visible in minutes this way, and invisible in reports for months.

Then declare authority. One source is authoritative per decision: platform numbers for in-platform bidding, CRM or booking numbers for revenue reporting, with a documented expected variance between them. Write the expected variance down. A gap you predicted is a footnote; a gap you discovered on a client call is a credibility problem.

Reporting all four without stating which is authoritative is the practice that erodes trust fastest, because each number is defensible in isolation and the set is not.

For multi-location businesses there's a fourth failure mode that dwarfs the others: conversion events that fire without a location parameter. The conversions are real and correctly counted in aggregate, and per-location performance is simply unmeasurable — which means budget decisions across locations are being made on aggregate data and gut feel.

This is what an attribution gap means in practice, and it's fixable at the event layer. It is worth checking before any optimization work, because per-location CPA is not comparable until it is fixed.