Simpson's Paradox is a statistical phenomenon where an association between two variables consistently observed within subgroups of a population reverses direction when those subgroups are aggregated into a single pool. This reversal occurs due to a hidden confounding variable—often an unequal distribution of sample sizes or a lurking categorical factor—that distorts the marginal association, making the aggregate conclusion mathematically correct yet practically misleading for decision-making.
Glossary
Simpson's Paradox

What is Simpson's Paradox?
A statistical paradox where a trend appearing in several data groups reverses or disappears when the groups are combined, posing a critical risk to valid inference in segmented A/B test analysis.
In A/B testing infrastructure, the paradox frequently manifests when experimenters segment results by device type, geography, or user cohort without applying proper statistical controls like the Cochran-Mantel-Haenszel test. A new recommendation model may appear to increase conversion in both mobile and desktop segments individually, yet show a global decrease when combined—simply because the lower-converting mobile segment received a disproportionate share of overall traffic during the experiment.
Core Characteristics
The defining features of Simpson's Paradox and why it represents a critical threat to valid inference in segmented A/B tests.
Trend Reversal on Aggregation
The defining characteristic: a statistical relationship present in multiple subgroups disappears or reverses direction when the subgroups are combined into a single aggregate view. For example, a new recommendation model may show a positive lift in conversion rate for both mobile and desktop users separately, but when the data is pooled, the aggregate metric shows a negative lift. This occurs because the confounding variable (device type) influences both the assignment to the variant and the baseline conversion rate.
Confounding Variable Dependency
The paradox is always driven by a lurking or confounding variable that correlates with both the independent variable (treatment assignment) and the dependent variable (outcome metric). In experimentation, this often manifests as:
- Unequal sample sizes across segments
- Different baseline conversion rates between segments
- Imbalanced traffic allocation that skews the aggregate Without identifying and controlling for this confound, the aggregate result is mathematically correct but causally misleading.
Simpson's Reversal in A/B Tests
In online controlled experiments, the paradox emerges when traffic splits are not uniform across user segments. Consider a test where the treatment group receives 80% mobile users (low-converting) and 20% desktop users (high-converting), while the control group has the inverse proportion. Even if the treatment improves conversion within each device segment, the aggregate metric will favor the control group simply because it contains more high-converting desktop users. This is not a model failure — it is a compositional artifact.
Mitigation via Stratified Analysis
The primary defense is to never rely solely on aggregate metrics. Best practices include:
- Stratified sampling: Ensure treatment and control groups have identical covariate distributions at assignment time
- Segment-level reporting: Always examine treatment effects within key subgroups (device, geography, user tenure) before aggregating
- Weighted averages: Use fixed weights based on the population distribution rather than sample proportions to compute an unbiased overall effect
- Regression adjustment: Include the confounding variable as a covariate in a linear model to isolate the treatment effect
Historical Origin
The paradox is named after Edward H. Simpson, who described the phenomenon in a 1951 paper, though Karl Pearson and Udny Yule had observed similar effects decades earlier. A famous real-world example is the UC Berkeley gender bias case (1973), where aggregate admission data appeared to show bias against women, but a department-by-department analysis revealed a slight bias in favor of women. The reversal occurred because women applied disproportionately to more competitive departments with lower overall admission rates.
Relationship to Berkson's Paradox
Simpson's Paradox is closely related to Berkson's Paradox, another statistical phenomenon where conditioning on a common effect creates a spurious negative correlation between two independent causes. While Simpson's involves aggregation across subgroups, Berkson's involves selection bias from conditioning. Both highlight the danger of drawing causal conclusions from observational data without a clear understanding of the underlying data-generating process and the role of collider variables.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about Simpson's Paradox and its dangerous implications for segmented A/B test analysis.
Simpson's Paradox is a statistical phenomenon where a trend or relationship that appears consistently within multiple subgroups of data reverses or disappears entirely when those subgroups are aggregated into a single population. The mechanism driving this paradox is the presence of a lurking variable—often an uneven distribution of sample sizes or a confounding covariate—that differentially weights the subgroups during aggregation. For example, a new recommendation algorithm might show a higher conversion rate than the control in both mobile and desktop segments individually, yet show a lower overall conversion rate when the segments are combined. This occurs because the algorithm was disproportionately served to the lower-converting mobile segment, skewing the aggregate average. The paradox is not a flaw in the mathematics; it is a structural artifact of collapsing a multidimensional contingency table into a marginal table, which can produce a weighted average that points in the opposite direction of every conditional association.
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
Mastering Simpson's Paradox requires a deep understanding of the statistical and experimental design principles that prevent segmented data from misleading aggregate conclusions.
Stratified Sampling
A randomization technique that divides the population into homogeneous subgroups before sampling to ensure the treatment and control groups are balanced on critical covariates. By controlling for the confounding variable that causes the reversal, stratified sampling prevents Simpson's Paradox from manifesting in the first place.
- Mechanism: Pre-segment users by the confounding variable (e.g., device type, traffic source) before random assignment.
- Benefit: Reduces variance and guarantees proportional representation of segments in both control and treatment arms.
- Contrast: Post-hoc segmentation without stratified assignment is where the paradox thrives.
Confidence Interval
A range of values, derived from sample data, that is likely to contain the true population parameter with a specified probability. When analyzing segmented results, overlapping confidence intervals between subgroups can signal the presence of Simpson's Paradox.
- Interpretation: A 95% CI means that if the experiment were repeated many times, 95% of the intervals would contain the true effect.
- Paradox Detection: If the aggregate CI points in one direction but every segment's CI points in the opposite direction, the aggregation is confounded.
- Key Metric: Always report CIs at both the aggregate and segment levels.
Covariate Shift
A specific type of data distribution change where the input feature distribution differs between the training and inference environments. In A/B testing, a covariate shift in the underlying user population mix can trigger Simpson's Paradox by changing the relative sizes of subgroups.
- Example: A mobile-heavy user base during a holiday sale versus a desktop-heavy base during weekdays.
- Impact: The aggregate metric shifts not because of the treatment, but because the weighting of segments changed.
- Mitigation: Use propensity score matching or inverse probability weighting to re-balance the covariate distribution.
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. This creates a hidden confounding structure that can mimic Simpson's Paradox in two-sided marketplaces.
- Mechanism: If treating a power seller changes the experience for buyers in the control group, the groups are no longer independent.
- Paradox Link: The interference creates a latent variable that confounds the relationship between treatment and outcome.
- Detection: Use network-clustered randomization or ego-network analysis to isolate interference.
Causal Impact
A time-series analysis methodology developed by Google that constructs a synthetic counterfactual baseline to estimate the causal effect of an intervention. It is invaluable for diagnosing Simpson's Paradox when a randomized control group is unavailable.
- How it works: Builds a Bayesian structural time-series model using control time series to predict the post-intervention period.
- Paradox Application: Run Causal Impact on each segment independently to see if the direction of effect is consistent before aggregating.
- Output: Provides a posterior distribution of the causal effect, not just a point estimate.
Guardrail Metric
A secondary organizational metric monitored during an experiment to ensure that a new model or feature variant does not cause unintended harm. Guardrails are the first line of defense against Simpson's Paradox masking a negative effect in a critical subgroup.
- Segmented Guardrails: Define specific guardrails for high-value segments (e.g., paying users, new users) rather than relying solely on the global average.
- Example: A recommendation model increases aggregate click-through rate but degrades the experience for the top 1% of power users.
- Action: If a segment-level guardrail fails, the experiment is halted regardless of the aggregate North Star Metric.

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