Process / pipelineMarketing ScienceDigital experimentation / causal inferencePipeline

Online Controlled Experiment

Also known as: A/B Testing, Split Testing, Randomized Web Experiment, Controlled Experiment on the Web

Online controlled experiments, commonly called A/B tests, randomly split live web or app traffic between a control and one or more treatment variants to measure the causal effect of a change on user behavior. Ron Kohavi, Diane Tang, and Ya Xu — who built and ran experimentation platforms at Microsoft, Google, and LinkedIn — set out the modern theory and best practice in their 2020 Cambridge book, and Kohavi's earlier survey with colleagues established the practical foundations of running trustworthy web experiments at scale. The discipline centers on a clearly defined Overall Evaluation Criterion (OEC) that captures long-term value, rigorous randomization, adequate statistical power, and a battery of trustworthiness checks such as the Sample Ratio Mismatch test. Because users are randomized, the difference in metrics between variants is an unbiased estimate of the change's causal impact — the gold standard for marketing and product decisions that attribution and observational analysis can only approximate. The output is a confident ship/no-ship decision: did this headline, layout, price, or feature actually move the metrics that matter, by how much, and with what certainty?

Key highlights

  • Randomization yields unbiased causal estimates of a change's effect, the gold standard versus observational or attribution analysis.
  • Forces a disciplined Overall Evaluation Criterion that ties decisions to long-term value rather than vanity metrics.
  • Scales to thousands of concurrent tests on live traffic, enabling rapid, evidence-based iteration.
  • Built-in trustworthiness checks like Sample Ratio Mismatch catch instrumentation and design bugs that would otherwise mislead.

Intuition

This section is available to Pro members. Upgrade to Pro

How it works

This section is available to Pro members. Upgrade to Pro

When to use it

Use online controlled experiments whenever you can randomly assign live users to variants and want a causal answer about a change to a website, app, email, ad, price, or algorithm. They are the right tool for evaluating UI changes, copy and creative, recommendation and ranking models, pricing and promotion mechanics, onboarding flows, and feature launches — anywhere enough traffic exists to detect a meaningful effect and outcomes can be logged reliably. They are the gold standard precisely because randomization removes the confounding that plagues attribution and observational analysis. Online experiments are less applicable when traffic or conversion volume is too low to reach adequate power, when randomization is infeasible or unethical, when effects unfold over very long horizons or spill over between units (network effects, marketplace interference) so that simple user-level randomization is biased, or when the change cannot be toggled per user. In those cases switchback designs, geo-experiments, or quasi-experimental methods are alternatives, and uplift modeling can extend experimental learnings to targeting.

Strengths & limitations

Strengths
  • Randomization yields unbiased causal estimates of a change's effect, the gold standard versus observational or attribution analysis.
  • Forces a disciplined Overall Evaluation Criterion that ties decisions to long-term value rather than vanity metrics.
  • Scales to thousands of concurrent tests on live traffic, enabling rapid, evidence-based iteration.
  • Built-in trustworthiness checks like Sample Ratio Mismatch catch instrumentation and design bugs that would otherwise mislead.
Limitations
  • Requires substantial traffic to achieve adequate power; low-volume products cannot detect realistic effect sizes.
  • Network effects, marketplace interference, and spillovers can bias simple user-level randomization.
  • Short experiments can be confounded by novelty or primacy effects that fade, misstating long-term impact.
  • A good OEC is hard to define, and optimizing a poor proxy metric can ship changes that quietly harm the business.

Common pitfalls

This section is available to Pro members. Upgrade to Pro

Applications

This section is available to Pro members. Upgrade to Pro

Frequently asked

What is an Overall Evaluation Criterion and why does it matter so much?

The OEC is the metric, or weighted set of metrics, that defines success for the experiment and ideally reflects long-term business value rather than a short-term proxy. Kohavi, Tang, and Xu argue it is the single most important and most difficult design decision, because experimentation will relentlessly optimize whatever you measure. If you pick clicks, you may ship clickbait that boosts clicks while eroding trust, revenue, or retention. A good OEC is sensitive enough to move within a reasonable test, hard to game, and aligned with strategic goals, often paired with guardrail metrics that must not degrade. Getting the OEC right is what separates experiments that improve the business from experiments that merely produce statistically significant but harmful 'wins.'

Why is peeking at results and stopping early a problem?

Classical fixed-horizon statistical tests assume you decide the sample size in advance and analyze once. If you instead watch the p-value continuously and stop the moment it crosses the significance threshold, you give random noise many chances to fake a win, which dramatically inflates the false-positive rate — well above the nominal level. Kohavi and colleagues highlight this as one of the most common and damaging mistakes in web experimentation. The fixes are to commit to a planned sample size and duration, or to use methods designed for continuous monitoring such as sequential testing or always-valid confidence intervals, which control error rates under repeated looks. Either way, results must not be cherry-picked at the first favorable moment.

What is a Sample Ratio Mismatch and why check for it?

A Sample Ratio Mismatch (SRM) occurs when the actual proportion of users in each variant differs significantly from the intended split, for example a 50/50 design that arrives as 52/48 at large scale. Because the assignment is supposed to be random, a meaningful deviation signals a bug — a broken redirect, asymmetric logging, bot filtering, or a flawed randomization unit — that almost always biases the results, often masquerading as a lift. Kohavi's work treats the SRM test (a simple chi-square on the observed versus expected counts) as a mandatory trustworthiness gate: if it fails, the experiment's metrics are not to be trusted no matter how attractive the apparent effect, and the root cause must be fixed before any conclusion is drawn.

Sources

  1. 1.
    Kohavi, R., Tang, D., & Xu, Y. (2020). Trustworthy Online Controlled Experiments: A Practical Guide to A/B Testing. Cambridge University Press.
    ISBN 9781108724265
  2. 2.
    Kohavi, R., Longbotham, R., Sommerfield, D., & Henne, R. M. (2009). Controlled experiments on the web: survey and practical guide. Data Mining and Knowledge Discovery, 18(1), 140-181.

You have read it. What now?

Cite this page

ScholarGate. (2026, June 23). Online Controlled Experiment. ScholarGate. https://scholargate.app/marketing-science/online-controlled-experiment