# Price First or Benefits First on a Pricing Page

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/price-first-or-benefits-first-on-a-pricing-page

## Hypothesis

If visitors choose mainly on budget, seeing the price first lets them judge fit right away, and the price-first order could earn more revenue per visitor. If the value is not obvious at a glance, visitors who read the benefits first may reach the price better prepared, and the benefit-first order could come out ahead.

## When to run this test

Scroll maps of visitors racing down the page to find the price, questions about where the price is, or visitors who leave right after seeing it suggest that the order of price and benefits is getting in the way of the decision. If the idea is right, one order brings visitors to the price better prepared, with more purchases or better-qualified leads. In markets where price must appear at a set stage, check that rule first, and never use the later position to hide the total payable until visitors are committed.

## Primary metric

**Revenue per visitor (RPV)**: Compare revenue per assigned visitor to see whether price placement changes results.

## Other metrics

- **Average order or plan value**: Read purchase value alongside conversion to explain revenue.
- **Purchase conversion rate (CR)**: Check how the share of visitors who buy changes.
- **Bounce rate**: Make sure showing price early does not materially increase exits.
- **Lead quality**: If collecting leads, apply the same qualification rule and follow-up period; check whether later price disclosure brings less-qualified leads.

## What to check before and during the test

- **Order**: Compare showing the same price block before or after the benefits.
- **Visibility**: Keep typography, price amount and terms unchanged.
- **Lead quality**: Check whether earlier pricing changes the quality of incoming leads.
- **Clarity**: Use direct feedback to assess whether visitors perceive the price as hidden; do not infer trust from exits alone.
- **Audience**: Review predefined buyer segments instead of segmenting on behavior after the test.

## What to watch when reading the result

- A higher bounce rate is not automatically a bad result, since an early price can filter out visitors whose budget does not fit. Pick the order on revenue per visitor, weigh average order or plan value together with conversion, and if you collect leads, compare lead quality over a matching follow-up window.
- What you learn is limited to where this price block sits on this page. Do not report that the price was moved up if shipping, tax or setup costs were left for later, or if the currency or tax wording got smaller. Read predefined buyer segments rather than groups defined by behavior after the test.
- Exit data cannot show whether visitors felt the price was hidden; assess that with direct feedback. Put both orders' visitor and purchase counts into the [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test). If the conversion gap is not significant, this data cannot tell you which order leads, and since the calculator does not test revenue, the revenue-per-visitor gap deserves the same caution.

## Frequently Asked Questions

### Does placing price later mean hiding it?

It must not. Keep the total commitment and required costs clear before payment. Follow applicable disclosure rules rather than testing concealment.

### Is higher bounce after early price disclosure necessarily bad?

Not alone. Early price can filter unsuitable budgets. Use revenue per visitor as the primary outcome and apply the predefined exit and lead-quality guardrails.

### How can perceived price concealment be investigated?

Use direct feedback, not exits alone. Inspect predefined buyer groups rather than assigning price-sensitivity labels from treatment-affected purchasing behavior.