All terms

CRO Glossary

Experiment Health Score

A composite indicator of whether a running test's data quality and setup are trustworthy enough to draw conclusions from.

An experiment health score rolls up several diagnostic checks — sample ratio mismatch, traffic stability, instrumentation errors, outlier rates, and exposure consistency — into a single signal that tells a team whether a test is behaving as expected. Rather than waiting until the end of a test to discover something went wrong, teams use this score to catch problems early, often within the first day or two of launch.

It matters because a clean-looking lift can be an illusion caused by broken tracking, a caching bug that only affects one variant, or a segment of bot traffic skewing one arm. Without a health check layer, teams end up making decisions on data that was never valid in the first place, and the error is only found in a post-mortem.

For example, a testing platform might flag a test as 'unhealthy' because the control is receiving 54% of traffic instead of the expected 50%, or because mobile exposure dropped sharply after a deploy. The team can then pause, investigate, and restart rather than letting the test run to completion on bad data.

In practice, health scoring is usually automated as a dashboard or alert system sitting alongside the main results view, separate from the statistical read-out itself.

Related terms

See this in the wild

ABWatcher watches how top teams apply experiment health score.

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