
When Not to A/B Test
Is A/B testing always useful? Maybe not.
by Martin Horn
A/B testing has become shorthand for rigorous, evidence-based marketing. Put two versions into the market, compare the results, and let the data decide. The logic is sound. The problem is that many real-world tests are too small, too vague, or too messy to produce useful evidence.
Do not A/B test when the budget cannot generate enough observations.
If each version receives a few dozen clicks and one or two conversions, the apparent winner may be the product of chance. A difference of one registration can make one ad look dramatically stronger, even though there is no reliable pattern. In that situation, splitting the budget can reduce performance without creating meaningful learning.
Do not test without a hypothesis.
“Let’s see which one works” is not enough. A useful test asks a specific question: does a concrete benefit produce more registrations than an institutional message? Does showing the amount of a donation improve completion rates? Does a shorter form increase submissions? A clear hypothesis makes the result interpretable and reusable.
Do not change several major variables at once.
If one ad has a different image, headline, format, audience, and call to action, you are not testing a single idea. You are comparing two bundles. One may win, but you will not know why. This is sometimes acceptable when choosing between complete creative concepts, but it should not be presented as evidence about a particular element.
Testing can also be the wrong priority when the campaign has an obvious weakness. If the landing page is broken on mobile, the offer is unclear, or the tracking is unreliable, fix that first. There is little value in carefully comparing two headlines while a larger problem undermines both versions.
None of this means small organizations should abandon experimentation.
It means matching the method to the scale of the campaign. Sometimes the better approach is to run one strong version, observe patterns across several campaigns, and document what happens. Not every decision requires a formal test. Good judgment includes knowing when the available conditions cannot produce a trustworthy answer.
Have a difficult communications problem? Reach out, we’re always happy to chat.