An online controlled experiment is a randomized experiment conducted on live production traffic where users are randomly assigned to a control group or one or more treatment groups to measure the causal impact of a software change on key metrics. Unlike offline evaluation, this methodology isolates the effect of a specific variable—such as a new recommendation model or UI element—from external confounders by ensuring the only systematic difference between groups is the intervention itself. The approach relies on randomization to balance known and unknown covariates, enabling valid statistical inference through hypothesis testing.
Glossary
Online Controlled Experiment
What is an Online Controlled Experiment?
An online controlled experiment is a randomized experiment conducted on live production traffic to measure the causal impact of a software change on key metrics.
The infrastructure supporting these experiments requires a randomization unit (typically a user ID or device ID), a metrics pipeline to compute aggregate statistics, and a logging system to capture exposure events. Core statistical concepts include the null hypothesis (assuming no difference between variants), p-values for significance testing, and confidence intervals to quantify uncertainty around the estimated treatment effect. Properly designed experiments also monitor guardrail metrics to detect regressions and employ sample ratio mismatch checks to validate the integrity of the randomization mechanism before drawing conclusions.
Key Characteristics of a Valid Experiment
A valid online controlled experiment relies on rigorous statistical design and robust infrastructure to establish true causal relationships between a model change and observed business metrics, free from confounding biases.
Randomization & Independence
The cornerstone of causal inference. Users must be randomly assigned to control or treatment groups using a deterministic hashing algorithm on a stable user ID. This ensures that, on average, all known and unknown confounding covariates are balanced. A violation of the Stable Unit Treatment Value Assumption (SUTVA), known as the Interference Effect, occurs when the treatment of one user influences the outcome of another, breaking independence.
Statistical Power & MDE
An experiment must be adequately powered to detect a meaningful change. A Power Analysis calculates the required sample size based on:
- Minimum Detectable Effect (MDE): The smallest lift you care about.
- Statistical Power: Typically set to 80%, representing the probability of correctly rejecting a false null hypothesis.
- Significance Level (Alpha): Usually 5%. Insufficient power leads to Type II Errors (false negatives), missing real improvements.
Guardrail Metrics & Trustworthiness
Experiments must not sacrifice long-term health for short-term gains. Guardrail Metrics are secondary organizational checks that protect the business from unintended harm. Key trustworthiness checks include:
- Sample Ratio Mismatch (SRM): Verifying the actual traffic split matches the design to detect buggy randomization.
- Data Leakage: Ensuring no future information contaminates the training data.
- Peeking Problem: Avoiding the inflation of false positives by not stopping tests early based on interim significance.
Hypothesis Testing Framework
A structured statistical framework is required to draw conclusions. The process begins by assuming the Null Hypothesis (no difference exists). A P-Value is calculated to measure the probability of observing the data if the null were true. If the p-value falls below the significance threshold, the null is rejected. To control for multiplicity when testing many metrics, adjustments like the Bonferroni Correction or False Discovery Rate (FDR) control are essential to prevent Type I Errors (false positives).
Long-Term Impact & Holdouts
Standard A/B tests measure short-term impact but miss novelty effects or long-term user fatigue. A Holdout Group is a stable, permanent subset of users excluded from all experimental treatments. This group serves as a global baseline to measure the aggregate, cumulative causal impact of all model changes over months or years, preventing the tragedy of the commons where individually winning tests degrade the overall ecosystem.
Covariate Balance & Shift
Even with randomization, finite samples can be imbalanced. Stratified Sampling ensures critical segments are proportionally represented. During analysis, Covariate Shift must be monitored—if the input feature distribution diverges from the training set, the model's performance metrics become unreliable. Techniques like propensity score matching can adjust for residual imbalances, but they cannot replace proper randomization.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about designing, running, and interpreting online controlled experiments for AI-driven personalization.
An online controlled experiment is a randomized experiment conducted on live production traffic where users are randomly assigned to a control group or one or more treatment groups to measure the causal impact of a software change on key metrics. Unlike offline evaluation, it captures real user behavior in a genuine production environment. The mechanism relies on a randomization engine that deterministically assigns user IDs to variants based on a hash of the user identifier and a seed for the experiment layer. The control group receives the existing experience (often called the "holdback" or "baseline"), while the treatment group receives the new model, feature, or algorithm. A metric pipeline then computes summary statistics—such as the mean, variance, and sample size—for each group on North Star Metrics and guardrail metrics. Statistical tests, typically a Student's T-Test for continuous metrics or a Chi-Squared Test for binary metrics, determine whether the observed difference is statistically significant. The experiment runs for a pre-calculated duration based on a power analysis that specifies the minimum detectable effect and required sample size. Critically, experimenters must avoid the peeking problem by not stopping the test early based on interim p-values, which inflates the Type I Error rate. The output is a causal estimate of the treatment effect, expressed as a percentage delta with a confidence interval.
Online Controlled Experiment vs. Alternative Methods
A comparison of randomized online controlled experiments against quasi-experimental and observational methods for measuring the causal impact of software changes.
| Feature | Online Controlled Experiment | Pre-Post Analysis | Causal Impact (Synthetic Control) |
|---|---|---|---|
Randomization of Treatment Assignment | |||
Controls for Confounding Variables | |||
Requires Holdout Group | |||
Sensitive to External Time-Based Shocks | |||
Minimum Sample Size Required | 10,000+ users per variant | N/A (single cohort) | 100+ time periods |
Typical False Positive Rate Control | Precise (via p-value threshold) | Uncontrolled | Moderate (Bayesian posterior intervals) |
Real-Time Decisioning Compatibility | |||
Primary Use Case | Feature and model validation | Post-hoc campaign measurement | Macro-level intervention impact |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the statistical and methodological concepts essential for designing, executing, and interpreting rigorous online controlled experiments.
Statistical Power
The probability that a statistical test will correctly reject a false null hypothesis. It represents the experiment's sensitivity to detect a true effect if one exists.
- Standard target is 80% (0.80), meaning a 20% chance of a Type II Error (false negative)
- Directly influenced by sample size, effect size, and significance level
- Insufficient power is the primary reason experiments fail to detect genuine improvements
- Calculated during power analysis before launching an experiment
P-Value
The probability of observing a test statistic at least as extreme as the one calculated, assuming the null hypothesis is true. It is a measure of surprise, not a measure of effect magnitude.
- A p-value of 0.03 means: if there were truly no effect, you'd see results this extreme only 3% of the time
- The common threshold for significance is α = 0.05
- Does not measure the probability that the null hypothesis is true
- Highly susceptible to the peeking problem if interim checks are performed
Multi-Armed Bandit
A reinforcement learning approach that dynamically allocates more traffic to better-performing variants in real-time, minimizing the opportunity cost of exploration compared to traditional fixed-horizon tests.
- Epsilon-Greedy: exploits the best variant but explores randomly with probability ε
- Thompson Sampling: uses Bayesian inference to sample from posterior distributions
- Upper Confidence Bound (UCB): selects the arm with the highest upper bound on expected reward
- Reduces cumulative regret but complicates causal impact measurement for long-term metrics
Guardrail Metric
A secondary organizational metric monitored during an experiment to ensure that a new model or feature variant does not cause unintended harm to the business.
- Trustworthy metrics: verify experimental integrity (e.g., Sample Ratio Mismatch checks)
- Business metrics: protect revenue and user experience (e.g., latency, crash rate, gross merchandise volume)
- Trigger automatic alerts or experiment shutdown if degradation exceeds a predefined threshold
- Essential for fairness-aware personalization to detect disparate impact across segments
Interference Effect
A violation of the Stable Unit Treatment Value Assumption (SUTVA) where the treatment applied to one experimental unit influences the outcome of another.
- Common in two-sided marketplaces: treating a driver affects the experience of riders
- Occurs in social networks: a user's new feature changes their friends' behavior
- Mitigated by cluster randomization (randomizing at the city or network level)
- Ignoring interference leads to biased effect size estimates and incorrect conclusions
Holdout Group
A long-term, stable subset of users who are permanently excluded from any experimental treatments to serve as a global baseline.
- Measures the aggregate, cumulative impact of all model changes over months or years
- Prevents innovation theater: ensures short-term A/B wins translate to genuine long-term value
- Typically 1-5% of total traffic, kept in a pristine, untreated state
- Critical for validating North Star Metric trends against a true control

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us