What's the Difference Between Sessions and Users?
A session is a single visit to your website. A user is the person (or more precisely, the browser/device) making that visit. One user can generate multiple sessions, but a single session always belongs to one user.
Think of it like a coffee shop. The number of users tells you how many distinct customers walked in today. The number of sessions tells you the total number of visits, including regulars who came back for a second cup.
Concrete example:
- Alex visits your site Monday morning, browses three pages, then leaves. That is 1 user, 1 session.
- Alex returns Monday afternoon and reads a blog post. That is still 1 user, but now 2 sessions.
- Jordan visits your site Monday evening. You now have 2 users, 3 sessions.
The distinction matters because these metrics answer fundamentally different questions. Users answer "how many people are visiting?" while sessions answer "how much engagement is happening?"
How GA4 Counts Sessions vs Users
GA4 handles session and user tracking differently from Universal Analytics, and the details affect your data accuracy.
How GA4 Defines a Session
A session in GA4 starts when a user triggers a session_start event, which fires automatically when someone opens your site or app. A session ends after 30 minutes of inactivity (this timeout is configurable in GA4 Admin under Data Streams > Configure tag settings, with a range of 5 minutes to 7 hours 55 minutes).
Key session counting rules in GA4:
- No midnight reset. Unlike Universal Analytics, GA4 does not start a new session at midnight. If a user is active from 11:45 PM to 12:15 AM, that counts as one session.
- No campaign reset. In Universal Analytics, arriving via a new campaign source mid-session created a new session. GA4 does not do this. The session continues regardless of campaign parameter changes.
- 30-minute inactivity window. If a user is idle for 30+ minutes and then interacts again, GA4 starts a new session.
How GA4 Identifies Users
GA4 uses a hierarchy of identifiers to recognize returning users:
- User ID (highest priority) -- A custom identifier you assign when users log in. This is the most reliable method because it works across devices.
- Google Signals -- When users are signed into Google and have opted into ad personalization, GA4 can recognize them across devices.
- Device ID / Client ID -- A first-party cookie (
_ga) stored in the browser. This is the fallback and most common identifier.
Each method has limitations. A user who visits from their phone and then from their laptop will be counted as two separate users unless User ID or Google Signals connects them. This is why your "Users" count is almost always slightly inflated.
Active Users vs Total Users
GA4's default "Users" metric is actually Active Users, not Total Users. An active user is anyone who had an engaged session or whose session triggered the first_visit event (web) or first_open event (app). This differs from Universal Analytics, which reported Total Users by default.
When to Use Sessions vs Users
Choosing the right metric depends on what you are trying to measure. Using the wrong one leads to misleading reports and poor decisions.
| Metric | Best For | Example |
|---|---|---|
| Users | Audience sizing and reach | "We reached 50,000 unique people last month" |
| Sessions | Engagement and visit volume | "Our blog generated 120,000 visits last quarter" |
| Sessions per User | Return visit frequency | "Users visit an average of 2.4 times before converting" |
| Users | Deduplication across channels | "How many unique people saw our brand across organic and paid?" |
| Sessions | Capacity planning | "We need server capacity for 10,000 concurrent sessions" |
| Sessions | Comparing page performance | "Product page A gets 3x more visits than product page B" |
| Users | Cohort and retention analysis | "30% of January users returned in February" |
Rules of thumb:
- Reporting to executives on audience growth? Use users.
- Analyzing content engagement and on-site behavior? Use sessions.
- Measuring ad campaign performance? Use sessions for volume and users for reach.
- Evaluating conversion funnels? Use users to understand how many people convert, sessions to understand how many visits it takes.
Sessions Per User Ratio
The sessions-per-user ratio reveals how often people return to your site. It is one of the most underused metrics in GA4.
Formula:
Sessions per User = Total Sessions / Total Users
What the Ratio Tells You
- Ratio close to 1.0 -- Most visitors come once and do not return. Common for informational content and top-of-funnel traffic.
- Ratio of 1.5-2.5 -- Healthy return visit frequency for most B2B and content-heavy sites.
- Ratio above 3.0 -- Strong loyalty signal. Common for SaaS dashboards, news sites, and community platforms.
Benchmarks by Site Type
| Site Type | Typical Sessions/User | Interpretation |
|---|---|---|
| E-commerce | 1.5 - 2.5 | Comparison shopping and return purchases |
| B2B SaaS marketing site | 1.8 - 3.0 | Multi-touch research before demo request |
| SaaS product (logged in) | 5.0 - 20.0+ | Daily active usage |
| News / media | 2.0 - 4.0 | Habitual readers |
| Blog / content site | 1.1 - 1.8 | Mostly one-time search visitors |
How to Use This Metric
Track sessions-per-user over time to spot trends. A declining ratio may signal that your content is not compelling enough to drive repeat visits. A rising ratio often correlates with growing brand recognition and stronger email or push notification programs.
To find this in GA4: navigate to Reports > Acquisition > Overview. The "Users" and "Sessions" cards are both shown. Divide sessions by users manually, or create a custom exploration with both metrics.
Common Reporting Mistakes
1. Adding Sessions Across Channels and Expecting It to Equal Total Sessions
If a single user visits via organic search in the morning and paid search in the afternoon, that is two sessions. If you pull a report by channel and sum the sessions, the total will be correct. But if you do the same with users, the sum will exceed your total users because the same user appears in multiple channels. Users are deduplicated at the report level but not when you sum across rows.
2. Comparing Sessions Between GA4 and Other Tools
GA4, Google Ads, Adobe Analytics, and server-side analytics all define sessions differently. GA4 uses the 30-minute inactivity model with no midnight or campaign resets. Google Ads counts clicks, not sessions. Adobe uses its own visit definition. Comparing raw session counts between tools will always produce discrepancies. Pick one source of truth for each metric and stick with it.
3. Ignoring Cross-Device User Duplication
Without User ID or Google Signals configured, a person who visits from their phone and laptop is counted as two users. For B2B sites where users research on mobile and convert on desktop, this can inflate user counts by 15-30%. If accurate user counts matter to your reporting, implement User ID for logged-in users and enable Google Signals for anonymous users.
4. Reporting Users When You Mean Sessions (and Vice Versa)
A page with "10,000 users" and "25,000 sessions" tells two different stories. Saying "we had 25,000 visitors" when you are reading the sessions metric overstates your audience by 150%. Always label which metric you are reporting and be consistent across dashboards.
Frequently Asked Questions
Can one session have multiple pageviews?
Yes. A session includes everything a user does from arrival to exit (or 30 minutes of inactivity). A single session often contains multiple pageviews, events, and conversions. The number of pageviews per session is a separate metric called "Views per session" in GA4.
Why do I have more sessions than users?
This is expected behavior. Since one user can visit multiple times, sessions will always be equal to or greater than users. If sessions equal users exactly, it means every visitor came only once during the reporting period, which typically indicates a site driven entirely by one-time search traffic.
Does a page refresh count as a new session?
No. Refreshing a page within an active session does not create a new session. It generates a new pageview event within the existing session. A new session only starts after 30 minutes of inactivity or when the user returns after closing the browser and the session has timed out.
How do sessions and users differ between GA4 and Universal Analytics?
In Universal Analytics, sessions reset at midnight and when new campaign parameters are detected. GA4 eliminated both of these resets. This means GA4 typically reports fewer sessions than UA for the same traffic. For users, UA reported "Total Users" by default while GA4 reports "Active Users," so the numbers are not directly comparable. If you are migrating reports from UA to GA4, expect both metrics to shift.
Related Terms
- Organic Traffic - Non-paid search engine visitors
- Bounce Rate - Percentage of non-engaged sessions
- GA4 - Google's current analytics platform
- Engagement Rate - Percentage of sessions with meaningful interaction