GA4 sessions vs users explained for clients
Every agency has had this call. You send the monthly report, the client scans the traffic section, and the first question back is "why does it say 1,240 sessions but only 890 users - which one is the real number?"
Both are real. They count different things. A user is a person (well, a browser with a cookie). A session is one visit that person made. One user can come back five times in a month, which is five sessions and still one user. That is the whole idea in two sentences, and it is the version you should be putting in front of clients instead of a screenshot of the GA4 interface.
This post covers what GA4 counts as a session, the difference between active users and total users, how to read the new vs returning users report, and how to phrase both metrics in a client report so nobody has to ask. For the wider metric set, start with our guide to GA4 metrics explained for clients.
Last updated: August 2026
Key takeaways
- A user is a person; a session is a visit. One user can generate many sessions, so sessions are almost always the larger number.
- A GA4 session ends after 30 minutes of inactivity by default, and the next activity from that same user starts a new session. The timeout is adjustable in the property's data settings.
- GA4's headline "Users" number is Active users, not Total users. Active users only counts people who actually engaged; total users counts everyone who fired any event.
- Sessions per user is the ratio worth reporting. Anything close to 1.0 means almost nobody is coming back; above roughly 1.5 means the audience returns.
- Never report sessions and users side by side without a one-line explanation. The gap between them is the thing clients query, and one sentence prevents the email.
What this post covers
- What is the difference between sessions and users in GA4?
- What counts as a session in GA4?
- Active users vs total users in GA4
- Why sessions are always higher than users
- How to read the new vs returning users report
- Why GA4's user count never matches Google Ads or your CRM
- How to present sessions and users in a client report
- FAQs
Sessions vs users at a glance
| Metric | What GA4 counts | What you tell the client | Watch out for |
|---|---|---|---|
| Users (Active users) | Distinct people who had an engaged session or triggered an engagement signal | "How many different people visited" | This is the default "Users" in most GA4 reports |
| Total users | Every distinct person who fired any event at all | "Everyone who loaded the site, engaged or not" | Only surfaces in some reports and explorations; always higher than active users |
| New users | People whose first ever visit fell in the date range | "People who found you for the first time" | Cookie deletion and new devices recreate "new" users |
| Sessions | Individual visits, split by a 30-minute inactivity timeout | "How many separate visits those people made" | One person browsing across a lunch break can be two sessions |
| Engaged sessions | Sessions over 10 seconds, with 2+ pageviews, or with a key event | "Visits where someone actually did something" | Powers engagement rate, the metric that replaced bounce rate |
| Sessions per user | Sessions divided by active users | "How often the average visitor comes back" | The single most useful ratio for a retention story |
What is the difference between sessions and users in GA4?
In GA4, a user is one identified person and a session is one visit by that person, so a single user can produce many sessions in the same reporting period. GA4 identifies a user by a first-party cookie (or by User-ID or Google signals if you have those switched on), and it groups that user's activity into sessions using a timeout.
Think of it like a shop. Users are the people who walked in this month; sessions are the number of times the door opened. One loyal customer visiting every Friday is one person and four door-openings.
This is why the two numbers should never match, and why "users down, sessions up" is a readable story: fewer people, visiting more often. It usually means remarketing or email is working while acquisition has stalled.
Google Analytics Help documents both metrics in its user and session references. Those are the definitions your client's next agency will quote too, so stay aligned with them rather than inventing house definitions.
What counts as a session in GA4?
A GA4 session starts when someone triggers the session_start event and ends after 30 minutes with no activity, which is the default session timeout you can change in your property's data collection settings. If that same person returns 45 minutes later, GA4 records a second session. If they return five minutes later, it is still the first one.
Three things about the GA4 session definition regularly surprise people who came from Universal Analytics:
- Campaign changes do not start a new session. In Universal Analytics, arriving from a different source mid-visit split the visit in two. GA4 does not do this, which is one reason GA4 session counts often read lower than the old UA numbers for the same site.
- The timeout is configurable from 5 minutes up to 7 hours 55 minutes. Raising it lowers your session count and raises your average session duration, so if a client's session numbers drop off a cliff, check this setting before you write a paragraph about seasonality.
- Sessions are attributed to the day they started. A visit beginning at 11:50pm sits in that day's figure, not the next day's.
The practical version for the report: a session is one visit, and a visit is considered finished after half an hour of doing nothing.
Active users vs total users in GA4
GA4's default "Users" metric is Active users, which counts people who had an engaged session or otherwise showed an engagement signal, while Total users counts every person who triggered any event at all. Total users is the bigger number and the one closest to the old Universal Analytics "Users".
Both metrics are listed separately in the GA4 Data API schema as activeUsers and totalUsers, which is worth knowing if you pull GA4 data programmatically. If a client compares the Users figure in a standard report against a Total users column from an exploration, the two disagree by design, not because anything is broken. This is the most common cause of "your report doesn't match what I see in Analytics" emails.
Our rule for client-facing work: report Active users, label it plainly as "visitors who engaged with the site", and keep total users for internal diagnostics. Clients care about people who did something. A bot-adjacent bounce that fired a single page_view is not a lead.
If engagement terminology is new to the client, our breakdown of GA4 engagement rate vs bounce rate explains the engaged-session threshold in the same plain terms.
Why sessions are always higher than users
Sessions exceed users because every user generates at least one session, and returning visitors generate several. Divide sessions by active users and you get sessions per user, which is a far better retention signal than either number on its own.
A rough reading for most service and local business sites:
| Sessions per user | What it usually means |
|---|---|
| 1.0 to 1.1 | Almost nobody returns. Traffic is one-and-done, usually paid or cold. |
| 1.2 to 1.5 | Normal for a small business site with a mix of paid and organic. |
| 1.6 and above | A genuinely returning audience: email, brand search, or a strong content library. |
The ratio also protects you when raw traffic dips. A month where sessions fall but sessions per user climbs from 1.2 to 1.5 is a month where the audience got better, and saying so turns a bad-looking chart into a strategic point.
How to read the new vs returning users report
GA4's new vs returning users report splits your audience by whether the visitor's first ever visit happened during the reporting window, with new users identified by the first_visit event. It is the fastest way to show a client whether growth is coming from reach or from loyalty.
Two caveats to state out loud before a client draws the wrong conclusion:
- "New" is browser-new, not human-new. Someone who clears cookies, switches from mobile to desktop, or opens the site in a private window is counted as a new user again. Cross-device inflation is normal and it is not a tracking fault.
- Returning users need history to exist. A property that was only set up eight weeks ago cannot show a meaningful returning cohort yet, and GA4's default data retention setting of two months for exploration data can also cut historical comparisons short.
For most client reports, the useful framing is a simple share: "72% of visitors this month were first-timers, up from 64%." That is a reach story. When the returning share climbs instead, it is a retention story, usually driven by content and email rather than ad spend. Pair it with the GA4 traffic acquisition report to show where the new people came from.
Why GA4's user count never matches Google Ads or your CRM
GA4 counts users with a first-party cookie in a browser, so it will never agree exactly with Google Ads clicks, Search Console clicks, or the contact records in your client's CRM. Each system counts a different object.
The main causes of the gap, in the order they usually matter:
- Consent and tracking prevention. Rejected cookie banners, ad blockers and browser privacy defaults mean a share of real people are never counted, or are counted as modelled data.
- Different units. Google Ads Help defines a click as an ad interaction, not a person. One person clicking twice is two clicks and one user.
- Cardinality estimation. GA4 approximates distinct user and session counts at scale, so large numbers carry a small margin rather than being an exact tally.
- Time zones. GA4 reports in the property's time zone; ad platforms report in the account's.
None of this is a defect, and clients handle it fine when you tell them once, upfront, in the report. It goes wrong when they find the discrepancy themselves three months in. Our post on Search Console vs GA4 organic traffic covers the same reconciliation for organic numbers.
How to present sessions and users in a client report
The fix for sessions vs users confusion is not a better dashboard, it is a labelled sentence next to the number. Put "1,240 visits from 890 different people" in the report and the question never gets asked.
We built ReportsMate email-first because, after years around agency reporting, the dashboards clients were handed almost never got logged into. The report that lands in the inbox is the one that gets read, and a metric with a plain-English label attached is the one that gets understood.
GA4 is the platform this matters most for. Across the client accounts connected to ReportsMate today, roughly 7 in 10 clients with any platform connected have a GA4 property attached, making it the most-connected platform on the system, and the average client has just under two platforms connected. GA4 does the heavy lifting in most agency reports, so the way its metrics get labelled sets the tone for the whole document.
Three habits that hold up across client types:
- Lead with users, support with sessions. People first, visits second, because that is how non-marketers think.
- Report the ratio, not just the totals. Sessions per user gives the numbers a direction.
- Keep the definitions identical every month. Switching from active users to total users mid-engagement, even by accident, costs you trust in the whole document.
You can see how the automated version handles this in our GA4 integration, or read the GA4 report documentation for the exact fields that get pulled through.
Frequently asked questions
Q: Is GA4 sessions the same as visits?
A: Yes, a session is GA4's name for a visit. One session covers everything a person does on your site from the moment they arrive until they have been inactive for 30 minutes, at which point the next thing they do starts a fresh session. The word "visits" is usually the better one to use in a client report because it needs no explanation. If your client came from Universal Analytics, the concept is the same, but GA4 no longer splits a visit into two when the traffic source changes mid-visit, so GA4 session counts often read a little lower than the old UA figures for identical traffic.
Q: What is the difference between active users and total users in GA4?
A: Active users counts people who had an engaged session or produced an engagement signal; total users counts every person who triggered any event, engaged or not. Active users is the default "Users" metric in standard GA4 reports, so it is the number your client sees in the interface, and it is the number we recommend reporting. Total users is always the larger figure and mainly appears in explorations. If two reports disagree on user counts, this is usually why, not a tracking problem.
Q: What is the GA4 session timeout and can I change it?
A: The default GA4 session timeout is 30 minutes of inactivity, and yes, you can change it in the property's data collection and modification settings to anything from 5 minutes up to 7 hours 55 minutes. Changing it changes your numbers, so treat it as a reporting decision, not a technical tweak. A longer timeout produces fewer sessions and a longer average session duration. If a client's session count moves sharply with no matching change in traffic, check whether this setting was edited before you attribute the shift to anything else.
Q: How do I explain new vs returning users to a client?
A: Say it as a share of the audience: "68% of the people who visited this month had never been to the site before." New users are people whose first ever visit landed inside your date range, identified by GA4's first_visit event. Add the caveat once that "new" means a new browser rather than a new human, so cookie clearing and device switching inflate it slightly. A rising new share is a reach and acquisition story; a rising returning share is a retention and content story. Both are good news, but they justify different budget decisions next quarter.
Q: Should I report sessions or users to clients?
A: Report users first and sessions second. Clients think in people, so "890 people visited your site, making 1,240 visits between them" lands immediately, whereas a bare session count invites the question you are trying to avoid. Keep the pairing consistent every month and add sessions per user when you want to show whether the audience is sticking around. The one thing to avoid is switching which metric leads your traffic section between reports, because the month-on-month comparison stops making sense.
Getting this right without writing it out every month
Sessions vs users is not a hard concept. It gets explained badly, or not at all, because the metric arrives with no label attached. The agencies whose clients never ask about it are the ones whose reports answer it in advance, in the same words every month.
That is a template problem more than an analytics problem. Write the plain-English framing once, put it beside the metric, and let the reporting run on a schedule so it comes out identically each month. Consistency is what makes a client stop auditing your numbers and start reading your recommendations instead.
Stop losing your Sundays to client reports. See how ReportsMate works or start your free 14-day trial - no credit card, no setup fees, cancel anytime. Your clients get branded, plain-English GA4 reports in their inbox automatically, with the metrics labelled so nobody has to guess which number is the real one.