> For the complete documentation index, see [llms.txt](https://docs.elevateab.com/elevate-helpcenter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateab.com/elevate-helpcenter/price-testing/reading-price-experiment-results.md).

# Reading Price Experiment Results

Which metrics matter when reading a price experiment in Elevate A/B Testing, how orders are attributed, and the misreads that cost merchants money.

***

Judge an Elevate A/B Testing price experiment on Revenue per visitor, or on Profit per visitor if you have added COGS, not on conversion rate. A lower price almost always converts better, so reading a price test on conversion rate leads you to roll out a price on your Shopify store that sells more units and earns less money.

### Which metric decides the winner

The goal metric you chose at setup decides the winner. Every other metric is still calculated, so you can see the full picture.

| Goal metric                           | Use it when                                                                                                           |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Revenue per visitor**               | Almost always. Accounts for both how many people buy and how much they spend.                                         |
| **Profit per visitor**                | You have added COGS and want cost of goods, shipping, and fees subtracted. The most honest measure of a price change. |
| **Average order value**               | You are testing something meant to change basket size rather than conversion                                          |
| **Subscription percentage of orders** | You are testing subscription pricing and want to see the effect on subscription mix                                   |

### Should you judge a price experiment on conversion rate?

**A lower price almost always converts better.** That is not a finding, it is arithmetic.

If you read a price test on conversion rate, the cheapest variation wins nearly every time, and you roll out a price that sells more units and earns less money.

A worked example. Two variations, 1,000 visitors each:

|                     | Control at 50.00 | Variation at 40.00 |
| ------------------- | ---------------- | ------------------ |
| Conversion rate     | 3.0%             | 3.4%               |
| Orders              | 30               | 34                 |
| Revenue             | 1,500            | 1,360              |
| Revenue per visitor | 1.50             | 1.36               |

The variation converts better and earns less. Conversion rate says the variation won. Revenue per visitor says the control did, and revenue per visitor is right.

This is why Elevate A/B Testing recommends Revenue per visitor for price experiments, and why Profit per visitor is better still when you have cost data.

### What conversion rate means here

Conversion rate in your results is the share of unique visitors who purchased.

It is worth watching as a secondary number, because it tells you how buyers reacted to the price. It should not decide the winner of a price test.

### Profit per visitor requires COGS

If [COGS](https://docs.elevateab.com/elevate-helpcenter/experiment-setup/cogs.md) is not set up, profit columns and charts are hidden and replaced with an option to set it up. Add your COGS, and profit becomes available.

One caution: products without cost data contribute zero cost to the calculation, which inflates profit. If you enable profit reporting, make sure costs are complete for the products in your experiment.

### How orders are attributed

A visitor is counted in an experiment once they have seen it. When they purchase, the order is credited to the variation they saw.

Assignment is sticky, so a visitor who sees a variation, leaves, and returns days later to buy is still credited to that variation.

This is why Elevate A/B Testing's numbers can differ from Shopify's or from Google Analytics. Elevate A/B Testing counts unique visitors and attributes revenue to the variation each one saw. Other tools count sessions, or attribute to the last channel. See [Analytics Discrepancies](https://docs.elevateab.com/elevate-helpcenter/analyze/tracking/analytics-discrepancies.md).

### When to trust the result

Elevate A/B Testing uses a Bayesian model and tells you when a result is trustworthy. Until it does, the numbers are provisional no matter how large the gap looks.

Three things that make a result look real when it is not:

**Too little data.** Early results swing hard. A twenty percent lift on forty orders is noise.

**Too short a run.** Weekday and weekend buyers differ. Run at least a full week.

**A change mid experiment.** If prices, targeting, or catalog prices moved while the test ran, the data describes two different experiments. Start again.

See [Statistical Significance](https://docs.elevateab.com/elevate-helpcenter/analyze/reports/statistical-significance.md).

### Reading a result that is not a clear win

Not every price test produces a winner, and a flat result is still useful.

**No difference at all** usually means the price change was too small to matter to buyers, which is itself a finding: you have room to move without losing volume. Test a larger change.

**Higher revenue, lower profit** means the winning price sold products with worse margins. This is why Profit per visitor exists.

**Higher conversion, lower revenue** is the classic price cut result. You bought volume with margin.

**Wildly different results by segment** is worth investigating before acting. A price that works for returning customers and fails for new ones may be a personalization rather than a price change.

### Before you act on a result

* \[ ] Elevate A/B Testing has identified a winner
* \[ ] The experiment ran at least a full business cycle
* \[ ] Nothing was changed mid run
* \[ ] You are reading Revenue per visitor or Profit per visitor, not conversion rate
* \[ ] Test orders you placed during QA are accounted for
* \[ ] The result matches or usefully contradicts the hypothesis you recorded

When you are ready, see [Ending a Price Experiment](https://docs.elevateab.com/elevate-helpcenter/price-testing/ending-a-price-experiment.md).
