Page value
Page value estimates the average monetary value of a page by crediting it with revenue from transactions (and goal values) that occurred in sessions where the page was viewed before the conversion. It is a way to surface which content contributes to revenue, not just which page closes the sale. Page value is an attribution-style estimate, so it shares the assumptions and limits of crediting upstream pages.
What this means
Page value, as defined by Google Analytics, is the average value of a page a user visited before landing on a goal or completing an ecommerce transaction. It divides the total transaction revenue (plus any goal values) credited to a page by the number of unique pageviews for that page, surfacing pages that appear on the path to revenue.
An attribution-style estimate
Page value is fundamentally an attribution calculation: it spreads conversion value back across pages that were viewed earlier in the converting session. That means it inherits attribution's assumptions — it credits presence in the session, not proven causal influence, and a page viewed in many converting sessions can accrue high value without being persuasive. It is best read comparatively (which content sits on valuable paths) rather than as an exact monetary price for a page.
- Revenue + goal value credited to pages seen before converting
- Divided by the page's unique pageviews
- An attribution estimate, not a causal per-page price
How it appears in analytics and logs
A page value figure shows the average revenue associated with sessions that included a page before converting. A high page value on a non-checkout page signals content that supports purchases, not that the page itself transacts.
Diagnostic use case
Use page value to find content that contributes to revenue ahead of the conversion, treating it as an attribution estimate rather than a precise per-page price.
What WebmasterID can help detect
WebmasterID records ordered first-party page_view and value events, so revenue can be associated with the pages that preceded a conversion without third-party cookies.
Common mistakes
- Reading page value as proof a page caused the purchase.
- Comparing page value across different goal/revenue setups.
- Ignoring that high-traffic pages accrue value by presence.
Privacy and accuracy notes
Page value is derived from aggregate transaction/goal values mapped to pageviews, not from personal identity. No personal identifiers are required.
Related pages
- Event value
Event value is a numeric value attached to an event via a value parameter, letting analytics sum the worth of actions that are not direct purchases — a lead, a sign-up, a key interaction. It turns counted events into an aggregable monetary or proxy figure. The catch is that event values are assigned by the implementer, so inconsistent or arbitrary values quietly distort every total and comparison built on them.
- Return on ad spend (ROAS)
Return on ad spend (ROAS) is the revenue attributed to advertising divided by the cost of that advertising, usually expressed as a ratio or percentage. It answers 'how much revenue did each unit of ad spend bring back'. ROAS is not ROI — it ignores product margins and other costs — and its numerator depends entirely on the attribution model, so the same campaign can show very different ROAS under different rules.
- Data-driven attribution: promise and caveats
Data-driven attribution (DDA) assigns credit using a model trained on a site's own conversion paths rather than a fixed rule like last-click. Done well it credits assist touches more fairly. Its caveats are real: it needs enough conversion volume, it is a model not a measurement, and it cannot see touches that were never tracked.
- Attribution analytics
Associate revenue with the pages on the path.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.