Why Do Adobe Analytics, GA4 and Session Replay Tools Never Agree on Sessions?
Adobe Analytics, GA4 and session replay tools never agree on sessions because each defines a session differently and sees a different set of visitors. Inactivity timeouts, midnight resets, consent banners, ad blockers, bot filtering and where each tag loads all change the count. Compare trends and rates, not raw totals.
Last updated November 16, 2026
It is one of the most common moments in any analytics evaluation: one tool reports one number of sessions for the week, another reports nearly twice as many, and someone asks which one is broken. Usually neither is. The tools are answering slightly different questions. This post explains the definitions behind each count and a practical way to reconcile them.
Key takeaways
- Adobe Analytics, GA4 and session replay tools each use a different rule for when a session starts and ends.
- Consent banners and ad blockers hide some visitors from some tools and not others.
- Bot filtering, tag placement and single-page app tracking widen the gap further.
- Choose one source of truth per decision and compare rates and trends, not absolute session totals.
Part of: Noibu's CRO Agent
How does each tool define a session?
Adobe Analytics calls a session a visit. Adobe's documentation on the Visits metric says a new visit begins after more than 30 minutes between hits, after 12 hours of continuous activity, or after 2,500 image requests. It also ends a visit with more than 100 hits in its first 100 seconds, a pattern that usually means a bot.
Google Analytics 4 says in its help article on sessions that a session ends after 30 minutes of user inactivity by default, and that web properties can change the timeout. Noibu's help center notes that a GA4 session also ends at midnight, even if the visitor is still browsing.
Session replay tools set their own rules. Noibu's help center explains in why GA4 session counts differ from Noibu that a Noibu session stays active for the whole visit while the browser tab stays open, so one visit can be one session in Noibu and several in GA4.
| Rule | Adobe Analytics | GA4 | Noibu |
|---|---|---|---|
| Inactivity timeout | 30 minutes | 30 minutes by default, adjustable | No inactivity timeout while the tab is open |
| Midnight reset | Not part of the visit definition | Session ends at midnight | No midnight reset |
| Other limits | 12 hours or 2,500 hits starts a new visit | None stated in the help article | None stated in the help article |
| Loads before consent? | Depends on your setup | Often set up to load before the banner | Usually deployed behind the banner |
What else makes session counts disagree?
Consent banners. Tools that load before the banner record visitors who later decline cookies; tools that load after it do not. Noibu's help article notes that a meaningful share of visitors reject cookies when asked, so this one setting can move counts a long way between tools on the same site.
Ad blockers and privacy tools. Browser extensions and some VPNs block analytics and replay scripts. Which scripts get blocked depends on the extension's lists, so one tool can lose visitors that another still sees.
Bots. Each tool filters automated traffic differently, and some installs add custom filters on top. Bot surges, which are common during peak season, inflate whichever tool filters least. The causes and checks are covered in how bot traffic distorts ecommerce analytics.
Tag placement and page coverage. A tag missing from checkout, a subdomain or a landing page builder drops those sessions from one tool only. Checkout on a separate domain can also split one visit into two sessions if cross-domain tracking is not configured.
Single-page apps and headless storefronts. When pages change without a full reload, each tool needs to be told about the new page. Differences in how that is set up change page views and, in some tools, session boundaries.
How do you reconcile session counts across tools?
Reconcile session counts in five steps
- 1
Match the window
Use the same dates and time zone in every tool before comparing anything.
- 2
Read each definition
Note each tool's timeout, midnight rule and visit limits, as in the table above.
- 3
Check consent and blocking
Record which tags load before the consent banner and which wait for it.
- 4
Audit tag coverage
Confirm every tool fires on every template, including checkout and other domains.
- 5
Compare rates, not totals
Compare conversion rate, add-to-cart rate and trends, where definitions matter less.
After those checks, a stable gap between tools is normal and fine. What matters is that each tool is consistent with itself over time. A sudden change in the gap is the signal worth investigating, because it often means a tag stopped firing or a consent setting changed. The same logic applies to platform reports, covered in why Shopify Analytics and GA4 show different sessions and orders.
Which tool should be the source of truth?
Pick by decision, not by tool. Marketing attribution usually runs on the tool connected to ad platforms. Finance runs on orders from the commerce platform. Questions about why shoppers struggle on a page, where errors and slow pages cost conversions, and what a shopper saw, are best answered by the tool that records behavior and technical detail together. Teams carrying several overlapping tools can find which ones to keep in how to audit overlapping analytics tools before renewal.
How does Noibu use session data?
Noibu records sessions with the technical and behavioral detail behind them: errors, page performance, funnels and heatmaps. Noibu's CRO agent uses that data to find underperforming product pages and rewrite them to convert better. Your team reviews the changes, can edit them inline and publishes when ready. Because the agent works from conversion rates on the same session definition every time, the cross-tool gap does not affect which pages it ranks as worst.
The CRO agent is one of six supervised agents, with Bug Resolution, Performance, ADA, A/B Testing and ROAS. Each follows the loop of find, build, your approval, ship and measure, in the Noibu console and in AI tools such as Claude through Noibu MCP.
Frequently asked questions
Why does Adobe Analytics show more sessions than GA4?
The two tools count differently. Adobe Analytics starts a new visit after 30 minutes of inactivity, after 12 hours of activity or after 2,500 hits, while GA4 uses a 30-minute default timeout that can be changed. Consent setup, bot filtering and tag placement also differ between installs.
Why does my session replay tool show fewer sessions than GA4?
Session replay scripts often load behind the cookie consent banner and can be stopped by ad blockers or privacy extensions, so visitors who decline or block are not recorded. Replay tools may also keep one session open for a whole visit instead of splitting it on a timeout.
Which tool has the correct session count?
None of them is wrong. Each one applies its own definition to the visitors it can see. Pick one tool as the source of truth for each decision and compare trends rather than absolute counts.
How does Noibu count sessions?
Noibu's help center says a Noibu session stays active for the whole visit while the browser tab is open, without GA4's 30-minute inactivity timeout or midnight reset. Noibu is usually deployed behind the consent banner, so visitors who decline cookies are not recorded.
How do I reconcile session counts across tools?
Compare the same date range and time zone, check each tool's timeout and consent setup, confirm tags load on every page including checkout, apply the same bot filtering, and compare ratios such as conversion rate rather than raw session totals.
What does Noibu's CRO agent use session data for?
Noibu's CRO agent finds underperforming product pages and rewrites them to convert better. It works from Noibu's sessions, funnels, errors, performance and heatmap data, and your team reviews changes before publishing.
The short version
Adobe Analytics, GA4 and session replay tools disagree on sessions because they use different timeouts and resets, see different visitors after consent and blocking, and filter bots differently. Align dates, definitions, consent and tag coverage, then compare rates and trends. To see where your store loses shoppers, start with Noibu's free website audit.
Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.
