⚡ TL;DR: Users count unique people visiting your site. Sessions count individual visits — one user can have many sessions. GA4 defaults to "Active Users" (users who had an engaged session), not total users. Use users to understand audience size, sessions to understand visit behaviour and traffic patterns.
If you've ever looked at a Google Analytics 4 report and wondered why your user count and session count don't match — or why "Users" in GA4 seems different from what you remember in Universal Analytics — you're not alone. The sessions vs users distinction is one of the most common sources of confusion in GA4, and misunderstanding it can lead to poor decisions about your marketing and content strategy. Meaning's natural language analytics platform lets you ask questions like "how many users visited last week vs this week?" and get instant, plain-English answers from your GA4 data.
In this guide, we'll break down exactly what each metric means in GA4, how Google counts them, when to use one over the other, and how to avoid the most common mistakes analysts make when interpreting these numbers.
What is a user in GA4?
A user in GA4 represents a unique individual who interacts with your website or app. But the word "unique" deserves some unpacking, because GA4 actually tracks three different user metrics:
Active users (the default)
Key Takeaway: The "Users" number in every standard GA4 report is Active Users — not all visitors. Anyone who bounces in under 10 seconds without a key event is excluded. Your true total audience is always larger than what GA4 shows by default.
When you see "Users" in any standard GA4 report, you're actually looking at Active Users — not total users. This is a crucial distinction that catches many people off guard.
An Active User is someone who has had an engaged session or triggered specific events. GA4 considers a session "engaged" if it meets any of these criteria:
- The session lasted longer than 10 seconds
- The user viewed 2 or more pages/screens
- The user triggered a conversion event (now called a "key event")
This means a visitor who lands on your site, spends 3 seconds, and leaves is technically a user — but not an Active User. They won't show up in your default "Users" column.
Total users
Total Users counts every unique visitor who initiated at least one session during the selected time period, regardless of engagement. This is closer to what Universal Analytics used to report as "Users."
You can find Total Users by adding it as a metric in GA4's Explorations or by customising your reports.
New users
New Users counts visitors who interacted with your site for the first time during the selected period. GA4 identifies new users based on the absence of a previously stored user identifier (typically a cookie or User ID).
How GA4 identifies users
GA4 uses a hierarchy of identifiers to recognise returning users:
- User ID — A custom identifier you assign (e.g., login credentials). Most reliable.
- Google Signals — Cross-device tracking for users signed into Google with ads personalisation enabled.
- Device ID — A client ID stored in a browser cookie. Least reliable, since clearing cookies creates a "new" user.
This means the same person browsing on their phone and laptop could be counted as two users unless User ID or Google Signals connects the dots.
Practical example: Imagine Sarah visits your online shop from her work laptop during lunch, then checks it again from her phone that evening. Without User ID or Google Signals, GA4 sees two separate users. With Google Signals enabled (and Sarah signed into Chrome on both devices), GA4 recognises her as one user with two sessions.
What is a session in GA4?
A session represents a single visit to your website or app. It begins when a user opens your site and ends after a period of inactivity. But GA4 handles sessions quite differently from Universal Analytics, and these differences matter.
How sessions start and end
A session starts when a user triggers the session_start event — typically by loading a page. The session ends after 30 minutes of inactivity (this timeout is configurable in your GA4 property settings, from 5 minutes up to 7 hours and 55 minutes).
Key differences from Universal Analytics:
- Midnight doesn't split sessions. In UA, a session active at midnight was cut in two. GA4 keeps it as one session.
- Campaign changes don't create new sessions. In UA, if a user clicked a new campaign link mid-session, it started a fresh session. GA4 does not restart sessions when the campaign source changes.
- There's no hard session limit. UA capped sessions at specific durations. GA4 sessions can theoretically last as long as the user remains active.
These changes mean that GA4 will generally report fewer sessions than UA would for the same traffic, which can be alarming if you're comparing historical data.
Engaged sessions
Engaged Sessions are sessions that lasted longer than 10 seconds, included a key event, or involved 2 or more page views. GA4's Engagement Rate (engaged sessions ÷ total sessions) is the platform's modern replacement for the old bounce rate — a more meaningful signal of whether visitors found value in your content.
GA4 introduces the concept of Engaged Sessions — sessions that lasted longer than 10 seconds, had a key event, or involved 2+ page views. This metric feeds directly into the Engagement Rate (engaged sessions ÷ total sessions) and is GA4's replacement for the old bounce rate logic.
Sessions vs users: a side-by-side comparison
| Aspect | Users (Active Users) | Sessions |
|---|---|---|
| What it counts | Unique people (engaged) | Individual visits |
| One person, three visits | 1 user | 3 sessions |
| Scope | Cross-session | Single visit |
| Best for | Audience size, reach | Visit behaviour, traffic volume |
| Affected by cookies | Yes — cleared cookies = "new" user | Less so — each visit is a session regardless |
| GA4 default | Active Users (engaged) | All sessions |
A real-world scenario
Suppose your GA4 report for last week shows:
- Users: 5,000
- Sessions: 8,200
- New Users: 3,100
Here's what this tells you:
- 5,000 unique active people visited your site (and were engaged enough to count)
- Those people collectively made 8,200 visits — meaning on average, each user visited about 1.64 times
- 3,100 of those users were visiting for the first time, so roughly 1,900 were returning visitors
This is valuable context. A high sessions-per-user ratio suggests strong return traffic — people coming back repeatedly. A ratio close to 1.0 means most visitors come once and don't return.
When to use users vs sessions
Choosing the right metric depends entirely on what question you're trying to answer.
Use users when...
- Measuring audience reach: "How many people saw our campaign landing page?"
- Assessing growth: "Is our audience growing month over month?"
- Segmenting: "How many users from the UK converted?"
- Calculating per-user metrics: Revenue per user, events per user, etc.
Use sessions when...
- Analysing traffic patterns: "How many visits did we get from organic search this week?"
- Evaluating landing pages: "Which pages attract the most visits?"
- Measuring engagement depth: Sessions paired with engagement rate tell you about visit quality.
- Comparing channels: "Does paid search drive more visits than email?"
Use both together when...
- Understanding loyalty: A high sessions-to-users ratio indicates repeat visits.
- Diagnosing problems: If users are flat but sessions are dropping, your existing audience is visiting less often.
- Reporting to stakeholders: Users for reach, sessions for activity. Together they tell the full story.
Tools like Meaning let you ask these kinds of questions in plain English — for instance, "How many returning users do I have this month?" or "What's my sessions per user from organic search?" — without needing to build custom reports or navigate GA4's interface.
Common mistakes and misconceptions
Mistake 1: assuming "Users" means total visitors
As we covered, the default "Users" metric in GA4 is Active Users, not Total Users. If someone bounces in under 10 seconds with no key event and only one page view, they're excluded from the Active Users count. This can make your audience look smaller than it actually is.
Fix: If you need a complete headcount, use Total Users in Explorations or free-form reports.
Mistake 2: comparing GA4 sessions to Universal Analytics sessions
GA4 counts sessions differently — no midnight splits, no campaign restarts. Comparing session counts between GA4 and UA will almost always show a discrepancy, and that's expected. It doesn't mean your tracking is broken.
Fix: Treat GA4 data as a fresh baseline. Compare GA4 periods to other GA4 periods, not to UA.
Mistake 3: thinking one user = one device
Without User ID or Google Signals, each device (or browser, or cleared cookie) creates a separate user identity. This inflates user counts.
Fix: Enable Google Signals in your GA4 property settings, and implement User ID if you have a login system.
Mistake 4: ignoring sessions per user
Many teams report users OR sessions, but rarely look at the ratio. Sessions per user is a simple but powerful indicator of audience loyalty and content stickiness.
Fix: Add "Sessions per User" to your regular reporting. In GA4, you can calculate this by dividing sessions by users, or ask a tool like Meaning to surface it directly: "What's my average sessions per user this quarter?"
Mistake 5: using sessions to measure campaign success
Sessions tell you how many visits a campaign drove, but not how many people it reached. If one enthusiastic person clicked your ad 10 times, that's 10 sessions but only 1 user.
Fix: Use users (specifically new users) to measure campaign reach, and sessions to measure activity volume.
How to find these metrics in GA4
In standard reports
Navigate to Reports → Life cycle → Acquisition → Traffic acquisition. Here you'll see Sessions, Users, and New Users broken down by channel. The "Users" column is Active Users by default.
In explorations
For more flexibility, go to Explore → Free form. You can add both "Active Users" and "Total Users" as metrics, alongside Sessions and Engaged Sessions. This lets you compare the full picture side by side.
Using the realtime report
The Realtime report shows users active in the last 30 minutes. This is useful for monitoring campaign launches or content drops, but remember — it's a snapshot, not a trend.
Asking in plain English
If navigating GA4's interface feels overwhelming, conversational analytics tools offer a simpler path. With Meaning, you can connect your GA4 property and ask questions like:
- "How many users visited my site last week?"
- "What's the difference between my total users and active users?"
- "Show me sessions per user by traffic source"
You get instant answers without building reports from scratch — particularly useful for marketers and founders who need insights quickly but aren't analytics specialists.
Sessions, users, and your reporting strategy
Here's a practical framework for incorporating both metrics into your regular reporting:
Weekly check-ins
Track sessions and active users week over week. Look for:
- Sudden drops in sessions (possible tracking issues or traffic loss)
- Users growing faster than sessions (new audience, but low return rate)
- Sessions growing faster than users (existing audience becoming more engaged)
Monthly reviews
Compare new users vs returning users alongside total sessions. Calculate sessions per user to gauge loyalty trends. Segment by channel to see which acquisition sources bring the most engaged audiences.
Quarterly strategy
Use user-level data to assess audience growth and session-level data to evaluate content performance. Are you attracting new people? Are they coming back? Which pages or campaigns drive the most repeat visits?
Frequently asked questions
What is the difference between users and sessions in Google Analytics 4?
Users represent unique individuals who visit your site, while sessions represent individual visits. One user can generate multiple sessions. By default, GA4 reports "Active Users" — users who had an engaged session (lasting 10+ seconds, with 2+ page views, or a key event).
Why does GA4 show fewer sessions than Universal Analytics?
GA4 doesn't restart sessions at midnight or when campaign parameters change, unlike Universal Analytics. This typically results in lower session counts for the same traffic. The data isn't wrong — GA4 simply measures sessions differently.
What is an active user in GA4?
An Active User is someone who had at least one engaged session during the reporting period. An engaged session lasts longer than 10 seconds, includes 2 or more page/screen views, or triggers a key event. This is the default "Users" metric in all standard GA4 reports.
How does GA4 identify unique users across devices?
GA4 uses a hierarchy: User ID (custom login-based identifier), Google Signals (cross-device for Google-signed-in users), and Device ID (cookie-based). Without User ID or Signals, the same person on two devices counts as two users.
What is a good sessions-per-user ratio?
This varies by industry and site type. E-commerce sites often see 1.3–1.8 sessions per user, while content and media sites may see 2.0+ as readers return regularly. A ratio near 1.0 suggests most visitors don't return, which may indicate a loyalty or content problem.
Can I see total users instead of active users in GA4?
Yes. Total Users isn't shown in standard reports by default, but you can add it as a metric in GA4 Explorations (free-form reports). Total Users includes everyone who initiated a session, regardless of engagement level.
Wrapping up
The difference between sessions and users in GA4 is conceptually simple — users are people, sessions are visits — but the devil is in the details. GA4's default to Active Users, its changed session logic, and its cross-device identification methods all add layers of complexity that can trip up even experienced analysts.
The key takeaway: always know which metric you're looking at and why. Use users to understand your audience, sessions to understand behaviour, and both together to get the complete picture. And if you'd rather skip the report-building and just ask your data a question, tools like Meaning make that straightforward — connect GA4, type your question, and get your answer.