A/B/n Testing
Conversion & UXAlso: Multivariant Testing · Split Testing (Multiple Variants)
Quick definition
A/B/n testing is a conversion-rate optimisation (CRO) method where you test three or more versions of a page or element against each other at the same time, instead of just two. The 'n' stands for however many additional variants you add beyond a standard A/B test.
As a rough guide, each variant needs enough conversions per week, not just visitors, to reach significance in a reasonable timeframe. If this number looks thin, run fewer variants or extend the test window.
How it varies across Australia
A/B/n tests need meaningfully more traffic than a standard two-way test because the same visitor pool gets split further. Australian sites outside high-traffic ecommerce and media categories often lack the volume to run clean A/B/n tests and end up with results that never reach statistical significance.
See conversion benchmarks across Australian industries →What it actually means
Standard A/B testing is a coin flip. A/B/n testing is a coin with three, four or five sides. Instead of comparing a control against one challenger, you compare it against several challengers at once. A headline test might run the original alongside three rewritten versions, all live simultaneously.
The appeal is obvious. Why test one idea at a time when you can test four and find the best one in a single round? The catch is traffic. Every extra variant divides your visitor pool further, which means each variant needs longer to reach a reliable sample size. A test that would resolve in two weeks as an A/B test can stretch to six or eight weeks as an A/B/n test on the same traffic.
A/B/n testing is a genuine tool, not a shortcut. It earns its place when you have real traffic volume and a genuine need to compare multiple distinct concepts rather than one variable. Used on a low-traffic landing page, it mostly produces noise dressed up as a result.
A/B/n testing doesn't test more ideas faster. It tests the same number of ideas slower, with a bigger traffic bill.
How to calculate it
Traffic split = 100% divided by the number of variants, including the control
Worked example. You're testing a control plus three new headline variants, four versions total. With 4,000 weekly visitors, each variant gets roughly 1,000. If your baseline conversion rate is 3%, each variant only converts around 30 visitors a week, which is thin ground to declare a statistically significant winner.
The Australian context
Australia's smaller population means fewer sites have the raw traffic volume that A/B/n testing needs to produce trustworthy results in a reasonable window. A business in the United States or United Kingdom might comfortably run a four-way test on a high-traffic page. The equivalent Australian site, serving a market roughly a tenth the size, often needs to either run fewer variants or accept a much longer test duration.
For most mid-market Australian businesses, sequential A/B testing (one clear challenger at a time) delivers more usable results per month of testing than a sprawling A/B/n programme that never quite reaches significance on any single variant.
Where people get this wrong
Related terms
Common questions
How is A/B/n testing different from multivariate testing?
A/B/n testing compares complete, separate versions of a page against each other. Multivariate testing changes several individual elements at once and tests every combination. A/B/n asks 'which whole version wins', multivariate asks 'which combination of parts wins'. Multivariate needs even more traffic than A/B/n.
How many variants can I realistically test at once?
It depends entirely on your traffic and baseline conversion rate. As a general guide, if adding another variant means each one gets too few conversions per week to reach significance within a sensible timeframe, you've added one variant too many.
Do I need special software to run A/B/n tests?
Most standard CRO and conversion-rate optimisation platforms support A/B/n testing natively, since it's a straightforward extension of two-way testing. The tool matters less than having the traffic volume and patience to let each variant reach statistical significance before acting.
When should I use A/B/n testing instead of running sequential A/B tests?
Use A/B/n when you genuinely have several distinct concepts you need to compare and enough traffic to support it. If traffic is limited, sequential A/B testing, one challenger at a time, usually delivers more reliable results faster than splitting traffic too thin across several variants.
Debrief
Get the next one
No spam. No fluff. Just the next article, straight to your inbox.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →