Attribution & Analytics 6 min read

Understanding Sessions, Users, and Events in Plain English

Sessions measure visits, users measure reach, and events measure actions, mixing them up is the most common source of misread GA4 reports.

P

Priya Nair

Senior Marketing Analyst

August 15, 2026|
UTMLOOP COMPREHENSIVE VIEW

Attribution & Analytics Blueprint Guide

What is a session in GA4?

A session is a single visit to your website, the continuous stretch of time someone is actively engaged with your site. GA4 starts a new session when a visitor arrives and generally ends it after about thirty minutes of inactivity or when a new day begins, though platform-specific rules can affect exactly when a session closes. One person visiting your site multiple times across multiple days generates multiple separate sessions, even though it's the same individual each time.

What is a user in GA4?

A user is a distinct browser or device, GA4 identifies users through this technical proxy rather than true individual identity, interacting with your site, potentially across many separate sessions over time. If the same person visits five times over a month, that's five sessions but only one user. A campaign with sessions far exceeding users suggests strong repeat engagement from a smaller group of people; sessions and users nearly equal suggests it's mostly reaching new, one-time visitors.

What is an event in GA4?

An event is a specific action taken during a session, a page loading, a button clicked, a video played, a form submitted, a purchase completed. GA4's entire data model is built around events as the fundamental unit of measurement, with sessions and even page views themselves tracked as specific types of events under the hood, which is part of why GA4's interface feels different from older, page-view-first analytics tools.

How do sessions, users, and events relate to each other?

A single user can have many sessions over time, and within each session, many events can occur. If someone visits your site once (one session, one user), views three pages, watches a video, and completes a purchase, that single session contains at minimum five distinct events, three page views, one video-related event, and one purchase event, all attributed to the same user and session.

Which metric should you actually look at for campaign performance?

It depends on the question. Sessions tell you about traffic volume, including repeat visits. Users tell you specifically about reach, how many distinct people your campaign touched, regardless of how many times each visited. Events, particularly conversion-related ones, tell you about actual engagement and outcomes. A campaign report showing only sessions gives an incomplete, potentially misleading picture of true impact.

What's the most common mistake when reading these metrics?

Treating session count as a rough proxy for how many distinct people a campaign reached, when it may reflect a smaller number of people returning repeatedly. A campaign showing 1,000 sessions but only 400 users is meaningfully different from one showing 1,000 sessions and 950 users, even though the session totals match, the first suggests a smaller, more engaged audience, the second a broader, largely one-time audience.

What is an engaged session, and how is it different?

An engaged session is a session lasting at least ten seconds, including a conversion event, or including at least two page or screen views, essentially a session showing genuine engagement rather than an immediate bounce. Comparing total sessions to engaged sessions for a given campaign provides a useful, if imperfect, signal about traffic quality, distinct from raw volume alone.

Frequently Asked Questions

Can one user have more sessions than events?

No, every session contains at least one event by definition, since GA4 tracks session starts and page views themselves as events, so total events for a user will always be at least as high as their session count.

Why does GA4 count users by device instead of by person?

GA4 identifies users through a browser or device signal rather than verified personal identity, so the same person visiting from a phone and a laptop without being logged in may register as two separate users.

What counts as an engaged session in GA4?

A session lasting at least ten seconds, containing a conversion event, or including at least two page or screen views, any one of these three conditions qualifies a session as engaged.

Join 14,000+ marketing growth leaders

Receive our bi-weekly breakdown of campaign analytics setups, attribution rules, naming tactics, and link-stitching blueprints. Direct to your inbox.

Continue reading blueprints

All Articles
Understanding Sessions, Users, and Events in Plain English | UTMLoop Blog