OmniCommand

GA4 and Google Ads don’t match: making sense of conversion discrepancies

Say Google Ads reports 48 conversions for a campaign last month, and Google Analytics 4 reports 31. Both reports come from Google, both describe the same campaign, and the meeting stalls on which number is right.

Google itself does not expect them to agree. Its help documentation on understanding conversion tracking data notes that discrepancies “often up to 20%” are expected because the two products use different attribution models.

A difference between the two reports is usually not an error. It is two measurement systems answering slightly different questions. The useful work is understanding why they differ, deciding which number answers your question, and noticing when a gap grows beyond what those differences explain.

Why the two reports disagree

They credit different clicks and channels

Google Ads reports conversions it can connect to its own ad interactions. Google Analytics 4 looks at every channel a visitor used and assigns credit according to its own attribution settings. A visitor who clicked an ad, left, and returned later through an email or an organic search can be credited differently by each.

They date conversions differently

Google Ads’ primary conversion columns are dated to the time of the ad click, not the time of the conversion. Someone who clicked on the 30th and inquired on the 2nd appears in the earlier month in Google Ads. Google Ads also offers “by conversion time” columns, which align more closely with how analytics reports events. Google’s documentation notes that reporting can lag by 24 to 48 hours as well.

They count differently

A Google Ads conversion action can count every conversion after an ad interaction or only one. Google’s guidance is to count one for leads, so a visitor who submits the same form twice is not counted twice. Analytics may record both events. Two systems counting the same behavior by different rules will produce different totals.

They may not be counting the same action

The Google Ads conversion might be a form submission tracked by the Google Ads tag, while the GA4 figure is a key event defined differently, or imported into Google Ads from GA4 under a different name. Before comparing, confirm that both numbers refer to the same action.

They see different visitors

Consent choices, browser restrictions, and ad blockers affect what each tool can record. Analytics may miss sessions that Google Ads still counts as clicks, and the reverse can also happen.

How to compare them fairly

Treat the comparison as a check on your measurement, not a contest.

CheckWhat to align
The actionBoth numbers must count the same behavior
The date basisClick date in Google Ads versus event date in Analytics
The windowThe same date range, and enough time for late conversions
The trafficAnalytics filtered to Google Ads traffic, not all visits
The counting ruleOne per interaction or every conversion
The time zoneAccount and property time zones can differ

Once those are aligned, a consistent gap of similar size from month to month is usually structural. You can account for it and move on. A gap that suddenly widens deserves attention, because it often signals a change in tracking: a tag removed during a site release, a form replaced, or a conversion action redefined.

Which number should you use?

Use each number for the question it answers.

Google Ads conversions describe what Google Ads optimizes toward and are the right reference when evaluating bidding and campaign performance inside the platform. Google Analytics 4 describes behavior across channels and is the better reference for how visitors move through the site.

Neither should be averaged with the other, and neither should silently replace the other in a report. Present them side by side, each with its own source and definition. Where possible, add the business’s own record, such as CRM inquiries or orders, as the outcome both tools are trying to approximate.

A worked example

Consider a hypothetical service business. Over one month, Google Ads reports 48 form conversions, GA4 reports 31 form submissions from Google Ads traffic, and the CRM shows 36 new inquiries that mention a search ad.

None of these numbers is wrong. Google Ads dates some conversions to clicks made in the previous month and credits a few visitors who returned through other channels. GA4 misses visitors who declined analytics cookies. The CRM depends on how the team records the source of each inquiry.

The useful reading is not which figure wins. It is that the three move together from month to month. If next month Google Ads reports 50 and GA4 reports 9, the gap has changed shape, and the first suspect is tracking rather than the campaign.

When the gap is a real problem

Some discrepancies point to something that needs fixing:

  1. The gap changes suddenly without a matching change in campaigns or traffic.
  2. One source drops to zero while the other continues to record activity.
  3. Campaigns cannot be matched between the two tools because campaign names or tracking parameters are inconsistent.
  4. Conversions appear in one tool for actions the other cannot see at all, which usually means the tools are measuring different things.

In each case, the fix is in measurement: tags, conversion definitions, or tracking parameters. Changing bids or budgets before measurement is repaired risks optimizing against a broken signal.

How OmniCommand handles numbers that do not agree

OmniCommand connects to Google Ads, Google Analytics 4, Meta Ads, and Google Search Console, and it keeps each source’s figures in that source’s own terms. A Google Ads conversion and a Google Analytics key event are never added together or averaged into a blended number. When both are relevant, they appear side by side, each named by its source.

Where OmniCommand joins data across tools, for example matching Google Ads campaigns to Google Analytics sessions and key events, it states how much of the data actually matched rather than presenting a partial join as complete. Its cross-source checks are labeled as directional checks across two measurement systems, not attribution, because they cannot prove which count is correct.

That leaves the judgment where it belongs: with a team that can see each number, its source, and its limits before deciding what to act on. OmniCommand reads your connected accounts and never changes anything in them.

To see your own sources side by side, you can request early access to OmniCommand.

Frequently asked questions

Why don’t my GA4 and Google Ads conversions match?

The two products use different attribution models, date conversions differently, can apply different counting rules, and may be tracking different actions. Some difference is expected, and Google’s own documentation says so.

Which is more accurate, Google Ads or GA4?

Neither is universally more accurate. Google Ads describes conversions connected to its ads, and GA4 describes behavior across channels. Use each for the question it answers, and compare both with your business records.

How big a difference is normal?

It varies by account. Look for a gap that stays roughly stable over time. A sudden change in the size of the gap is a better warning sign than the gap itself.

Should I import GA4 conversions into Google Ads?

It can make the two systems count the same action, but the figures may still differ because of attribution and date basis. Decide based on which event best represents the outcome your bidding should pursue.

Can I add GA4 and Google Ads conversions together?

No. They often describe the same customers, so adding them double counts. Present them side by side with their sources.

Does OmniCommand decide which number is right?

No. OmniCommand shows each source’s figures in its own terms and labels cross-source comparisons as directional checks, not attribution. Your team decides which measure fits each decision.