By Prakhar KirsaliPublished Topic: GA4
Short answer
Google Ads and GA4 never report identical conversion numbers because they use different attribution models (Google Ads credits its own clicks under data-driven attribution; GA4 applies last non-direct click across all channels), different conversion definitions and counting settings, different time zones and reporting dates, and they lose traffic differently under consent and browser privacy limits. A gap of roughly 10–20% between the two for lead conversions is common and normal; a much larger gap, or a gap that suddenly widens, usually points to duplicate counting, a misconfigured import, or a consent/tracking fault worth fixing.
You compare last month's reports: Google Ads says 118 conversions, GA4 says 87 key events from the paid search channel. Neither number is a typo, and neither platform is lying. They are answering slightly different questions about the same clicks.
This is the most common measurement confusion I get asked about, and the answer is almost never "your tracking is broken." Most of the gap is structural — the two systems were built with different purposes, and they will never reconcile to the last conversion. What matters is knowing which part of the gap is expected, which part is a fault, and which number you should actually use for each decision. This walks through every major cause in order, from the biggest to the smallest, then gives you a reconciliation procedure.
The core reason: the two platforms answer different questions
Google Ads counts conversions to help its bidding system decide which clicks are worth buying. GA4 counts key events to describe what happened on your website across every traffic source. Same visitor, same form fill — but each platform wraps that action in its own rules about who gets credit, when it's counted, and what qualifies as a conversion in the first place.
Even in a perfect implementation with no technical faults anywhere, the two systems will report different numbers. Expecting them to match is the wrong baseline. The right baseline is: understand each source of difference, and expect a predictable, stable gap — not a zero gap.
The short version of every cause in this article
Different attribution models (Google Ads credits its own clicks; GA4 shares credit across channels), different conversion definitions (what each platform counts as "a conversion"), different reporting dates and time zones, different counting settings, duplicate events from double-tagging or misconfigured imports, cross-domain session breaks, and unequal data loss under consent rules and browser privacy restrictions. The sections below take these one at a time, in rough order of how much difference they typically make.
1. Different attribution models
This is usually the largest single cause of the gap.
Google Ads attributes conversions to the Google Ads clicks that drove them. Since late 2023, data-driven attribution is the default for new conversion actions: credit is distributed across the clicks on the path based on a model of which ones mattered most — but every credited click is a Google Ads click, and if Google Ads drove the whole path, it takes all the credit.
GA4's default attribution is last non-direct click across all channels. If someone clicked your ad, came back two days later through an organic search result, and then filled in the form, GA4 gives the key event to organic search. Google Ads still counts the conversion, because its click was on the path. Multiply this by every lead who researches before converting and you get a systematic gap: Google Ads claims more conversions than GA4 assigns to the paid search channel.
What this means for your comparison
When you compare Google Ads conversions with GA4 key events filtered to the paid search channel, part of the gap is simply leads GA4 credited to another channel. That's not a discrepancy — it's GA4 correctly telling you those people returned through a different door. In GA4's advertising reports, session default channel group analysis can show how often paid clickers convert on a later organic or direct visit. GA4's own attribution reporting (advertising attribution settings) can also be set to data-driven, which narrows but never eliminates the difference, because GA4 still models cross-channel credit.
2. Different conversion definitions
The two platforms don't necessarily count the same list of actions.
In Google Ads, a conversion action is something you explicitly created: a tag firing on a thank-you page, a call with a minimum duration, an imported offline conversion, or an imported GA4 key event. Each action has a goal (primary or secondary) and a counting setting.
In GA4, an event becomes a key event when you mark it, and it counts in reports when it fires — regardless of which channel brought the visitor. A GA4 key event that was never imported into Google Ads shows up in GA4 but not in Google Ads at all. Conversely, Google Ads conversions like phone calls or store visits have no GA4 equivalent unless you built one.
Before comparing anything, write down exactly which actions each platform counts and confirm the lists match. A "mismatch" that turns out to be two different conversion definitions isn't a fault — it's two different measurements wearing the same label.
3. Reporting dates and time zones
Google Ads reports conversions on the date of the click that produced them; GA4 reports key events on the date the event happened. A lead who clicks your ad on 31 January and fills the form on 2 February appears in January's Google Ads report and February's GA4 report.
Time zones make it worse. Your Google Ads account has one time zone (set at account creation and permanently unchangeable), and your GA4 property has another (also fixed after creation). In accounts I've audited, these are different more often than not — a US-based Ads account and a GA4 property set to UK time, or the reverse. Every conversion between the two boundaries lands in different days, and at month edges this alone can shift several conversions between reports.
In Google Ads you can add the "Conversions (by conv. time)" column to see conversions attributed to the date they actually converted, which is the closer comparison to GA4 — though the two still won't match exactly, because of everything else in this article.
4. Counting settings
Both platforms let you choose how to count repeat actions, and mismatched settings produce one-sided gaps.
In Google Ads, each conversion action is set to count "One" or "Every". A lead-generation action left on "Every" counts a person who submitted the same form three times as three conversions; GA4, if the key event is set to count once per session, counts one. This is one of the first things to check when Google Ads shows consistently more conversions than GA4 for the same action.
In GA4, key event counting is set per key event: once per event, once per session, or every event. If GA4 is set stricter than Google Ads, Google Ads wins the comparison every month, and the gap grows with repeat submitters — a pattern worth checking in your own data before assuming tracking damage.
5. Duplicate events and misconfigured imports
Unlike everything above, this one is a genuine fault, and it inflates one side.
The most common version: a GA4 key event is imported into Google Ads as a conversion action, while a native Google Ads conversion tag also fires for the same form fill. Google Ads now counts each conversion twice (once per action) while GA4 counts it once. Check the conversion actions page — if two actions track the same outcome, one of them is surplus.
A subtler version: the thank-you page fires a GA4 event and a Google Ads tag both keyed off the same page view, and a second GA4 event rule also fires from the same trigger. Duplicates inside GA4 itself inflate key events. DebugView is the arbiter: submit one test lead and confirm exactly one event appears per platform.
The rule that prevents all versions of this: one source of truth per business action. If GA4's key event is imported into Google Ads, the native Google Ads tag for that same action should be removed or set to secondary. The companion piece on which events to mark as GA4 key events covers the import-vs-native decision in detail.
6. Cross-domain and session breaks
Google Ads almost always knows about its click: the click identifier (gclid) travels with the visitor and survives reasonably well. GA4 is more fragile — it needs cookies to stay alive across the whole journey.
If part of your journey crosses to a different domain — a booking engine, a checkout, a scheduling tool, a subdomain that isn't configured — GA4 treats the visitor as a new session on the new domain. Unless cross-domain measurement is configured, the original referral is lost, and if the conversion happens on the second domain, GA4 may attribute it to direct traffic or miss the connection entirely. Google Ads still counts the conversion.
Similar breakage comes from cookie deletion, Safari and Firefox's tracking prevention shortening cookie life, and visitors moving between devices — a click on mobile, a form fill on desktop splits into two people as far as GA4 can tell.
7. Consent and tracking limitations
The two platforms lose data differently, and consent mode makes the gap bigger, not smaller.
Where consent is denied, GA4 (in consent mode basic) receives no event at all — the visit is invisible. Google Ads may still receive a consentless ping in consent mode basic, and its conversion modelling fills in some of what it can't directly observe. So in consent-required regions, GA4 can undercount relative to Google Ads by design.
Even without consent mode, the platforms lose different visitors: ad blockers commonly block the GA4 script, but Google Ads conversion tags attached differently can occasionally survive where GA4 doesn't — and vice versa. Pages that load slowly, or conversions that fire after the visitor leaves, are caught differently by each system.
The consequence: some part of your gap is permanent, unfixable, and simply reflects that two measurement systems see different slices of the same reality. Budget for it rather than chasing it.
8. Conversion windows and lag
Google Ads conversion actions have a conversion window (default 30 days from the click). GA4 key events appear when they happen. Imported GA4 key events in Google Ads additionally inherit GA4's processing and reporting delay, and Google Ads notes that imported GA4 conversions use GA4's attribution — importing changes the numbers as well as the plumbing.
Recent days are also incomplete in both systems: Google Ads conversions for the last few days keep arriving as windows close, and GA4 processing has its own lag. Comparing a period that ended yesterday exaggerates the mismatch; compare closed periods instead.
A reconciliation procedure that takes twenty minutes
Rather than staring at the headline numbers, work through this sequence once and you'll know exactly how much of your gap is explained.
How much gap is normal?
In well-built lead-generation accounts, a remaining gap of roughly 10–20% between Google Ads conversions and GA4 key events is common and not worth chasing. What deserves attention: a gap that's much larger than that, a gap that suddenly widens after a site change or a tracking edit, or GA4 showing near-zero where Google Ads shows conversions — that pattern usually means a broken GA4 event or a consent misconfiguration rather than attribution noise.
- Confirm both platforms count the same list of actions for the outcome you're comparing (section 2), and that each action is counted once across platforms (section 5).
- Compare only primary conversion actions in Google Ads — exclude secondary actions and "view-through" style additions from the comparison.
- Match the date ranges to closed periods, and add the "Conversions (by conv. time)" column in Google Ads to compare like with like; check both platforms' time zones.
- In GA4, look at the key event across all channels, not just paid search — that isolates how much of the gap is attribution (section 1).
- Check counting settings on both sides (section 4) and look for repeat submitters if Google Ads is consistently higher.
- Subtract consent-region traffic if consent mode is active, and accept a residual gap — that's the privacy and data-loss floor (section 7).
Which number should you actually use?
Use each platform for the job it's built for. Google Ads conversions drive Smart Bidding — the bidding system optimises toward what its own conversion column reports, so that's the number that matters for bid decisions. GA4 is the better number for business reporting: it shows the full picture across channels, reveals when paid clickers convert through other channels, and reconciles against your CRM. Neither is "the true number"; they measure the same outcome under different rules.
The reconciliation that matters most is neither platform against the other — it's both against reality: how many enquiries actually arrived in your inbox or CRM. If GA4 says 87 and the CRM received 41 genuine enquiries, that gap is worth far more attention than the Google Ads-versus-GA4 difference. That reconciliation discipline is central to how I approach GA4 and analytics measurement and conversion tracking setup for clients, and it's the first thing checked in any Google Ads account review I run.
Frequently asked questions
- Why does Google Ads show more conversions than GA4?
- Usually a combination of attribution (Google Ads credits conversions to its own clicks even when GA4 credits the final touch to another channel), counting settings (Google Ads set to "Every" while GA4 counts once per session), and unequal data loss under consent and privacy restrictions. Small persistent differences are normal; a large or sudden gap should be investigated.
- Should GA4 conversions and Google Ads conversions match?
- No. The two platforms use different attribution models, conversion definitions, counting settings, time zones and reporting dates, and they lose data differently. In well-built accounts a gap of roughly 10–20% for lead conversions is common. Expect a stable, explained gap rather than a match.
- Which is more accurate, Google Ads conversions or GA4 key events?
- Neither is universally more accurate — they measure under different rules. For bid optimisation, Google Ads' own conversion column is the operative number because Smart Bidding acts on it. For business reporting, GA4's cross-channel view is more representative. The most important check is both against your actual leads in your inbox or CRM.
- Why do GA4 key events imported into Google Ads still differ from Google Ads' own conversions?
- Imported GA4 key events keep GA4's attribution and reporting lag, and Google Ads reports them by click date within the conversion window. Native Google Ads conversions use Google Ads' attribution and count settings instead. Mixing the two in one account makes the numbers harder to reconcile — one source per action keeps it clean.
- Can duplicate conversion tags cause Google Ads to overcount?
- Yes. If a GA4 key event is imported into Google Ads while a native Google Ads conversion tag also fires for the same action, Google Ads counts the conversion twice. Check the conversion actions list for two actions covering the same outcome and keep one as the primary source.
- Does consent mode make the GA4 and Google Ads gap bigger?
- Typically yes. With consent denied, GA4 in consent mode basic receives nothing, while Google Ads can receive a consentless ping and apply conversion modelling — so GA4 undercounts relative to Google Ads in consent-required regions. The gap is expected behaviour, not a tracking fault.