Skip to main content
Use stability and uncertainty to decide how much weight a measurement can carry. A precise-looking percentage is not enough on its own.

​
Check stability after selecting the run

Call get_results_stability with the same project, run, and supported filters as your analysis. The default aggregation is domain. The signal-to-noise ratio is key to interpreting whether the measurement has enough separation to support a decision. Below the target, differences can be too small relative to uncertainty. Reaching the target alone is not sufficient: the ranking check must also pass. Use the returned flags. Do not replace them with your own fixed rank-percentage threshold or treat “95% confidence” as a 95% stability requirement. Domain and URL SNR describe different scopes; never compare one against the other as if they were the same number.

​
What to do with each result

Collecting too little data can leave you acting on noise. Once the relevant checks pass and the intervals are adequate for the decision, collecting more of the same data may add limited value and consume resources. These read tools do not automatically stop or launch a measurement, and no single sample count guarantees convergence.

​
Keep row quality and run quality separate

An individual estimate can have stability: "stable", "danger_zone", or "insufficient". These are row-level indicators. They do not replace the run’s convergence result. Mark limited rows clearly and avoid presenting insufficient rows as findings. A decision-grade run still contains uncertain estimates and does not make an assistant’s interpretation infallible. For change claims, use the confidence interval on the difference and the returned comparison result. See compare measurements.