Try it on your own data
Every report in this article is in the free plan. One snippet for web and apps, up to 10 sites.
Start freeEvery team that installs a second analytics tool asks the same question in the first week: why are the numbers different? This guide explains the eight causes, from blocked scripts and consent to bots, session rules, identity and time zones, shows a worked example of where a gap actually goes, and gives you a checklist to reconcile two tools in an afternoon.
What you will learn
- The eight reasons two analytics tools disagree, and which number each one moves
- A worked example: bots and consent explain most of a typical gap
- Compare daily uniques, not monthly, and read funnels inside one tool
What changed · Nov 3, 2026
Rewritten around eight causes of mismatched numbers, with a reconciliation checklist, bot and consent examples, and an FAQ.
Why analytics tools show different numbers1. Script blocking and consent2. Bots inflate exactly one side3. Session rules move the line first4. Identity: cookies, hashes and logins5. Estimates instead of exact counts6. Time zones and single-page appsA worked exampleA reconciliation checklistWhy funnels survive the disagreementFAQ
Why analytics tools show different numbers
New section
If you are wondering why analytics tools show different numbers for the same website, it is because a visitor is not a fact the tools read off your site. It is a count each tool builds from its own rules: which requests it receives, which of them it treats as bots, how it groups requests into sessions, how it recognises the same person tomorrow, and which day a visit belongs to. Two tools that make even one of those choices differently will never report the same number of unique visitors, and neither of them is broken.
A pageview is close to a fact: a page loaded and a request arrived. A visitor is an inference. The table lists the eight causes we check, in the order they usually matter, and which tool each one pushes up or down.
| Cause | What differs | Which number it moves |
|---|---|---|
| Script blocking | Ad blockers and privacy browsers stop some analytics scripts from loading | The blocked tool reads lower |
| Consent | A tool that waits for cookie consent does not count people who decline | The consent-dependent tool reads lower |
| Bots | One tool removes crawlers and monitors, the other keeps them | The unfiltered tool reads higher |
| Session rules | Idle timeout, maximum length, midnight and campaign splits | Sessions, and daily uniques a little |
| Identity key | Cookie, device ID, server-side hash or login | Weekly and monthly uniques most |
| Estimation | Some tools approximate distinct counts instead of counting exactly | Small differences on large numbers |
| Time zone | UTC vs. property time zone moves visits across midnight | Daily totals, not monthly |
| Single-page apps | Route changes sent as pageviews or not | Pageviews, then sessions |
1. Script blocking and consent
New section
Browser-based analytics only counts a visit if its script loads and runs. Ad blockers, privacy browsers and corporate filters stop some scripts and not others, often depending on the script's domain and name. Server logs and hosting dashboards do not have this problem, which is one reason they always read higher than any browser-based tool.
Consent is the second filter. A tool that sets cookies usually waits for the visitor to accept them in the regions that require it, and counts nothing for the people who decline. The size of that gap depends on your audience and banner design, so measure it on your own site instead of borrowing someone else's percentage: compare daily visitors in a consent-dependent tool with a tool that does not need consent, for the same pages and days.
2. Bots inflate exactly one side
New section
The biggest single source of disagreement is not a definition at all. It is traffic that one tool counts and another removes. Monitoring services, link previews, search crawlers and AI crawlers all load pages. If tool A removes them and tool B does not, B will always be higher, and the gap will jump on the days a crawler decides to re-crawl you.
TapCub checks each hit against five layers (user agent, request headers, client signals, network and request rate) with 197+ built-in rules, and keeps bot traffic in its own report instead of silently deleting it. By default, recognised bots are excluded from human visitors, sessions and pageviews (how bots are reported). In the sample workspace below, the human line sits about 22% under the all-traffic line, and the gap widens on the two days a crawler visited.
Humans
48,213
▲ 12.4%
All traffic incl. bots
61,902
▲ 19.8%
Sessions
73,480
▲ 10.9%
Daily visitors · last 14 days
HumansAll traffic3. Session rules move the line first
New section
A session is cut by rules, and the rules differ. Google Analytics 4 ends a session after 30 minutes of inactivity by default, and the timeout can be changed per data stream (Google: About Analytics sessions). Other tools also start a new session at midnight or when campaign parameters change mid-visit. A visitor who reads at 23:50 and clicks again at 00:05 is one session under the first rule and two under the second.
TapCub's default is 30 minutes idle and 24 hours maximum; midnight and ad-parameter changes do not split a session unless you turn that on (metric definitions). Before comparing sessions between tools, write both rule sets side by side. Sessions are usually where the first few percent of difference comes from.
4. Identity: cookies, hashes and logins
New section
The identity key decides whether today's visitor is the same person as yesterday's. A cookie-based tool stores an identifier in the browser: it survives a network change but not cleared storage or a second browser. TapCub's default is cookieless: it writes neither a cookie nor local storage, and derives a keyed hash on the server from the site, a salt, the truncated IP address and the browser type. In the balanced preset the salt is kept, so the same browser on the same network is recognised tomorrow; in the strict preset the salt rotates daily and returning visitors are not linked across days (counting modes).
The practical consequence: compare daily unique visitors between two tools, where the models agree on what a person is. Weekly and monthly uniques are different metrics with the same name. Once people log in, a user ID (identify) beats both models, because it follows a person across devices. The cookieless analytics explainer goes through the trade-off.
5. Estimates instead of exact counts
New section
Counting distinct visitors exactly is expensive at scale, so some tools estimate. Google Analytics uses the HyperLogLog++ algorithm to estimate cardinality for metrics including Active Users and Sessions (Google Analytics developer blog, 2022). Estimates are close, but two tools that estimate differently, or one that estimates and one that counts, will disagree slightly even on identical input. That difference is small and stable; if you see a large gap, the cause is one of the others on this list.
Retention settings are a related trap. In GA4, the data retention setting (2 or 14 months on standard properties) affects explorations and funnel reports but not the standard aggregated reports (Google: Data retention). A year-old number pulled from an exploration and the same number from a standard report can therefore differ inside one tool.
6. Time zones and single-page apps
New section
A tool reporting in UTC and a tool reporting in your property's local time put the same late-evening visit on different days, so day-level totals never line up perfectly even when the month does. Check the time zone setting in both tools before comparing anything daily.
Single-page apps are the last fork. A route change in a React or Vue app is not a page load. One snippet sends a pageview on every route change, another only on the first load. Pageviews diverge first; sessions follow when the route change is the only activity keeping a session alive. TapCub's web SDK sends a pageview on history changes by default.
A worked example
New section
Here is how the gap between two tools typically breaks down, using illustrative numbers for one day on one site. Tool A is a cookie-based tool behind a consent banner; tool B counts cookieless and filters bots.
| Step | Daily visitors | Explains |
|---|---|---|
| Tool B, all traffic including bots | 6,190 | Starting point |
| Tool B, humans only | 4,820 | 1,370 bot visitors removed |
| Minus visitors whose browser blocked tool A's script | 4,390 | 430 never reached tool A |
| Minus visitors who declined consent in tool A | 3,240 | 1,150 not counted by tool A |
| Tool A reports | 3,190 | 50 left: session, time zone and estimation differences |
Read it top to bottom: almost the whole gap is explained by two filters, bots on one side and consent on the other. The remaining 1–2% is definition noise you can stop chasing. Your proportions will differ; the method is what transfers.
A reconciliation checklist
Section updated
You can reconcile two tools in an afternoon if you change one thing at a time. Work down the list, fix or note each difference, then move on. Keep the notes next to the dashboards so the next person who asks “why is it different?” finds the answer.
| Check | What to compare | Effect if it differs |
|---|---|---|
| Bot filtering | Compare humans-only in both tools, or all traffic in both | The unfiltered tool reads higher, with spikes on crawl days |
| Missing pages | Is the snippet in the head of every template? | Whole sections missing in one tool |
| Consent | Does one tool count only people who accept cookies? | The consent-dependent tool reads lower |
| Session rules | Idle timeout, maximum length, midnight and campaign splits | Sessions differ by a few percent |
| Identity window | Compare daily uniques, not monthly | Large on monthly, small on daily |
| Time zone | Same reporting time zone in both tools? | Visits shift across midnight |
| Single-page apps | Do both snippets fire on route changes? | Pageviews first, then sessions |
Work top to bottom and change one setting at a time.
Why funnels survive the disagreement
Section updated
A funnel does not need the totals to match anything. It compares steps inside one dataset, counted with one definition. If 2,400 visitors reach the pricing page, 1,248 start checkout, 674 reach payment and 508 complete, the 46% drop between checkout and payment is real under any definition, because every step was counted the same way.
So stop trying to make the totals match and start reading shape. Run both tools in parallel, compare trend lines and the ranking of top pages and sources, and when the shapes agree, pick one tool as the source of truth. The GA4 migration checklist covers the parallel run, and funnel analysis mistakes covers how to build funnels you can defend.
FAQ
New section
Which analytics tool is accurate?
Each is accurate to its own definition. Server logs count requests including bots; a cookie-based tool counts consenting people whose browser ran the script; a cookieless tool counts everyone whose browser ran the script, with a different identity rule. Pick the tool whose definition matches the decision you need to make, and use it consistently.
How big a difference between analytics tools is normal?
There is no universal number. After you align bot filtering, sessions, time zone and the identity window, what remains should be small and stable from day to day. A gap that moves a lot from day to day points to bots or to pages where one script is missing.
Why does Google Analytics show fewer users than my server logs?
Server logs record every request, including bots and visitors whose browser blocked the analytics script or declined consent. Google Analytics only counts browsers that ran its tag, under its own consent and session rules.
Should I compare daily or monthly unique visitors?
Daily. Monthly uniques depend on how each tool links the same person across days, which is exactly where cookie-based, cookieless and login-based tools differ most.
Can I make two tools match exactly?
Not completely, and you do not need to. Align the settings you control, document the rest, and make decisions from trends and funnels inside one tool.
See also: Data Discrepancies: Why Your Analytics Numbers Don't Match.
See also: Cross-Domain Tracking: Setup and a Before and After Check.
Update history1
- Major updateRewritten around eight causes of mismatched numbers, with a reconciliation checklist, bot and consent examples, and an FAQ.
- First published
Was this article helpful?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Analyst
Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.

Data Engineer
Writes about event design, data quality, and collection workflows, with verifiable implementation methods for reliable analytics.



