Products Solutions Templates Pricing Resources

Data discrepancies: why different analytics tools show different numbers

Home / Everything About / Everything About Analytics / Data discrepancies: why different analytics tools show different numbers

You check Google Analytics. It reports 5,000 visitors. You check your server logs. They show 7,000 requests. You check Mixpanel. It reports 4,500 visitors. Three data sources, three different numbers. Which one is right?

All of them. And none of them. Different tools count different things and use different definitions. The discrepancies are normal. Understanding why they exist helps you interpret your data.

Why different tools show different numbers

Different definitions of a "session"

One tool defines a session as 30 minutes of inactivity. Another uses 45 minutes. Another uses 24 hours. A user who leaves your site for 40 minutes and comes back might count as one session in one tool and two sessions in another. Session count will always differ.

Different pageview counting rules

Some tools count only traditional pageviews. Others count virtual pageviews from single-page apps. Some count pushState events as pageviews. Others don't. Pageview counts vary based on these differences.

Different bot filtering

Tool A filters out search engine bots. Tool B doesn't. Tool C uses a different bot list. Bot filtering differences change traffic totals. You'll always see different numbers if tools filter differently.

Different data collection timing

Server logs record at the server level at the millisecond the request arrives. Analytics libraries collect client-side and batch requests. If a user closes their browser before the analytics request sends, it gets lost. Server logs capture it. Client-side tools don't.

Different timezone handling

You have Google Analytics set to Eastern Time and server logs in UTC. Daily totals align differently. Yesterday's data might include today's server traffic if timezones don't sync. Small discrepancies appear.

Different attribution models

Tools use different attribution rules. Some use last-click. Some use first-click. Some use time decay. If you have multiple touchpoints before conversion, different tools will credit different sources. Multi-touch attribution will never match last-click attribution.

Different traffic classification

Tool A classifies traffic from a certain source as organic. Tool B classifies it as direct. Tool C classifies it as referral. Each tool uses different rules. Source distribution will differ.

Common discrepancy patterns

Google Analytics showing lower numbers than server logs

This is typical. Server logs show all requests. Google Analytics misses traffic blocked by ad blockers, blocked by tracking prevention, or where the tracking code fails to fire. Google Analytics is usually 20-40% lower than server logs.

Conversion counts differing from payment processor

Analytics might track more conversions than your payment processor because it counts abandoned checkouts or other events as conversions. Or it might track fewer if some conversions complete offline or on third-party platforms.

Organic traffic discrepancies across tools

Different tools classify organic differently. Google Search Console shows organic keywords. Google Analytics shows organic traffic. They rarely match exactly because they measure different things at different stages of the journey.

Traffic source differences

A click from Facebook might be classified as "direct" in one tool and "social" in another depending on how the URL is tagged and how tools classify unmarked traffic.

How to handle discrepancies

Understand what each tool measures

The first step: know what each tool is counting. Google Analytics counts pageviews and events. Server logs count HTTP requests. Your payment processor counts transactions. They're measuring different things, so differences are expected.

Pick one source of truth for each metric

Choose which tool owns which metric. "Google Analytics owns traffic metrics." "Shopify owns conversion metrics." "Server logs own technical diagnostics." When you need traffic, you always check Analytics. This prevents confusion.

Document the discrepancies and explain them

For major discrepancies, document them. "Google Analytics shows 5K visitors. Server logs show 7K. Difference is explained by ad blockers blocking tracking code (~40% of traffic)." Document the explanation so your team understands.

Create a reconciliation process

Monthly, compare your main tools to each other. Google Analytics vs. Mixpanel. Google Analytics vs. payment processor. Check whether the gap is consistent. If it suddenly changes, investigate why.

Use the most complete data source for analysis

If you need real transaction data, use your payment processor. If you need traffic patterns, use server logs. If you need user behavior and segments, use analytics tools. Each source is best for certain questions.

Tools should complement each other

Build a complete picture from multiple sources

Instead of fighting discrepancies, use them as intended: each tool provides a different view. Analytics shows user behavior. Server logs show traffic patterns. CRM shows customer data. Payment processor shows revenue. Together they're more complete than any single tool.

Use discrepancies to find problems

When discrepancies change suddenly, something might be broken. Tracking might have failed. Filters might have been applied. The difference reveals the issue.