How Big a Gap Between Google Ads and Analytics Is Normal?

Your Google Ads account credits last month's paid search with more conversions than GA4 gives to google / cpc, and your client wants to know which number is wrong. Chase that gap to zero and you lose days to a reconciliation that cannot succeed. Shrug it off and you miss the week a duplicate tag doubled your purchases.

No published percentage defines a normal conversion discrepancy, because the two systems are built to disagree. A normal gap is stable week to week, has Google Ads above GA4 for paid search, and is explained by attribution, conversion dates and browser blocking. A gap that jumps or changes direction points to a tracking fault.

Why is there no single normal percentage?

The figures that circulate for "acceptable" gaps come from individual agency accounts, with no stated sample, period or method. None of them is a benchmark, and none of them would carry over to your account. The forces that create the gap differ in size from one business to the next.

Four things set how far apart the two numbers sit:

• Time to purchase. The longer buyers take between click and conversion, the more the two platforms' different date logic and lookback windows matter. A 60-day B2B cycle produces a wider gap than an impulse-buy store.
• Channel mix. If buyers often return through organic search, email or a direct visit before buying, GA4 gives credit to those channels and Google Ads still claims the sale.
• Audience privacy behaviour. GA4's tag runs in the browser. Consent refusals and ad blockers stop it firing, and the share of visitors who do either varies by market and audience.
• Conversion setup. Counting rules, tag placement and whether you bid on the native Ads tag or imported GA4 key events all move the number.

These forces are the same ones covered in the full breakdown of why the two platforms' conversions don't match. For the question of what is normal, the practical consequence is simple. The only meaningful benchmark is your own account's history. A double-digit gap is not, on its own, evidence that anything is broken.

Which direction should the gap run?

The size of a healthy gap is not fixed, but its direction mostly is. For paid search conversions, Google Ads should usually report more than GA4. Each of the main mechanisms pushes that way.

Attribution favours Google Ads in its own account

Google Ads only credits conversions that follow an interaction with its own ads, and it gives the credit to an ad click that falls inside its conversion window. GA4 looks at the whole site across every channel. Its Traffic acquisition report uses last non-direct click.

So a buyer who clicks a search ad on Monday and returns through an organic listing on Thursday is a paid conversion in Google Ads and an organic one in GA4. Neither platform is wrong. They are answering different questions.

"The GA4 number" depends on which report you open

GA4 does not use one attribution model throughout. Session-scoped reports such as Traffic acquisition use last non-direct click. User-scoped reports such as User acquisition use first touch. Event-scoped reports use the property's reporting model, which is data-driven by default.

If you compare Google Ads against Traffic acquisition one month and against an event-scoped key events report the next, the gap will move even though nothing in your tracking changed.

The two platforms date conversions differently

Google Ads records a conversion against the date of the ad click. GA4 records it on the day it happened. Time zone differences between the two accounts can also push the same purchase onto a different day.

Over a full month these effects largely wash out. Over a day or a week they can be large, which is also why Google Ads can show conversions on days you had none.

Browser blocking hits GA4 hardest

Whenever GA4's client-side tag fails to fire, the conversion is missing from GA4 altogether. That loss shows up as part of the gap, and it grows as your audience gets more privacy-conscious.

The reverse pattern needs explaining. If GA4 reports more paid search conversions than Google Ads for the same conversion action, look for duplicate GA4 events or a misconfigured Ads tag. Do not assume it is noise.

Which gaps signal a tracking problem?

A normal gap is boring. It sits in roughly the same place each week and moves with seasonality, not with deployments. These patterns are not normal:

• A step change on a specific date. If the ratio between the platforms shifts overnight and stays shifted, look for something that changed that day. Common causes are a tag deployment, a CMS or checkout update, a new consent banner, or a new plugin.
• A change of direction. If Google Ads normally leads and suddenly trails, a tag has stopped firing on one side, or paid traffic has started arriving under a different source.
• Either platform exceeding your backend. If conversions in Google Ads or GA4 outnumber the orders in your store or CRM, you are counting something twice. Typical causes are a purchase tag on a second domain, a confirmation page that fires again on reload, or missing transaction IDs that would otherwise deduplicate. Check the counting setting as well. One conversion per click and every conversion per click give very different totals for the same activity.
• Paid traffic appearing as referral or another source. A feed or marketing plugin that adds its own UTM parameters can override the gclid. GA4 then loses the link between the session and the ad that drove it.
• Conversions recorded before payment. A tag that fires when checkout starts, rather than when payment clears, inflates conversions on both sides. It also makes the platform totals drift away from real revenue.
• Unexplained week-to-week swings. Some movement is expected around promotions and seasonal peaks. Regular swings with no commercial reason behind them suggest something intermittent, such as a tag that fires on some page templates and not others.

How do you set a baseline for your account?

The aim is not to close the gap. The aim is to know what your gap looks like when things are working, so you notice when they stop.

Compare like for like. Use the same conversion action on both sides. In GA4, use an event-scoped key events report filtered to Google Ads traffic, not Traffic acquisition. In Google Ads, use the conversion-time columns so both platforms report on the date of the purchase rather than the click. Then confirm both accounts use the same time zone.

Anchor both to the backend. Your store or CRM is the source of truth for whether a sale happened. Record each platform's total as a ratio against backend orders, as well as against each other. If Google Ads drifts away from GA4 while staying steady against the backend, the problem is on the GA4 side.

Track the ratio weekly for a couple of months. The band it moves within is your normal. Write that band down, share it with the client, and investigate only when a week falls outside it. That gives you one conversation about why the numbers differ, not a new one every month.

Give each number its job. Google Ads conversions are the input to bidding. Backend orders are the record of revenue. GA4 is where you compare channels against each other. Stakeholders accept the gap far more readily when they know which number answers which question.

Conclusion

A normal gap between Google Ads and GA4 is not a percentage you can look up. It is a pattern you establish. Google Ads should usually report more paid search conversions than GA4, for reasons that are structural rather than faulty. The useful question is whether the gap is stable, runs in the expected direction, and tracks your backend. Measure your own band, compare reports that use the same scope and dates, and save your investigation time for the moment the pattern breaks.

Companion reads Google Ads, Analytics and Shopify data side by side and reports what changed in a daily brief, rather than leaving that for month-end reconciliation.