All terms

CRO Glossary

Post-Test Segmentation Bias

The distortion introduced when segments are defined or chosen after seeing test results, inflating the odds of spurious findings.

Post-test segmentation bias occurs when analysts slice experiment data into subgroups (by device, geography, new vs. returning user, etc.) after observing the overall result, specifically looking for a segment where the effect looks stronger, weaker, or significant. Because many possible segment cuts exist, some will show an apparently notable pattern purely by chance — a variation of the multiple comparisons problem applied specifically to ad hoc segment hunting.

This matters because it's an easy trap: a flat overall result tempts teams to keep cutting the data until they find a segment that "worked," then present that as the headline finding. Without pre-registering which segments matter and why, this practice manufactures false confidence and can lead to shipping changes that only helped a randomly favorable slice of users.

For example, if an email signup test shows no significant lift overall, but a post-hoc cut reveals a 15% lift among users on Safari in the afternoon, that's a red flag rather than a discovery — it's one of dozens of possible cuts, and Safari-afternoon-afternoon combinations have no causal story behind them.

The fix is to decide key segments of interest in the experiment design document before launch, correct for multiple comparisons when segments are examined, and treat any unplanned segment findings as hypotheses for a dedicated follow-up test rather than as conclusions.

Related terms

See this in the wild

ABWatcher watches how top teams apply post-test segmentation bias.

Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.