What is a pageview?
A pageview is one load or view of a page. What counts as one, how single-page apps change it, and how pageviews relate to sessions and unique visitors.
What is a pageview?
A pageview is a single recorded view of a page on your site. Every load counts, including reloads and repeat visits to the same page in one session. It is the base unit of web analytics: sessions group pageviews into visits, and unique visitors group sessions into people.
The formula.
Pageviews per session = total pageviews / total sessions
- pageview
- One recorded view. In a single-page app, one route change if client-side navigation is tracked.
- unique pageview
- Views of a page collapsed to one per session, which answers how many visits included the page.
Pageviews per session is the quickest health check on tracking. A value pinned at exactly 1.0 on a multi-page site nearly always means the tracker is misinstalled.
A worked example.
One visitor, one visit, a documentation site.
| Loads /docs/install | 1 pageview |
|---|---|
| Reloads it after editing a config file | 1 more pageview |
| Opens /docs/events, then goes back to /docs/install | 2 more pageviews |
| Total | 4 pageviews |
4 pageviews, 2 unique pageviews, 1 session, 1 unique visitor
The same visit produces four different numbers depending on what you asked. Reports go wrong when someone compares one site's pageviews to another site's sessions.
What counts as a pageview
Classically, a pageview is recorded when the tracking script runs during a document load. Reloads count. Returning to a page you already viewed counts again. Opening the same page in two tabs counts twice.
Modern applications broke that definition. In a React, Vue or Next.js app, moving between screens changes the URL through the History API without loading a document, so a tracker that only fires on load records one pageview for an entire session. Every screen after the first is invisible.
The fix is to track history changes as pageviews, which is what Mrkr's tracker does by default. Without it, pageviews collapse, bounce rate goes to almost 100%, and time on page stops working, all from one missing behaviour.
Pageviews, sessions, and visitors
Three counts of the same traffic, at three levels of grouping. They are related but never interchangeable.
| Metric | Counts | Typical relationship |
|---|---|---|
| Pageview | Every view of every page | The largest number |
| Unique pageview | Views collapsed to one per page per session | 60% to 80% of pageviews |
| Session | One visit, ending after inactivity | Pageviews divided by 2 to 4 |
| Unique visitor | One person in the period | Sessions divided by 1.2 to 2 |
Typical relationships are rough patterns, not rules. A documentation site runs many pageviews per session; a single-page landing site runs close to one.
See it on real data
The live demo is a fully populated dashboard with real demo traffic. No signup and no card required.
Open the live demo
Where pageview counts go wrong
Untracked client-side routing
The most common tracking bug there is. Symptom: pageviews per session sitting at 1.0 on an app people demonstrably click through.
The script installed twice
A tag manager plus a hardcoded snippet doubles every number on the site. Check for duplicate requests before you believe a sudden traffic jump.
Bots counted as people
Crawlers generate pageviews at scale. Measured over 30 days on a live site running Mrkr, AI and search crawler hits were 8.7 times the human pageviews.
Adblockers removing them
A meaningful share of visitors block third-party analytics requests outright, so pageviews are undercounted unless you serve the tracker from your own domain.
Pageviews in Mrkr
Mrkr records a pageview on document load and on client-side history navigations, so single-page apps report the same way multi-page sites do. Each pageview carries the path, the referrer, campaign parameters, and coarse device and country information, with no cookie set in the default mode.
Bot and crawler traffic is classified at ingest and excluded from the reported figures rather than filtered afterwards in the dashboard, so the number you see is already the human one.
Pageviews are also the metered unit for billing, and the only one: goals, custom events and session replay are stored without being counted. What a pageview allowance costs per month is on the pricing page.
Questions, answered.
Related terms.
- What is session?
A session is one continuous visit to a site: a group of pageviews and events from the same visitor with no long gap between them.
- What is unique visitor?
A unique visitor is one person counted once within a reporting period, no matter how many times they visit or how many pages they view.
- What is time on page?
Time on page is how long a visitor spent on one page before moving to the next.
- What is bounce rate?
Bounce rate is the share of sessions that end without a second interaction: one page loads, nothing else is recorded, and the visitor leaves.
- What is web analytics?
Web analytics is the collection, measurement and analysis of what happens on a website: who visits, where they came from, which pages they see, and what they do before they leave.
Where this shows up in Mrkr
- Stop losing pageviews to adblockers with a first-party proxy
Serve the tracker from your own subdomain so there is no third-party request to block.
- See how pageviews are metered on each Mrkr plan
- Browse the full analytics glossary
Every metric, method and privacy term, defined in one place.
Your first visitor is already here.
Drop in the script and watch them land. It takes about a minute.