---
title: Good experiment health
slug: experimentation-strategy/docs/good-experiment-health
createdAt: 2026-08-05T20:33:26.135Z
---

- Optimizely Web Experimentation
- Optimizely Performance Edge
- Optimizely Feature Experimentation
- Optimizely Full Stack (Legacy)

## The bottom line

When **Experiment Health** on your [experimentation results page](docId\:mrUblIuNVOZc1dvjWdsbw) displays **Good**, it means that your [Stats Engine](docId\:M_hHkOsff0PXhWFSIZNQn) experiment has the desired status.

The experiment's health status alerts you to untrustworthy experiment results on time.

## The green checkmark

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/MAUuaaavVW4T-x8BjCJs1-20260720-144745.png)

Whenever you launch a Stats Engine A/B test, Optimizely Experimentation's [automatic sample ratio mismatch (SRM) detection](https://www.optimizely.com/insights/blog/introducing-optimizelys-automatic-sample-ratio-mismatch-detection/) runs in the background. This algorithm finds unusual imbalances in visitor traffic to an experiment's variations and detects experiment problems early if they arise.

The Optimizely automatic SRM detection tool combines the power of automatic visitor imbalance detection with an indicator of experiment health. This indicator alerts you to any visitor traffic issues. It also tells you when everything works as expected and no traffic imbalance is present.

## Good experiment health status

In your live experiment, the *actual* split of traffic assigned to a variation relatively aligns with the *intended* traffic split you assigned to a variation. It means that your running experiment experiences a non-statistically significant difference in visitor counts at the expected probability (such as a 50/50 split between variations). See [Optimizely's automatic sample ratio mismatch (SRM) detection discovers any experiment deterioration early](docId\:JFKBHyB1tPQH0-EMRjAOR).

No underlying assignment bias is detected. It is not unusual for the traffic split to have this particular distribution. The algorithm finds no discrepancies between your intended outcome and the actual occurrences in the live experiment. See [Imbalance detected: What to do if Optimizely's automatic SRM detection alerts you to an imbalance in your Stats Engine A/B test](docId:2VGHBuvjNAJJnkir0LDTz).

## A sample ratio mismatch indicates a variety of data quality issues.

Optimizely's [automatic SRM detection](https://www.optimizely.com/insights/blog/introducing-optimizelys-automatic-sample-ratio-mismatch-detection/) continuously monitors your Stats Engine A/B tests and declares an imbalance carefully. The algorithm takes a dual-pronged, two-factor imbalance check by looking at the severity and consistency of the imbalance. This ongoing procedure during the life of your experiment maintains a **Good** status or changes to an imbalance detected and classified [Critical](docId\:m9r0cVA9YdjxBaSQRsFla). See [Imbalance detected: What to do if Optimizely's automatic SRM detection alerts you to an imbalance in your Stats Engine A/B test](docId:2VGHBuvjNAJJnkir0LDTz).
