Value per visitor for non-purchases
Value per visitor generalises revenue per visitor to sites without direct sales: you assign an estimated value to each goal (a lead, a signup, a download) and divide total assigned value by visitors. It makes mixed conversion goals comparable, but the result is only as honest as the values you assign. This page explains the method and the disclosure it demands.
Why assign goal values
Many sites convert on actions with no immediate price — a newsletter signup, a contact form, a trial start. Value per visitor lets you weight these by an estimated worth so a page driving signups and one driving downloads can be compared on a single scale instead of incommensurable counts.
The values must be documented
The honesty of value per visitor lives entirely in the value table. If a lead is worth a figure derived from your real close rate and deal size, the metric is meaningful; if it is a number someone guessed, the metric inherits that guess. Document how each value was derived and treat changes to the table as a versioned decision.
- Each goal type gets an estimated value
- Total assigned value / visitors = value per visitor
- Values must be documented, not invented
Reading shifts carefully
Because the metric blends behaviour and assigned values, a move can mean either changed. When comparing across time, hold the value table fixed; if you re-estimate goal values, recompute history on the new table or annotate the break so trends stay interpretable.
How it appears in analytics and logs
Value per visitor reflects your assigned goal values as much as real behaviour. A shift can come from behaviour or from someone changing the goal values.
Diagnostic use case
Assign a documented, defensible value to each non-purchase goal so you can compare pages and variants on one scale instead of juggling many goal counts.
What WebmasterID can help detect
WebmasterID's first-party goal completions let you attach estimated values to events and roll them into a per-visitor figure from data you own.
Common mistakes
- Assigning goal values by guess and treating them as facts.
- Changing the value table mid-trend without re-baselining.
- Comparing value per visitor across periods with different values.
Privacy and accuracy notes
Value per visitor aggregates goal completions and assigned values. It needs no personal identifiers — only counts and a documented value table.
Related pages
- Revenue per visitor (RPV)
Revenue per visitor (RPV) is total revenue divided by the number of visitors over a period. Because it combines conversion rate and average order value, it captures trade-offs a single metric hides — a change that lifts conversions but cuts order value may leave RPV flat. It is a common overall evaluation criterion in commerce experiments. This page defines RPV and its caveats.
- Goal completion and key events
A goal completion is recorded when a visitor performs an action you have defined as valuable, such as a purchase or signup. In modern tools you mark an event as a key event (a conversion) and each qualifying occurrence is counted. The traps are over-counting repeated actions, double-counting across sessions, and defining the goal so loosely it stops meaning success.
- Micro and macro conversions
A macro conversion is a primary business goal — a purchase, a signup. A micro conversion is a smaller, intermediate action that signals progress toward it, like viewing a product or starting a form. Tracking both gives a richer picture of the funnel, but only the macro conversion should be treated as the headline success metric.
- CTA tracking
Capture goal completions you can assign value to.
Sources and verification notes
- Google Analytics Help — About conversionsGoal/conversion value concept; no benchmark figures.
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.