Analytics and Tracking

Data Discrepancy

Also called Data mismatch

The gap between two tools counting the same thing, caused by different definitions, windows, time zones or blocked scripts.

Quick facts: Data Discrepancy

Category
Analytics and Tracking
Also called
Data mismatch
Level
Intermediate
Affects
Reporting confidence, budget decisions, client trust
Where to see it
GA4, Google Ads, Meta Ads Manager, your CRM, Looker Studio
In this article4
  1. How a data discrepancy arises
  2. Why data discrepancies matter
  3. Common mistakes with data discrepancies
  4. How to act on it

How a data discrepancy arises

Two tools rarely disagree because one of them is broken. They disagree because they were built to answer slightly different questions and were never designed to match. Google Ads credits a conversion to the date of the click that led to it, while GA4 records it on the day it actually happened. That single difference is enough to make two reports covering the same month look irreconcilable.

Everything else layers on top. Different attribution windows and models decide who gets the credit. Different definitions of a visit — a click, a session, a page view — count different things. Time zones and reporting calendars push events between days. Blocked scripts, consent choices and browser privacy limits strip events out of one tool but not the other. Conversions also arrive late, so a figure read this morning is not the figure the same report will show next week.

Why data discrepancies matter

Left unexplained, a gap destroys confidence in every number that comes after it. A client shown two totals for the same month reasonably concludes that neither can be trusted, and the meeting that was meant to be about the marketing turns into an argument about measurement.

It also invites the worst habit in reporting: quoting whichever tool tells the better story this month and a different one the month after. The result is a trend line assembled from two incompatible measurements, and it cannot be untangled once a few months have passed.

Common mistakes with data discrepancies

The first is chasing exact parity. Two systems measuring in different ways will never agree, and the hours spent forcing them together are better spent understanding the size and direction of the gap. What matters is that it is stable and explainable — a difference that suddenly changes shape is the genuine signal.

The second is assuming a discrepancy is only ever a reporting quirk. Sometimes it is a real fault: a tag firing twice, a pixel missing from one template, a form that submits without triggering its event. Establishing which of the two you are looking at should come before anyone dismisses it as attribution.

How to act on it

Nominate a source of truth for each type of decision and put it in writing. Platform figures for bidding, because that is what the algorithm learns from. Analytics for comparing channels against each other. The CRM or the accounts for anything touching revenue. Then stop treating one tool as though it were marking the other’s work.

Write the known reasons for the gap down once — windows, time zones, consent, definitions — and reuse that note in every report so the conversation does not restart each month. When the gap is large or moves without explanation, check the collection layer before the reporting layer: duplicate tags, missing events, an attribution window that somebody changed and nobody recorded. If the cause stays hidden, a structured tracking audit works through collection, tagging and configuration in order, which is quicker than arguing about which dashboard is right.

Do and do not

Do

  • Name one source of truth for each kind of decision
  • Document the known causes once and reuse the note
  • Investigate when the gap changes shape

Do not

  • Chase an exact match between two different systems
  • Switch source depending on which looks better
  • Blame attribution before checking the tags

Questions people ask about this

Which number should I report to the client?

Choose one source per decision and hold to it. Use the ad platform's own figures for bidding, because that is what the algorithm learns from. Use analytics when comparing channels against each other. Use the CRM or the accounts for revenue. Name the source on the report itself, so nobody has to guess which system produced the number.

How big a gap between GA4 and Google Ads is normal?

There is no fixed answer, because it depends on consent rates, the browsers your audience uses, how long your buyers take to decide and how each tool is configured. Judge it on stability instead. A gap that keeps roughly the same shape month after month is explainable; one that suddenly changes direction usually points to a tracking fault.

Do ad blockers cause data discrepancies?

They contribute to them. A blocked script means an event never reaches one tool, while a server-side or platform-side record of the same action may still exist, so the totals drift apart. The effect is uneven across audiences, because some groups block far more than others. Server-side collection reduces the problem without removing it.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.