Paid media

A/B testing

Split testing

Comparing two versions against each other to see which performs better.

Traffic is split between a control and a variant differing in one respect, and results are compared once enough data has accumulated to distinguish a real difference from noise. Changing several things at once tells you that something worked without telling you what.

Key takeaways

  • Work out before launching how much traffic it would take to detect the difference you care about. Most tests that end inconclusively were unwinnable on day one.
  • Small effects need large samples. Detecting a ten per cent relative lift on a three per cent conversion rate takes thousands of conversions per variant.
  • Stopping the moment a result looks significant inflates false positives, because every look is another chance to be fooled.
  • Running A this month and B next is not an A/B test. Seasonality and competitor activity will usually outweigh the effect being measured.
  • Deciding a test is not worth running is a real result and it saves a fortnight.

Deciding what you could detect before you launch

The step most agency tests skip is the one that determines whether the test can work. Before launching, decide how large a difference would be worth acting on, then work out roughly how much traffic each variant would need for a difference that size to be distinguishable from noise.

Run without that calculation, a test has two ways to end and both are bad. It runs out of time with no clear winner, which reads as a waste of a month. Or somebody calls it early on a gap that was noise, which is worse, because it produces a confident wrong answer that then gets rolled out across the account.

The arithmetic is unforgiving on small numbers. Detecting a ten per cent relative improvement on a baseline conversion rate of three per cent needs on the order of thousands of conversions per variant, which is more than many client accounts produce in a quarter. Halve the effect you want to detect and the traffic needed roughly quadruples.

This is why the honest conclusion is sometimes that the test should not run. An account generating forty conversions a month cannot resolve a ten per cent difference before the season changes underneath it, and saying so is more useful than starting anyway.

Why stopping early produces confident wrong answers

A significance test is built on the assumption that you look once, at a point decided in advance. Checking every morning and stopping the day it crosses the threshold breaks that assumption, because each look is an independent opportunity for random variation to cross the line.

The effect is large rather than marginal. Repeatedly peeking at a test with no real difference will eventually show a significant result a substantial share of the time, and the earlier you are willing to stop, the more often that happens.

It is also the most natural thing in the world to do, which is why it is worth guarding against structurally rather than by intention. Decide the end date and the sample size at the start, write them down, and treat the test as unread until then.

Where continuous monitoring genuinely matters, the fix is to use a method designed for it, such as a sequential test with corrected thresholds, rather than to apply a fixed-horizon test more often. Guessing at an adjustment is not a method.

Running A this month and B next is not a test

Comparing one period against the next is the most common substitute for a real test in agency work, usually because splitting traffic felt complicated. It measures the change plus everything else that moved between the two periods, and everything else is normally larger.

Consider what shifts across four weeks: the season, competitor budgets, a public holiday, the mix of returning and new visitors, a change in the ad platform nobody announced. Any of those can produce a swing bigger than the creative difference being tested.

The version that looks more rigorous and is not is testing across matched periods, such as the same fortnight last year. It relies on the assumption that the market was comparable, which is the assumption the test was supposed to check.

If traffic genuinely cannot be split, then say the result is directional and treat it that way. The failure is not running a before-and-after comparison, it is presenting one as though it were an experiment.

What is worth testing in a small account

The size of the detectable effect determines what is worth testing, and that reverses the usual priority order. Button colours and headline tweaks produce small differences that a small account can never resolve; offers, pricing presentation and page structure produce large ones that it sometimes can.

So on a modest budget, test things that could plausibly move the result by a third rather than by a twentieth. A different offer, a materially shorter form, a landing page built around a different objection. If the honest expectation is a few per cent, the test will not settle it.

Splitting by user rather than by campaign matters as much as what is tested. Two campaigns will not deliver to the same audience mix, so a campaign-level split compares variants and audiences together and cannot separate them.

Finally, a result is a result for the context that produced it. A variant that won during a promotion, on mobile, for returning visitors, has been shown to win there. Rolling it everywhere is an extrapolation, and it is worth labelling it as one in the report.

What it means for an agency

Estimate the traffic needed before launching. Saying "this account cannot resolve a difference that small, so let us test something bigger" is a far better use of a fortnight than a test nobody can interpret.

Where it goes wrong

  • Stopping a test the moment it looks significant. Peeking repeatedly inflates false positives.
  • Splitting by campaign rather than by user, so the two variants reach different audiences and the comparison confounds the two.
  • Testing changes too small for the account to detect, which guarantees an inconclusive month.
  • Rolling a winning variant everywhere when it won in one context, on one device, during one promotion.

In short

The discipline in testing is not statistical, it is deciding in advance what would count as an answer. A test with a stated effect size, a stated sample size and a stated end date produces something you can act on. Without those it produces a number that confirms whatever the person reading it already believed.

Frequently asked questions

How long should an A/B test run?

Long enough to reach the sample size decided before launch, and at least one full business cycle so that weekday and weekend behaviour are both represented. Duration on its own is not the criterion. A fortnight is plenty for a high-traffic page and nowhere near enough for an account producing forty conversions a month.

Why should I not stop a test as soon as it looks significant?

Because significance tests assume a single look at a predetermined point. Checking repeatedly and stopping at the first threshold crossing gives random variation many chances to cross it, so a test with no real difference will often produce an apparently significant one. If you need to monitor continuously, use a sequential method built for it rather than applying the usual test more often.

Can I test two things at once?

You can, but a plain A/B test will only tell you that the combination performed differently, not which change was responsible. Isolating the cause needs either separate tests or a multivariate design, and multivariate designs need considerably more traffic because they split it across more combinations.

My account is too small to test. What should I do instead?

Test larger changes rather than smaller ones, since a big effect needs far less traffic to detect. Beyond that, treat before-and-after comparisons as directional evidence and label them that way, and put the effort into things that do not need a test to justify, such as fixing tracking, matching the landing page to the ad, and removing steps from the form.

Related terms

Sources

Last reviewed

Keplent keeps track of these for you.

It holds what each client agreed to, watches what their campaigns actually did, and tells you in plain sentences what needs you this week.

Join the waitlist