> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abtestly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reading a result

> A tour of the results page. What each panel means, what to trust today, and when the test is actually done.

The results page is one long screen. It always shows things in the same
order, meta at the top, segment filters, the verdict, per-variant
performance, segments, speed. Once you know the order it reads quickly.

<Frame caption="Results page while a test is still gathering.">
  <img src="https://mintcdn.com/abtestly/TJFfWsOMn4uzK6iy/images/experiment-results.png?fit=max&auto=format&n=TJFfWsOMn4uzK6iy&q=85&s=013971f058a8ede724cf860bee674454" alt="Results page for a live experiment" width="2400" height="1141" data-path="images/experiment-results.png" />
</Frame>

## Meta bar

Six things: start date, end date (blank while it is running), days
running, report date range, baseline, and any active segments.

* **Report range** defaults to the full running time. Change it to Last 7
  or Last 14 to focus on recent traffic.
* **Baseline** is the variant every other variant is compared to. Defaults
  to the natural control (position 0). Override with the dropdown when you
  are comparing two treatments and neither is the "original".

## The verdict

Below meta, one heading. Written in plain English. It says one of:

| Verdict                           | What it means                                                                                 |
| --------------------------------- | --------------------------------------------------------------------------------------------- |
| **Still gathering**               | Not enough data yet. Wait.                                                                    |
| **No effect**                     | The engine can rule out an effect meaningful to your bar.                                     |
| **Variant X is the front-runner** | Ahead, but not confident enough to call.                                                      |
| **Variant X wins on \[goal]**     | Confident enough to call. Time to ship.                                                       |
| **Variant X harms a guardrail**   | Wins on the primary goal but breaks something else. Read the guardrail panel before shipping. |

The verdict is written by [the engine you picked](/results/engines).
Frequentist, sequential, and Bayesian each phrase the same result slightly
differently, the shape of the sentence is the same.

## Per-variant performance

Each variant gets a row. Visitors, conversions (or revenue), rate, and
lift-vs-baseline with a confidence interval. The interval is what tells
you whether the number is trustworthy.

* **Wide interval that crosses zero:** no honest read yet. Keep collecting.
* **Interval clears zero:** an effect that direction. Read the verdict copy
  for whether it is large enough to call.

Revenue tests have four possible metrics, conversion rate, revenue per
visitor, average order value, orders per visitor, see
[revenue metrics](/results/revenue-metrics).

## Confidence over time

A cumulative confidence chart plotted daily. It shows whether your test
is converging (line trending toward a call) or wandering (line bouncing
around zero). A test that has wandered for two weeks usually means the
effect is not there.

## Segments

Below performance, a segment bar with an **Add segment** button. Slice
the whole report by:

* Device / browser / OS
* Country
* New vs returning
* Traffic source / entry path / UTM campaign

Segments are URL-shareable, the filter shows up in the URL, so paste it
into a Slack message and your colleague sees the same slice.

<Note>
  Segments narrow the whole report. When you filter to "Mobile", the
  verdict, per-variant rows, chart, and speed panel all recompute for
  mobile visitors only. Sample sizes shrink accordingly, and the verdict
  copy respects that.
</Note>

## Speed guardrail

If the site has speed data, a per-device panel shows p75 largest
contentful paint for each variant, baseline first. This is a **guardrail**
a variant that wins on your primary goal but tanks LCP on mobile is
almost never worth shipping. The panel is quiet when it has nothing to
say.

## SRM and completeness

Two banners can appear at the top of the page:

* **Sample ratio mismatch (SRM).** The visitor split does not match the
  weights you set. Almost always a targeting or activation problem, not a
  statistics one. See [SRM](/results/srm).
* **Processing.** The exact ledger is catching up on a burst of events.
  The dashboard's live counters are current; the verdict is held while
  the ledger settles.

## Exports

Top-right of the results page:

* **Refresh data**, recomputes now.
* **Export**, CSV of the aggregated table, or an asynchronous raw-event
  export in CSV or JSONL. See [Exports](/results/exports).
* **Reset data**, discards all data collected on this experiment and
  starts a new epoch. Used when you changed the variant meaningfully and
  want the numbers to reflect only the new version. Confirmation-gated.

## When am I done?

There is no universal number. As a rough guide:

* **At least a few thousand visitors per variant.** A hundred visitors on
  each arm cannot resolve a real 5 % lift.
* **The verdict is a call, not a front-runner.** "Front-runner" means
  "ahead, keep looking".
* **The confidence line has stopped moving fast.** A line still climbing
  steeply means new data is still shifting the result.
* **No red guardrails.** A win with a broken guardrail is not a win.

For a proper answer read [time to decision](/results/time-to-decision).
The results page has a small "time to decision" hint that estimates the
same thing on your specific test.