Skip to content

Why GA4 Data Does Not Match Your Other Tools

GA4 data does not match other tools because each one counts something different, on a different date, under different rules. A gap is normal. A gap that suddenly changes size is the one to investigate.

By Kristijan GjorgjioskiIndependent SEO consultant

Published 18 October 2026 · 6 min read

Key takeaways

  • Search Console counts clicks, GA4 counts sessions from browsers that ran the tag. The two will never be equal.
  • Google Ads reports conversions on the ad click or impression date; GA4 reports key events on the date they happened.
  • Visitors who decline analytics cookies, block scripts or call you by phone never reach GA4, so it usually sits below your CRM.
  • GA4 can take 24 to 48 hours to finish processing, so yesterday's numbers may still change.
  • Compare trends, not totals. A stable gap is fine; a gap that moves means something broke.

Your GA4 report says 412 sessions from organic search last month.

Search Console says 530 clicks.

Your CRM says 38 new enquiries, while GA4 says 51 key events.

Which one is lying?

None of them, usually. They are measuring different things.

In this guide you will learn why each pair of tools disagrees, which gaps are normal, and the warning signs that mean your tracking is broken.

What Does a Normal Gap Look Like?

A normal gap is one that stays roughly the same size, in the same direction, month after month.

If GA4 always reports somewhat fewer organic sessions than Search Console reports clicks, that is expected.

If the gap suddenly doubles in one week, something changed.

Here's what I look for in every audit:

  • Direction. Is GA4 above or below the other tool? Each pair has an expected direction, covered below.
  • Stability. Does the gap hold steady across months?
  • Breaks. Did the gap change on a specific date? Match that date to a site release, a new cookie banner or a tag change.

The figures at the top of this page are made up for illustration. Your own gap will be different, and you should expect that.

What matters is that you know its normal size, so you notice when it moves.

Why Do GA4 Sessions Differ From Search Console Clicks?

Search Console counts clicks on Google Search results. GA4 counts sessions in browsers where the tag loaded and was allowed to run.

Those are not the same event.

Google lists several reasons in its Search Console discrepancy guide:

  • JavaScript. GA4 only records visitors whose browsers run JavaScript. Search Console counts the click regardless.
  • Privacy filtering. Search Console leaves out some rare queries to protect users.
  • Time zones. Search Console reports days in Pacific Time. GA4 uses your property's time zone.
  • Processing and lag. Search Console removes duplicates, and its data usually lands two to three days later.

Add consent banners to that list. A visitor who declines analytics cookies may still click your result, but GA4 sees less of them.

So if your GA4 sits below Search Console, that is the normal direction. It does not mean your SEO traffic is being undercounted by mistake.

Note: If GA4 shows more organic sessions than Search Console clicks, look for sessions from other search engines being grouped in, or a reporting mix-up such as comparing all organic search with Google only.

Why Do GA4 Key Events Differ From Google Ads Conversions?

Google Ads and GA4 disagree for structural reasons, even when you have set both up perfectly.

The biggest one is the date.

Google Ads Help says Google Ads reports conversions on the ad impression date. GA4 records a key event on the day it happened.

So an ad seen on the 30th that leads to a sale on the 2nd can land in different months in each tool.

Other causes:

  • Counting. Google Ads can count every conversion or one per click. GA4 key events count once per event or once per session.
  • Attribution. Google Ads only credits its own ad interactions. GA4 spreads credit across all channels under its attribution model.
  • Primary and secondary actions. The default Conversions column in Google Ads only includes primary actions.
  • Late conversions. Google Ads can record conversions up to 90 days after the click.
  • Invalid traffic. Google Ads may later remove conversions it flags as invalid.

There is also a naming trap. GA4 now calls its success events "key events". A "conversion" in GA4 means a Google Ads conversion, shown in the Advertising section, not in standard reports.

Why Is GA4 Lower Than Your CRM or Store?

Your CRM or store records every real enquiry or order you receive. GA4 only records what the tag could see.

The usual reasons GA4 comes in lower:

  • Consent. Visitors who reject analytics cookies send little or no usable data to GA4. How each tag reacts to that choice is set in your Tag Manager container.
  • Blocked scripts. Some browsers and extensions stop analytics tags from loading.
  • Offline leads. Phone calls, emails and walk-ins never touch your website tag.
  • Broken journeys. A booking tool or payment page on another domain, without cross-domain tracking, can lose the key event entirely.
  • Missing tags. A landing page builder or thank-you page that never got the tag.

GA4 can also come in higher than the CRM. That direction is a red flag.

It usually means GA4 is installed twice, a key event fires on a button click even when the form fails, or spam submissions are being counted.

My GA4 audit checklist walks through how to test each of these.

Why Do GA4 Numbers Change After You Look at Them?

Because GA4 has not finished processing them.

According to Google's data freshness page, processing can take 24 to 48 hours, and report data may change during that time. Intraday data on a standard property typically lands within two to six hours.

Two other effects change what you see:

  • (other) rows. When a report hits its row limit, GA4 groups less common values under (other). Stricter limits can apply before daily processing completes.
  • Data thresholds. GA4 can withhold rows in reports with demographic data or small user counts, to protect individual users. Widening the date range often brings them back.

The practical rule is simple:

Never report on the last two days. Compare complete weeks or months.

Why Do Two GA4 Reports Disagree With Each Other?

Sometimes the mismatch you are chasing is inside GA4 itself.

Common causes:

  • User versus session scope. The User acquisition report credits the channel that first brought each user. Traffic acquisition credits the channel that started each session. Same data, different question.
  • Reporting identity. Blended, Observed and Device-based identity count users differently. Changing it does not alter collected data, but it changes how users are de-duplicated in reports.
  • Attribution model. Changing the reporting attribution model applies to historical data as well, so last month's channel split can look different after the change.
  • Explorations versus standard reports. Explorations are limited by your data retention setting. Standard reports are not.

If two colleagues pull "the same" number and get different answers, check which report, which scope and which date range each one used.

Better still, write your identity and attribution choices into a GA4 measurement plan so you all read reports the same way.

How Do You Reconcile GA4 With Your Other Tools?

You will never make them match exactly. You can make the gap understood.

Here is the process I use:

  1. Pick one pair at a time. GA4 versus CRM, or GA4 versus Google Ads. Not all three at once.
  2. Align the basics. Same date range, same time zone, same definition of the thing being counted.
  3. Use complete months. Skip the most recent two days entirely.
  4. Compare trends, then totals. Plot both lines. If they move together, the tracking works.
  5. Write down the expected gap. "GA4 key events usually run about this far below CRM leads." Then check it monthly.
  6. Investigate breaks. When the gap jumps, look at what changed on that date.

For Google Ads, importing GA4 key events as conversions narrows the gap, because both tools then count the same action. Get the key events right first. My guide on how to set up key events in GA4 covers that.

If the break traces back to a tag change, the fix usually sits in your container. These steps to debug Google Tag Manager help you find which tag stopped firing.

Find Out Which Gap Is Hurting You

Some gaps are just how measurement works. Others mean you are making money decisions on broken data.

The quickest test you can run is to line up three months of GA4 key events against your own records.

If the gap is stable and explainable, you are fine.

If it jumps, flips direction or nobody can explain it, that is when a GA4 audit pays for itself.

I trace each gap to its source, test the key journeys in a real browser and give you a ranked fix list. If the property turns out to be past saving, a rebuild through GA4 setup is the cleaner route.

Either way, you end up knowing which numbers to trust. The Google Analytics consulting overview shows how those services fit together. Start with the audit if you are not sure which applies.

Frequently asked questions

Is it normal for GA4 and Search Console to show different numbers?

Yes. Search Console counts clicks from Google Search, while GA4 counts sessions from browsers that loaded the tag and allowed it to run. Consent choices, blocked scripts, time zones and Search Console's privacy filtering all widen the gap. Compare the trend line of both tools over months rather than expecting matching daily totals.

Why does GA4 show more key events than my CRM has leads?

Usually because the key event fires on the wrong action. Common causes are a key event on a button click rather than a successful submission, GA4 installed twice, spam form entries, or default key events added when Google Ads was linked. Test each key event in DebugView and compare against real CRM entries.

Why do yesterday's GA4 numbers keep changing?

GA4 is still processing them. Google Analytics Help says processing can take 24 to 48 hours, and reports may change during that time. Intraday figures can also show more (other) rows until the daily tables finish. Avoid reporting on the last two days, and compare complete weeks or months instead.

Can I make GA4 match Google Ads exactly?

Not exactly, because the two tools date and attribute conversions differently. You can narrow the gap by importing GA4 key events into Google Ads, matching counting settings, aligning lookback windows and comparing the same date basis. Some difference will remain, and that is expected.

About the author

Kristijan Gjorgjioski

Independent SEO consultant · 6+ years in SEO · 60+ client websites worked on

I'm an independent SEO consultant with 6+ years in SEO. I run audits, migrations and content programmes for businesses in Europe, the UK and the USA, and I build the automation behind my own research.

Need help with ga4 audit?

Book a free 30-minute call. I look at your site first and tell you plainly what I would fix, and in what order.