Is a pageview the same as a page view?

Yes. “Pageview” and “page view” are commonly used for the same website analytics concept. The spelling varies by tool, documentation, and editorial style.

How is a pageview different from a visit or session?

A pageview is one view of one page. A visit or session is a broader period of activity that can contain one or many pageviews. For example, one session in which someone views a landing page, a product page, and a checkout page contains at least three pageviews.

Does refreshing a page create another pageview?

Often, yes: a reload or revisit can be recorded as another pageview. The exact result depends on how the analytics tag and application are implemented, so teams should verify their tool’s collection rules when metrics do not match expectations.

What is the difference between a pageview and a unique pageview?

A pageview counts recorded views, including repeats. “Unique pageview” is not a universal metric definition: some tools deduplicate views within a session or time window, while others use different rules. Always check the reporting definition before comparing unique pageview numbers across tools.

How is a pageview different from a screenview?

A pageview generally describes a web page, while a screenview generally describes a screen in a mobile app. Both measure views of a digital experience, but the tracking event and implementation differ between web and app environments.

What is an artificial or virtual pageview?

It is a pageview sent to represent a distinct view that does not require a new URL or full page load. Examples can include a modal, pop-in, overlay, or virtual route. Contentsquare documentation describes artificial pageviews for steps that visitors see as distinct views even when the URL does not change.

How do pageviews work in a single-page application?

Because a single-page application can change content without reloading the browser document, its tracking setup may need to send a pageview when the route or meaningful view changes. Without that implementation, analytics may undercount the views users actually experience.

Are more pageviews always better?

No. More pageviews can indicate strong exploration, but they can also result from repeated reloads, looping navigation, or difficulty finding information. Use pageviews with progression, conversion, engagement, and qualitative or replay evidence to judge whether the experience is improving.

What is a pageview?

Definition

A pageview is counted when a web page is viewed or loaded. The total pageviews metric adds up those recorded views over a chosen time period, so a single person can contribute multiple pageviews by visiting several pages, revisiting a page, or refreshing it.

Pageviews are useful for measuring reach and content consumption at page level, but they are not the same as unique visitors, visits, or sessions. A high pageview count can reflect healthy exploration, repeated research, or friction that makes people revisit the same step, so it needs context from other behavioral and outcome metrics.

In modern websites, a page can also change without a full browser reload. Analytics implementations may send an additional or artificial pageview when a user sees a distinct view such as a modal, pop-in, overlay, or virtual route. The exact counting rules depend on the analytics implementation and tool configuration.

What does that mean

Think of a pageview like adding one tick mark every time a page is looked at. If the same person looks at three pages, that creates three pageviews; if they look at one page twice, that can create two pageviews.

Why this matters

Pageviews give teams a simple baseline for understanding which pages attract attention and how much content people consume. Marketing and Ecommerce teams can use them to assess traffic and product discovery, while Product and UX/UI teams can compare page-level patterns with journeys, friction, and conversion outcomes.

Use cases

Measure whether campaigns lead to deeper browsing

Relevant for Marketing and Ecommerce.

A campaign may bring people to a site without showing whether they explore products or useful content after landing. Comparing pageviews by landing page, campaign, traffic source, device, or audience segment helps teams see whether visitors move beyond the first page and which content attracts further attention.

The benefit is a clearer view of content and acquisition quality: teams can refine campaign destinations, internal links, and merchandising paths based on the journeys that lead to meaningful exploration rather than traffic volume alone.

See it in practice

After using behavioral analytics to investigate product discovery, Sur La Table found that driving people to category pages led to a 12% increase in total product page views and a 6% increase in overall conversion rate.

Find friction behind high-traffic pages

Relevant for Product and UX/UI.

A page can receive many pageviews while users still abandon the journey, loop back, or fail to complete an important task. Teams can use pageviews as a starting signal, then examine where those views sit in the journey and review representative sessions to understand whether the issue is unclear content, a broken element, slow progress, or another source of friction.

This turns a volume metric into a diagnostic workflow. Instead of asking only which pages are popular, teams can identify which high-traffic pages create obstacles and prioritize changes that help users progress.

Validate page and navigation changes

Relevant for Product and Data.

When a page layout, navigation structure, or content experience changes, teams need to know whether behavior changed as expected. Comparing pageviews before and after a release, or between audience segments and test variations, can show whether users are reaching important pages more often or whether traffic is being redirected unexpectedly.

The expected benefit is faster learning from product and content updates. Pageviews should be read alongside progression, conversion, engagement, and qualitative or replay evidence so that an increase is not mistaken for improvement when it actually reflects confusion or repeated attempts.

How Contentsquare helps

Web Analytics provides an overview of page views and related engagement metrics so teams can baseline content performance and compare channels, journeys, and segments.
Journeys shows how visitors progress through a site from entry to exit, helping teams put pageview volume in the context of paths, drop-offs, loops, and conversion journeys.
Session Replay lets teams watch the user experiences behind a pageview pattern, including hesitation, errors, clicks, scrolls, and other behaviors that pageview totals cannot explain.

FAQs on pageview

Yes. “Pageview” and “page view” are commonly used for the same website analytics concept. The spelling varies by tool, documentation, and editorial style.

Contentsquare x Škoda