Pageviews vs Events: Which Should You Track?

Pageview analytics asks: *What content did people see, and how did they arrive?*

Event analytics asks: *What did people do that matters to the business or product?*

Both can live in one tool (GA4, PostHog). Many privacy-first tools intentionally stay closer to pageviews and simple goals so the product stays light and compliant.

Stay pageview-first when:

• You run a blog, docs site, or marketing site
• Success metrics are traffic, referrers, and a few conversion goals (signup click, contact form)
• You want privacy-first, lightweight analytics without a big event taxonomy

Plausible and Fathom are built for this lane. You can still fire custom events for key buttons — just do not expect full product analytics depth.

Invest in events when:

• Users have accounts and multi-step journeys inside an app
• You care about activation, retention, feature adoption, or experiments
• Revenue happens through instrumented purchases you need to attribute precisely

That is the PostHog / mature GA4 lane. Expect engineering time for naming, identity, and QA — not just a script paste.

How you are charged changes the incentives:

• Pageview tiers (Plausible, Fathom hosted) — more pages ≈ more cost; custom events are usually secondary
• Event volume (PostHog Cloud, GA4 collection limits) — autocapture and chatty SDKs can burn quota
• Session caps (Hotjar) — recordings are not the same unit as pageviews

Use our pricing calculator with the unit your shortlist actually bills on.

If your weekly meeting stares at referrers and top pages, start with a privacy-first web analytics tool.

If your weekly meeting stares at funnels and retention charts, start with product analytics (and optionally keep a lightweight tool on the marketing site).

New to the vocabulary? Read Analytics Events: What They Are and Why They Matter next, then pick a comparison that matches your shortlist.