Pricing page optimisation
A pricing page sits at the decision point, so changes there move both conversion rate and order value. Optimising it means testing clarity, plan layout, and the unit you charge on — while judging results by revenue per visitor, since a layout that lifts signups onto cheaper plans can lower revenue. This page frames pricing tests honestly, with no invented benchmarks.
Why pricing tests are high-stakes
The pricing page is where intent becomes revenue, so a change can move conversion rate and order value at once. That makes the choice of success metric critical: revenue per visitor, not signup rate, because it captures the trade-off between converting more people and converting them onto cheaper plans.
What is actually testable
Real, defensible levers include clarity of what each plan includes, the order and framing of plans, the default or highlighted option, and the value metric you bill on (per seat, per usage). These are concrete, measurable changes — unlike vague 'make it convert better' goals — and each can be run as a controlled experiment.
- Plan clarity and feature framing
- Plan order and the default selection
- The value metric you charge on
Honesty constraints
Avoid borrowed 'best pricing layout' claims; there is no universal winner, and what works depends on your product and audience. Pricing tests can also have slow feedback (upgrades, churn) that a short conversion test misses — pair the immediate metric with longer-horizon retention before declaring victory.
How it appears in analytics and logs
A pricing change that raises signups but flattens RPV moved buyers down-plan. Reading conversion rate alone would have called a revenue-neutral change a success.
Diagnostic use case
Test pricing-page changes (clarity, plan order, default selection) and read them on revenue per visitor so a signup lift that shifts buyers to cheaper plans is not mistaken for a win.
What WebmasterID can help detect
WebmasterID's first-party value events let you measure plan selection and revenue per visitor on the pricing page, so pricing tests are judged on value rather than raw signups.
Common mistakes
- Judging a pricing test on signups instead of revenue per visitor.
- Copying a 'best' pricing layout that suited a different product.
- Ignoring downstream upgrade and churn effects of a pricing change.
Privacy and accuracy notes
Pricing tests use aggregate plan-selection and revenue counts. They need no personal identifiers — only outcomes per variant.
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.
- Average order value (AOV)
Average order value (AOV) is total revenue divided by the number of orders. It is simple but easy to misread: a few large orders pull the mean upward, refunds and taxes change what 'revenue' means, and mixing currencies without conversion corrupts it. For skewed order sizes, the median order value is often more honest.
- Checkout flow optimisation
Checkout optimisation targets the final, highest-intent stretch of the funnel, where small friction loses ready buyers. The method is to instrument each step, find where drop-off concentrates, and test specific reductions — fewer fields, guest checkout, clearer errors. Success is read at the step that changed, not only the overall completion rate. This page frames it with step-level diagnosis.
- Customer lifetime value (LTV)
Customer lifetime value (LTV or CLV) estimates the total revenue or margin a customer generates across their whole relationship. It is a forecast built on assumptions about retention, purchase frequency, and margin — not a measured number. Treated as fact it misleads; treated as a model with stated assumptions it guides acquisition spend.
Sources and verification notes
- Wikipedia — PricingPricing structure concepts; 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.