Sessions vs Page Views vs Users — The Basics You Were Afraid to Ask

"Sessions are the number of visitors, right?" "Page views are high, so traffic is healthy." — when someone is starting out with web analytics, these are the very first three metrics to trip them up. Sessions, page views, and unique users (UU) look similar but mean different things, are counted differently, and are used for different decisions.

This article walks through what each of the three metrics actually counts, how they relate to each other, which one to look at first, and how GA4 treats them under its event-based measurement model.

TL;DR#

1. The three metrics count different things

   Sessions = number of visits, Page views = number of pages viewed, Users (UU) = number of people who visited. The same person visiting 3 times and viewing 5 pages produces Sessions=3 / PV=5 / Users=1[1]

2. The base inequality is PV ≧ Sessions ≧ Users

   A person typically visits multiple times and views multiple pages per visit, so PV is always largest and Users is always smallest

3. For EC operators: Users first, then repeat rate, then engagement

   Start with Users (reach), then Sessions/Users (repeat rate), then PV/Sessions (engagement). Reading PV alone is dangerous[3]

1. What are sessions — counting visits#

A session is the time period during which a user interacts with a site, counted from arrival to leaving as a single unit[1].

Counting rules:

• A session ends automatically after 30 minutes of inactivity
• A new day (midnight) starts a new session
• Closing the browser ends the session

If someone visits at 9 AM, views 3 pages, leaves, and comes back at 8 PM the same day, that counts as 2 sessions. Even within the same day, a gap longer than 30 minutes creates a new session.

Common confusion: "Sessions = visitor count" is wrong. The same person visiting 5 times a day produces 5 sessions, not 1. Visitor count is a separate metric (Users).

In GA4, every session start fires a session_start event, incrementing the session count by 1. A session_id identifier groups all actions (page views, clicks, purchases) that happen inside that window[1].

2. What are page views (PV) — counting pages opened#

A page view is one count for every time a page is loaded. Opening the same page twice creates 2 page views.

Counting rules:

• Every page load counts (including reloads)
• Viewing 5 product pages produces PV = 5
• Returning to the same page adds another count

A flow of "Home → Product A → Home → Product B → Cart" produces PV = 5. Home was visited twice, so it counts twice.

Common confusion: "High PV = popular site" is wrong. A small group of users clicking around repeatedly can inflate PV. Always read it alongside PV / Sessions (engagement depth).

In GA4, PV is recorded as the count of page_view events. Reports may show it as "Views" or "Page views", but internally it is just the count of page_view events being aggregated[2].

3. What are users (UU) — counting actual people#

UU (unique users) is the number of distinct people who visited the site in a given period[4].

Counting rules:

• Identified via Cookie or User ID
• The same person visiting 10 times still counts as 1 user
• Visiting from another browser or device produces a separate user (different Cookie)

Suppose monthly UU = 1,000 with 200 repeat visitors averaging 3 visits each. New-user sessions = 800, repeat-user sessions = 200 × 3 = 600, so total monthly sessions = 1,400.

Common confusion: "UU = exact number of real people" is wrong. Cookie deletion and multi-device use inflate the number; users who reject Cookie consent are excluded, which can deflate it.

In GA4, this appears as "Active Users". A user is marked active when an engagement session occurs (a session GA4 considers meaningful) or when a first_visit event (first-time visit record) fires[3].

4. How the three metrics relate, and which to look at first#

The base inequality is:

PV ≧ Sessions ≧ Users

A person typically makes multiple visits, and each visit views multiple pages, so PV is the largest and Users is the smallest. Equality only holds in an extreme case where every user makes one single-page visit.

The derived combinations are what actually matter in practice:

For EC operators, the priority order is:

1. Users — "how many people are coming" (reach)
2. Sessions / Users — "how often do they come back" (retention)
3. PV / Sessions — "are they exploring the site" (structural health)

Reading PV alone is dangerous. A small number of users clicking around can produce inflated PV while new-user inflow is actually zero. Health becomes visible only when reach, repeat rate, and engagement depth are all read together.

When revenue is added to the analysis, Revenue Per Session (RPS) makes the picture three-dimensional (RPS complete guide).

5. How GA4 treats the three metrics under event-based measurement#

GA4 switched its measurement model to event-based[5]. This is a fundamental shift from the previous Universal Analytics (UA) session-based model.

Every action — page view, click, scroll, purchase — is recorded as an event. Sessions, page views, and users are computed as aggregations of those events under the hood.

Sessions = count of session_start event fires. Page views = count of page_view event fires. Users = displayed as "Active Users", aggregated from engagement signals. Each metric is rendered as the aggregation of its corresponding event under the hood.

The words "sessions" and "page views" still exist in GA4 reports, but internally they are derived from event counts. Understanding this model makes debugging unexpected GA4 numbers much faster.

For GA4-specific quirks like the rise of direct/none traffic, see Why GA4 direct/none increases and how to fix it. If you are setting up EC tracking on GA4, The complete GA4 e-commerce funnel analysis guide is the natural next step.

FAQ#

Q1. Is high PV always a sign of a good site?

No, not on its own. PV can be high while Users is low, which usually means a small group is clicking around. Read PV alongside Users.

Q2. How do I grow sessions?

You need both new-user acquisition (channel work) and retention (email, push) at the same time. Retention tends to respond to email cadence and freshness of content.

Q3. How do I check page views in GA4?

In GA4, go to Lifecycle → Engagement → Pages and screens. The display name is "Views" or "Page views", but internally it is the count of page_view events.

Q4. How do I deal with Cookie deletion and multi-device inflation for UU?

You can't fully eliminate it. Consent Mode or Google Signals can improve cross-device accuracy somewhat, but not to zero. Treat UU as an approximate count and focus on the direction (rising or falling) over absolute values. For combined revenue analysis on Shopify, see Shopify × GA4 revenue analysis guide.

References#

• Google Analytics Help “About Analytics sessions”
• Google Analytics Help “About events”
• Google Analytics Help “Understand user metrics”
• Google Analytics Help “User: definition”
• Google Analytics Help “Metrics comparison: GA4 vs Universal Analytics”