Your conversion rate went up. Your profit went down.
A rising conversion rate can sit on top of a falling profit. Discounts, free shipping and aggressive bundling all lift the share of visitors who buy while cutting what each order is worth. If reporting stops at conversion rate, that trade is invisible. Revenue per visitor and contribution margin make it visible immediately.
The number that moves the wrong way quietly
Conversion rate is a ratio. It has a numerator you want to grow and a denominator you can shrink by accident. Cut the price by fifteen percent and more people buy. The percentage climbs. The finance team asks why gross margin fell in a month the marketing dashboard called a win.
This is not a rare edge case. It is the default outcome of optimising a single ratio in isolation, and it is why an experimentation programme that reports only conversion rate will eventually make a business poorer while looking like it is working.
The test data already shows the gap
Look at what winning tests actually produce. In DRIP’s database of experiments across ninety-plus European ecommerce brands, winning tests delivered a median conversion rate uplift of 1.88% and a median revenue per visitor uplift of 2.77%. Those two numbers are not the same, and the difference between them is the entire argument. Some winners lift conversion and revenue together. Others lift the ratio and take the order value with them on the way down.
You only see which kind you have if you measure both.
Worth knowing how rare a real winner is before designing a programme around them. Optimizely’s analysis of more than 127,000 experiments puts the average win rate near 12%. ConversionTeam’s audit of 2,288 tests found 19.1% reached statistical significance. Most tests do not move anything. Which makes it expensive to spend one of your few genuine winners on a result that shrinks the average order.
Three ways a conversion win costs money
| What you changed | What the ratio does | What profit does |
|---|---|---|
| Sitewide discount code in the header | Rises | Falls, every order carries the discount |
| Free shipping with no threshold | Rises | Falls if shipping cost exceeds the margin gained |
| Removing an upsell to shorten checkout | Rises | Falls, average order value drops with it |
Each of these will pass a test that measures conversion rate alone. Each of them will fail a test that measures revenue per visitor, and fail harder against contribution margin.
What to measure instead
Three numbers, in this order.
Revenue per visitor. Conversion rate multiplied by average order value. It catches the discount trap immediately, because a price cut moves both inputs in opposite directions and RPV shows you the net.
Contribution margin per visitor. RPV minus the cost of goods, shipping and payment fees. This is the number a shipping test has to answer to, since free shipping shows up nowhere in RPV and everywhere in margin.
Sixty to ninety day repeat behaviour. A test that lifts first orders and suppresses second orders is a loss with a delay on it. Subscription take rate is usually the fastest read on this.
What this looks like in practice
Across the work we run at Parah Group, the clearest example came from a DTC supplements brand where the winning change was a shipping threshold test. It did not produce a dramatic conversion rate headline. It produced two million dollars in profit, because the threshold moved order composition rather than order count.
A cannabis DTC brand we worked with is the same lesson from the other direction. Over three months, while paid spend was scaling, subscription take rate rose 75%, average order value rose 25% and conversion rose 20%. Three numbers moving together, which is what a healthy programme looks like. Had we optimised for the conversion number alone, the tests that produced the first two would never have been prioritised.
Where to start this week
Open your test log and add two columns: revenue per visitor and average order value. Backfill them for the last ten tests you called winners. If any of those tests raised conversion rate and lowered RPV, you have already found the problem and it costs nothing to fix, because the change is in what you report, not in what you build.
Then set the rule going forward. No test ships as a winner on conversion rate alone. Revenue per visitor is the primary metric and average order value is reported beside it every time. Any test that touches price, shipping cost or bundle structure reports contribution margin as well, before the result is called rather than after.
