Skip to content
Glossary

What is a pageview?

A pageview is counted each time someone opens a page on your website. Example: a visitor reads your homepage and then your price list – that is two pageviews.

PureMetrixLast reviewed 4 min read5 sources checked

Definition

In PureMetrix, a pageview is recorded when a browser loads a page that contains the PureMetrix script. One visit can contain several pageviews. Visits with only one pageview count towards the bounce rate.

Pageviews are not people. One person can open many pages in a day. To count people, see unique visitors.

What usually creates a pageview

A full page load creates a pageview when the PureMetrix script runs—HTML snippet, WordPress, Shopify storefront, or a layout wrap in Next.js. Single-page apps that swap content without a reload must send a pageview on each route change (Next.js, npm). Classic multi-page sites usually work once the snippet is on every public page.

Cached pages must still include the script for visitors who are not logged in. Edge caches, Shopify theme caches, and WordPress speed plugins that strip scripts are a common reason pageviews drop after a performance change.

PureMetrix specifics

The script is under 3 KB. An optional same-origin /px proxy loads it from your own domain, so fewer visits are lost to ad blockers.

Exclude your own team: WordPress roles, Shopify staff accounts, or a staging hostname—so preview clicks do not inflate the charts.

How to read pageviews

Pageviews show which pages get attention. On a shop or business site, read them together with landing pages and goals. A sudden spike in pageviews without more goals reached is a content success, not automatically more sales.

PureMetrix takes campaign tags (UTM parameters) out of the page address and keeps them as separate campaign filters, so /pricing/ stays one row in your reports.

Messy URLs and duplicate page rows

Without this clean-up, UTM tags and session IDs would split one page into many rows. Keep campaign parameters as filters so /pricing/ stays one page. Otherwise every newsletter send creates a new “page” and your top-pages report becomes unusable.

More guides HTML snippet WordPress Shopify Next.js

Last updated: September 2026

What this means in practice

Update your privacy policy with which tool runs, where data is processed, and that a data processing agreement (DPA) is in place. Also review every other script on the site — chat, ads, heatmaps — that may still set cookies.

After switching, run both tools in parallel for two to four weeks and compare trends and goals. Absolute counts between cookieless tools and GA4 behind a banner differ by design; direction and conversions matter more.

Short checklist

  1. Connect the tool or plugin and fire a test pageview.
  2. Optionally serve events through the same-origin /px proxy.
  3. Exclude staff roles (for example admins) from counting.
  4. Create key goals: thank-you pages, forms, purchases.
  5. Sign the DPA and update your privacy policy.

Honest limits

Cookieless analytics will not recognise the same person across months and devices. Remarketing audiences and cross-device journeys are out of scope. In return you see the visitors who would otherwise refuse a banner, with a lean, EU-friendly setup.

Why this topic matters

Website owners in the EU increasingly choose analytics that work without a consent step for the statistics themselves. That only helps if the rest of the stack is honest: where data is processed, who the processor is, and which other scripts still need a banner.

PureMetrix is built for that setup: cookieless counting, EU-only processing on Hetzner, an official WordPress plugin, and plans from €6 a month. Use this page together with your privacy policy and a signed data processing agreement.

How PureMetrix helps

Install the WordPress plugin or a small snippet, connect your site, and you see visitors, sources, top pages and goals without storing a PureMetrix cookie on the device. From the Growth plan, WooCommerce purchases can be recorded on the server so payment redirects do not lose the sale.

Recommended next steps

  1. Read your current privacy policy and list every analytics or marketing script.
  2. Start a PureMetrix trial on a staging or low-traffic site first if you prefer.
  3. Recreate your main goals, then run both tools in parallel for two weeks.
  4. Update the privacy policy, sign the DPA, and remove what you no longer need.

Frequently asked questions

What is this page about?

This page explains “What is a pageview?” in practical terms for EU website owners and how PureMetrix fits.

Do I need a cookie banner for PureMetrix?

Usually not for PureMetrix alone, because it does not set visitor cookies. Other tools on your site can still require consent.

Can I try PureMetrix first?

Yes. 14 days free, no credit card. Then pick a plan or stop.

Try cookieless analytics on your own site

14 days free, no credit card. EU-hosted on Hetzner, set up in a few minutes with the WordPress plugin or a snippet.

Start the 14-day trial See pricing