Pageviews count every page load, sessions group those loads into visits that end after 30 minutes of inactivity, and users count distinct browsers. One person reading three articles in one sitting is 3 pageviews, 1 session, 1 user — which is why the three totals in an analytics report never match.
| Metric | What it counts | One reader, 3 articles, one sitting | Distorted by |
|---|---|---|---|
| Pageviews | Every page load or reload | 3 | Refreshes, bots, auto-reloading pages |
| Sessions | Visits closed by 30 minutes of inactivity | 1 | Shorter timeouts, reporting timezone |
| Users | Distinct browsers or devices, not people | 1 | Cleared cookies, incognito, phone plus laptop |
| Unique IPs | Distinct IP addresses seen | 1 | Shared office networks, mobile carrier NAT |
What a Pageview Counts
A pageview is one request to load a page, recorded on every load and every reload. Five refreshes of the same article write five pageviews, because the metric records the request rather than the reader. Pageviews carry no deduplication, no time window and no identity.
That rawness makes pageviews right for content questions and wrong for audience size, because one bot crawling a 500-page site produces 500 pageviews and zero readers. Single-page apps invert the problem: a route change that never reloads the document goes uncounted unless the app fires a pageview itself. Tracking page views in WordPress covers the mechanics.
What a Session Counts
A session, also called a visit, groups one browser’s pageviews until 30 minutes pass without activity. The 30-minute window is a convention rather than a law: Google Analytics uses 1,800 seconds by default, and SlimStat ships the same 1,800 seconds as an editable Visit Duration. SlimStat counts that window from the first pageview unless you switch on Extend Duration, which restarts the clock on every new page.
Shortening that window inflates session counts, because a pause that once sat inside one visit now splits into two. Compare session totals across tools only after checking both timeout values, since a tool set to 10 minutes reports more sessions than one set to 30 on identical traffic. Each tool also files a session under a date using its own reporting timezone, so a visit at 23:50 can land on different days in two reports of identical traffic.
What a User Counts
A user is a browser holding an identifier, usually a cookie — not a person. One human with a phone, a work laptop and a home desktop registers as three users, while three colleagues sharing one kiosk browser register as one user. Users is the least literal of the three metrics.
Cookie deletion, incognito windows and privacy browsers all reset that identifier, so user counts drift upward over long date ranges even when the audience is flat. Cookieless tools substitute a daily one-way hash of IP address and user agent, which counts a returning reader as new the next day.
Why the Three Numbers Never Reconcile
The three metrics are nested: every pageview belongs to a session, and every session belongs to a user, so pageviews ≥ sessions ≥ users on any healthy site. When that ordering breaks, or when the ratios move sharply, the cause is usually a counting artefact rather than a real change in audience.
- Sessions barely above users — almost nobody returns inside the date range selected.
- Pageviews barely above sessions — most visits are a single page, which is what bounce rate measures.
- Pageviews far above users, sessions flat — refreshes, auto-reloading pages, or bots no filter catches.
- Users rising while sessions stay flat — identifier churn, not growth.
Two tools disagree on all three counts because each applies its own timeout, bot list and identifier rule: see the Google Analytics alternatives for WordPress shortlist.
How SlimStat Reports These Three Metrics
SlimStat writes one row per pageview into its own table in your WordPress database and derives the other two figures from those rows. At a Glance reports Pageviews and Unique IPs as totals; Audience Overview adds Visits, Bounce rate and Pageviews per visit for human traffic only, with bots counted separately. The database tables reference documents every column.
Frequently Asked Questions
Four questions cover most of the confusion between these three metrics, and each has a one-line answer. The pattern underneath all four is the same: pageviews count requests, sessions count visits bounded by inactivity, and users count identifiers held by browsers, not people.
What is the difference between sessions and pageviews?
A session groups one browser’s interactions within a set window, usually 30 minutes of inactivity; a pageview is recorded on every page load. One session contains at least one pageview.
What is the difference between sessions and users?
A user is one browser holding an identifier; a session is that browser’s activity during a single visit. One user generates many sessions, so sessions equal or exceed users in any date range.
What is the difference between a pageview and user engagement?
A pageview counts page loads. Engagement describes what happens inside those loads — scroll depth, clicks, time on page, form submissions — so two sites with identical pageviews can differ on every engagement measure.
What is the difference between active users and views?
Active users are the distinct identifiers seen in a period; views count page loads in the same period. Views run far higher wherever people read more than one page per visit.