Growth Marketing Glossary

Variant

var·i·antnoun

The version you are testing. In an A/B test, a variant carries the change you want to measure, and its results are compared against the untouched control.

control versionapply the changevariant version
Schematic — the treatment measured against the control
Term
Variant
Is
A version carrying the tested change
Compared to
The control (unchanged version)
Used in
A/B and multivariate testing

Parts of speech & senses

variant · noun
  1. In an A/B test, a variant is a version of a page, ad, or email that carries the change you are testing — the treatment measured against the unchanged control to see whether the change helps. "The variant with the shorter form beat the control."

What a variant is

In experimentation, a variant is a version of whatever you are testing — a landing page, a headline, an email subject line, a checkout flow — that carries the specific change you want to evaluate. Say your current signup page has a long form and you suspect a shorter one would convert better. The long form is the control, the untouched baseline. The short form is the variant, the treatment. You split incoming visitors so some see the control and some see the variant, then compare how each group behaves. The variant is defined by exactly one intended difference from the control (or a small, deliberate set of differences), because the point is to isolate the effect of that change. Everything else — the traffic source, the timing, the audience mix — is held as equal as randomization allows, so the difference in results can be pinned on the variant.

A test can have more than one variant. A simple A/B test pits a single variant against the control. An A/B/n test runs several variants at once — three headlines, four button colors — each measured against the same baseline. Multivariate testing goes further, combining changes across elements and treating each combination as its own variant. Whatever the count, the logic holds: each variant is a candidate version, and the experiment exists to learn which one performs best on a chosen metric such as conversion rate, click-through rate, or revenue per visitor. A variant only earns the label winner when the difference is both meaningful and statistically credible, not merely a lucky swing in a small sample. Until then it is a hypothesis wearing a version number.

Variant versus control

The variant and the control are the two halves of the comparison, and confusing them muddies the whole test. The control is the incumbent — the version already in use, or the plain baseline, left exactly as it is. The variant is the challenger — the version altered on purpose to test an idea. The control's job is to answer what would have happened anyway, so the variant's lift can be measured against it rather than against nothing. Without a control, a rise in conversions after you launch a new page could be seasonality, a pricing change, or a good news cycle. The control absorbs all of that shared context, and the gap that remains between control and variant is the estimated effect of the change.

Naming discipline matters here. If you relabel a version mid-test, or quietly ship a second tweak to the variant, you no longer know what you measured. Keep the control frozen and the variant changed in one clear way. It also helps to remember that variant is a role, not a permanent identity: today's winning variant becomes tomorrow's control when it is rolled out and a fresh challenger is designed against it. That is how iterative testing compounds — each accepted variant resets the baseline, and the next experiment measures the next idea against the improved standard rather than the original one.

Using variants well

Good variant design starts with a clear hypothesis: this specific change will move this specific metric for this reason. Build the variant to test that idea and little else, so a result can be attributed cleanly. Split traffic randomly and concurrently — running the control this week and the variant next week reintroduces all the time-based noise a proper split removes. Decide the sample size and duration before you look at results, and hold to them, because peeking and stopping the moment a variant looks ahead is how false winners get shipped. Judge the variant on the metric that matters to the business, not a vanity proxy, and watch for guardrail metrics so a variant that lifts clicks but tanks revenue is caught.

The common failures are testing too many changes in one variant (so you cannot tell which change did the work), calling a winner from a handful of conversions, and ignoring segments where a variant that wins on average loses badly for a key audience. Underpowered tests are the quiet killer — a variant that looks 20% better on 40 conversions is often just noise. Treat a variant as a genuine question, size the test to answer it, protect the control, and only promote a variant to the new baseline when the evidence is real. Done this way, variants turn opinion into measured learning instead of a coin flip dressed up as a decision.

Worked example. An ecommerce team suspects that moving free-shipping messaging above the fold will lift purchases. The control is the current product page. The variant is identical except the free-shipping banner sits at the top. They split traffic evenly and randomly, set the test to run until each group reaches a pre-agreed sample size, and track conversion rate as the primary metric with revenue per visitor as a guardrail. When the variant finishes clearly ahead on both, they roll it out — and it becomes the new control for the next test. The lesson is that a variant carries one deliberate change measured against a frozen control, and only a credible, meaningful gap earns it the label of winner. (Illustrative; RGM analysis.)
Failure modes to watch. Bundling several changes into one variant so no single cause is identifiable; declaring a winner from too few conversions or by peeking early; running the control and variant at different times so seasonality contaminates the result; and ignoring segment differences where a variant that wins on average loses for an important audience.

Synonyms & antonyms

Synonyms

treatmenttest versionchallenger

Antonyms

controlbaseline

Origin & history

Variant — from Latin variare, to vary — names the changed version tested against a control in an experiment, the treatment whose effect on a chosen metric the test is designed to measure.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is a variant in an A/B test?
It is the version carrying the change you want to test — the treatment. You compare it against the control, the unchanged baseline, so the difference in results estimates the effect of the change.
How is a variant different from the control?
The control is the existing, unaltered version and answers what would happen anyway. The variant is deliberately changed to test an idea. The gap between them is the measured effect of that change.
Can a test have more than one variant?
Yes. An A/B/n test runs several variants against one control, and multivariate testing combines changes into many variant combinations. Each is measured against the same baseline to find the best performer.

Resources & people to follow

Curated, non-competitor resources verified per term.

Related training

Disciplines

Areas of marketing where variant is a core concern:

Sources

  1. trendsGoogle Trends — "a/b test variant"