Content Lexicon.

A/B testing

In one line

A way to compare two or more live variants with users, useful when the question is specific and the measure actually matters.

In an A/B test, one group might see version A of a page, email or journey while another sees version B. The team then looks at what people actually did, rather than relying only on opinion, preference or whoever was most confident in the meeting.

For content work, A/B testing can be useful when the question is specific, the audience is large enough and the team knows what kind of evidence would be meaningful. It can help compare calls to action, page structures, subject lines, onboarding flows or different ways of explaining a choice.

The trap is thinking that A/B testing automatically tells you what is better. It usually tells you what performed better under particular conditions, for a particular audience, against a particular metric. If the metric is too narrow, the test may reward worse content: more clicks, less understanding; more sign-ups, more regret; more attention, less trust.

Why it matters for content

A/B testing matters because content decisions are often argued from taste. One person likes the short version. Another wants more detail. Someone senior prefers a phrase they saw on a competitor’s website and suddenly everyone is pretending that counts as strategy.

A good test can bring evidence into that argument. It can show whether people notice a message, understand an offer, complete a task or choose one route more often than another. Used carefully, it helps teams learn from behaviour rather than endless internal debate.

But content teams need to be careful about what they are testing. Not every content question can or should be reduced to a conversion rate. Some content exists to reduce anxiety, explain complexity, build confidence, prevent mistakes or help people make better decisions. Those outcomes may not show up neatly in a quick A/B test.

How AI changes the picture

AI makes A/B testing easier to overproduce. It can generate headlines, summaries, calls to action, email variants and page introductions at speed. That can be useful when a team has a clear hypothesis and a disciplined way to review the options.

It can also create a fog of plausible alternatives. If the team tests variations without understanding the purpose of the content, the test becomes theatre: lots of variants, lots of numbers and very little judgement. The danger is not that AI makes bad options. The danger is that it makes too many mediocre ones, quickly enough to make them look intentional.

AI can help with A/B testing when it is used to sharpen hypotheses, draft sensible variants and summarise results. It should not be used as an excuse to test everything or to avoid deciding what good content is supposed to do.

Questions people ask

Is A/B testing the same as branching?

No. A/B testing compares two or more live variants with users to see which performs better. A branch is a separate working version where changes can be developed, reviewed and tested before they become live. A/B testing can happen from a branch, but branching is about controlled change rather than optimisation.

What makes a good A/B test?

A good A/B test starts with a clear hypothesis, a meaningful measure and a real decision the team is prepared to make afterwards. If nobody knows what will change as a result, the test is probably just decorative analytics.

Can content teams use A/B testing without huge traffic?

Sometimes, but small samples make it harder to trust the result. With lower traffic, teams may learn more from moderated research, usability testing, customer conversations or careful analysis of support and behaviour data.

What can go wrong?

Teams can test trivial differences, stop too early, overread weak results or optimise for the wrong metric. The biggest risk is mistaking “this won a test” for “this is better content”.

Learn more

Type a term, or a word from its definition.⌘K opens this from any page.