Shipping
4 tests · 3 winners
+2.5% pooled effect, +1.3% to +3.6%
High confidence. Together, the tests point the same way: the pooled range excludes zero.
Checkpoints set before launch, gains corrected for the winner’s curse, ideas ranked from past tests: the same rule applies from one test to the next.
Program summary
Across 1,000 simulated A/A tests, with no real difference:
Maison Lune, a fictional demo store · library computed by the engine
Rarely through one big failure. More often through winners that never show up in the numbers and tests that contradict each other.
Each answer rests on a published method and on the library of your own tests.
In the demo store: lessons from the most-tested themes, and the ideas at the top of the ranking. An idea’s expected effect comes from its theme’s lesson.
4 tests · 3 winners
+2.5% pooled effect, +1.3% to +3.6%
High confidence. Together, the tests point the same way: the pooled range excludes zero.
5 tests · 2 winners
+0.4% pooled effect, -0.3% to +1.2%
Medium confidence. Enough tests, but the pooled effect is still compatible with no effect.
3 tests · 1 loser
-0.9% pooled effect, -2.1% to +0.3%
Medium confidence. Enough tests, but the pooled effect is still compatible with no effect.
How a typical week goes, and what the demo store shows at each step.
Ideas are ranked by expected gain per day of effort. Ideas whose theme lowered the metric are flagged “Avoid.”
Target effect, visitors, checkpoint days, and guardrails are set at launch and visible to the whole team.
Between checkpoints, you can look at the daily range without deciding anything. The extra cost of planned looks is built into the test length.
The report gives the verdict, the gain corrected for the winner’s curse in revenue and margin, and the checks alongside.
The completed test joins its theme’s lesson, winner or not, and the expected effect of related ideas updates.
Yes, the daily range stays visible. But only a planned checkpoint allows a decision: across 1,000 simulated A/A tests (two identical versions), reading the test every day declares a false winner 22% of the time, versus 6% at the planned checkpoints.
Each idea gets an expected effect drawn from past tests on the same theme (or from the whole learnings library when the theme has too few tests), a duration based on its area’s traffic, and a monthly gain. The ranking divides that gain by the estimated effort.
Yes, in two different layers. Within one layer, tests take separate slices of traffic: a visitor sees only one of them, and Probant rejects a slice that overlaps another.
It goes into the learnings library with its range, like a winner, and counts toward its theme’s lessons and the expected effect of related ideas.
No. It’s corrected for the winner’s curse before being converted into euros: the measured effect is pulled toward what your past tests deliver on average, because a winner overestimates its effect on average.
The same engine, for other site areas and other teams. The demo opens on the screen this page describes.