---
title: How to Read Experiment Results
description: "Read and interpret Statsig experiment results, including scorecards, primary metrics, lift, confidence intervals, and statistical significance indicators."
product: general
lang: en
last_updated: 2025-09-18
token_estimate: 3241
---
# How to Read Experiment Results

The Results tab shows how each experiment group performed on your primary and secondary metrics: the relative lift, its confidence interval, and whether the result is statistically significant. Use it to check exposures and the Scorecard for a running or completed experiment. To filter or group results by a dimension the Scorecard doesn't show, use a [custom Explore query](https://docs.statsig.com/experiments/interpreting-results/custom-queries).

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

## Cumulative exposures

**Figure: Cumulative exposures by model group**

A launch burst brings the experiment to nearly 70,000 exposures in four days, then enrollment settles into a steady climb to 118,356 units, split within half a point of a third for each of the three model groups.

Stacked area chart. X axis: Date. Y axis: Cumulative exposures.

| Date | GPT-3 (Control) | GPT-4 | GPT-4o |
| --- | --- | --- | --- |
| 2026-02-17 | 0 | 0 | 0 |
| 2026-02-18 | 6526 | 7338 | 7029 |
| 2026-02-19 | 12757 | 13667 | 13364 |
| 2026-02-20 | 19214 | 19710 | 19406 |
| 2026-02-21 | 23169 | 23425 | 23402 |
| 2026-02-22 | 23412 | 23691 | 23683 |
| 2026-02-23 | 23884 | 24233 | 24185 |
| 2026-02-24 | 24385 | 24732 | 24702 |
| 2026-02-25 | 24781 | 25159 | 25154 |
| 2026-02-26 | 25198 | 25579 | 25575 |
| 2026-02-27 | 25559 | 25976 | 26013 |
| 2026-02-28 | 25851 | 26227 | 26296 |
| 2026-03-01 | 26099 | 26501 | 26562 |
| 2026-03-02 | 26659 | 26974 | 27093 |
| 2026-03-03 | 27069 | 27438 | 27546 |
| 2026-03-04 | 27474 | 27863 | 27965 |
| 2026-03-05 | 27949 | 28288 | 28375 |
| 2026-03-06 | 28376 | 28649 | 28789 |
| 2026-03-07 | 28630 | 28919 | 29091 |
| 2026-03-08 | 28892 | 29155 | 29326 |
| 2026-03-09 | 29364 | 29713 | 29906 |
| 2026-03-10 | 29844 | 30178 | 30418 |
| 2026-03-11 | 30331 | 30583 | 30870 |
| 2026-03-12 | 30715 | 31015 | 31273 |
| 2026-03-13 | 31131 | 31470 | 31712 |
| 2026-03-14 | 31432 | 31763 | 32000 |
| 2026-03-15 | 31668 | 32028 | 32261 |
| 2026-03-16 | 32130 | 32586 | 32728 |
| 2026-03-17 | 32624 | 33091 | 33238 |
| 2026-03-18 | 33085 | 33575 | 33634 |
| 2026-03-19 | 33462 | 33991 | 34018 |
| 2026-03-20 | 33905 | 34439 | 34405 |
| 2026-03-21 | 34163 | 34685 | 34682 |
| 2026-03-22 | 34433 | 34937 | 34943 |
| 2026-03-23 | 34986 | 35493 | 35460 |
| 2026-03-24 | 35476 | 35982 | 35960 |
| 2026-03-25 | 35952 | 36395 | 36404 |
| 2026-03-26 | 36421 | 36790 | 36814 |
| 2026-03-27 | 36855 | 37240 | 37195 |
| 2026-03-28 | 37118 | 37528 | 37452 |
| 2026-03-29 | 37380 | 37814 | 37723 |
| 2026-03-30 | 37845 | 38318 | 38286 |
| 2026-03-31 | 38316 | 38812 | 38727 |
| 2026-04-01 | 38776 | 39205 | 39166 |
| 2026-04-02 | 39176 | 39610 | 39570 |

The Cumulative Exposures chart shows exposures: the unique experimental units enrolled in the experiment, typically unique users, or devices for device-level experiments. The timeline shows when the experiment started and how many exposures Statsig enrolled each day. Use this chart to verify the rate at which users entered each group, the total number exposed, and whether the target ratio matches what you configured in experiment setup. Click the **See More** option to expand the chart.

## Scorecard

The experiment Scorecard shows the metric lifts for all of the primary and secondary metrics that you set up when creating the experiment.

### Real-time results in the first 24 hours

Statsig calculates the Scorecard results hourly up to the first 24 hours after you start your experiment. Statsig calculates Scorecard results before the first daily metric results run. This hourly calculation applies only to Statsig Cloud. For Warehouse Native projects, reload results on demand or set up a daily schedule. Use the real-time Scorecard to confirm that Statsig calculates exposures and metrics as expected, and to debug your experiment or gate setup.

> **Note:**
>
> Don't make any experiment decisions based on real-time results data in this first 24-hour time period. Let the experiment reaches its target duration, which is when your primary metrics reach experimental power, before you make any decisions. For more information about target duration, go to [Target Duration](https://docs.statsig.com/experiments/setup/analysis-settings#target-duration).

Until the first daily run, the real-time view differs from daily results in the following ways:

- Metric lifts don't have confidence intervals.
- There's no time-series view of metric trends.
- There's no projected topline impact analysis.
- You can't apply advanced statistical treatments such as CUPED or sequential testing.

### Daily Scorecard results

![Experiment scorecard table displaying metric lifts and confidence intervals](https://docs.statsig.com/images/snippets/pulse/read-results/8b855f5c-d26f-4185-ac31-5108fbebe18e.png)

The daily results run calculates the difference between randomization groups (for example, test and control) across your metric suite and applies a statistical test to the results. Refer to [Statsig's stats engine](https://docs.statsig.com/experiments/statistical-methods/introduction) for details.

For every metric, Statsig shows you:

- The calculated relative difference (Delta %).
- The confidence interval.
- Whether the result is statistically significant. Positive lifts are green, negative lifts are red, and non-significant results are grey.

The formula for calculating lift is:

$$
\Delta \overline{X} \% = \frac{\overline{X}_t - \overline{X}_c}{\overline{X}_c} \times 100 \%
$$

Statsig reports confidence intervals at the selected significance level (95% by default). In a typical two-sided Z-test, Statsig shows the confidence interval as $\pm 1.96 \times$ standard error.

Statsig automatically applies 99.9% winsorization to `event_count`, `event_count_custom`, and `sum` metrics. Winsorization caps extreme outlier values to reduce their impact on experiment results. For metrics in the Scorecard or Monitoring Metrics sections of your experiment or gate, you can also apply optional statistical treatments such as: CUPED (pre-experiment bias reduction) and sequential-testing-adjusted confidence intervals.

### 90-day compute window

By default, Statsig computes experiment results for only the first 90 days of your experiment. Statsig notifies you by email as you approach the 90-day cap. At that point, you can extend the compute window by 30 days at a time. If the experiment runs beyond the compute window, Statsig stops adding new users to the experiment's results. Analysis for users already exposed continues until you make a decision on the experiment.

This calculation window only affects whether Statsig includes a user in the experiment's analysis. It doesn't affect the experience each user receives: new users still receive the experience for the group Statsig randomizes them into.

## Experiment results views

On the Results tab, select **Display Options** and then set **Chart Type** to choose how the Scorecard renders metric lifts.

| Chart Type | What it shows |
| --- | --- |
| Cumulative (default) | The aggregate difference between experiment groups, with the corresponding confidence intervals. Hover over a metric for the raw statistics behind the lift calculation and the topline impact. |
| Daily | The difference between experiment groups, aggregated by days since the experiment started. |
| Days Since Exposure | The difference between experiment groups, aggregated by days since each user's exposure to the experiment. |
| Table | The same data as the cumulative view, in a table with additional fields. |

The **Display Options** panel also includes:

- **Data**: Choose the value to display: Relative Delta, Absolute Delta (per unit), Relative or Absolute Topline Impact, or Relative or Absolute Projected Launch Impact. For what the impact values mean, go to [Topline impact](https://docs.statsig.com/experiments/statistical-methods/topline-impact).
- **Zoom**: Adjust the zoom level of the chart.
- **Sort By** / **Organize By**: Control the order and grouping of the metrics.
- **Filters**: Filter the displayed metrics by tag or filter group.

![Cumulative results view with hover details](https://docs.statsig.com/images/snippets/pulse/read-results/856c7750-df56-45d9-b253-6b63f336cac7.png)

## Dimensions

You can break down a Scorecard metric by a user dimension or by an event dimension.

### User dimensions

User dimensions are user-level attributes that are either part of the user object you log or additional metadata that Statsig extracts. Examples include operating system, country, and region.

To filter or group by user dimensions, create a [custom Explore query](https://docs.statsig.com/experiments/interpreting-results/custom-queries) on the **Explore** tab. For example, view results for users in the US, or for users on iOS grouped by country.

### Event dimensions

Event dimensions are the `value` or `metadata` logged as part of the custom event that defines the metric. To break a metric down by categories specific to that metric, [specify the dimension](https://docs.statsig.com/metrics/metric-dimensions) in the `value` or `metadata` attribute when you log the source event. For example, when you log a "click" event, you can also log the target category in the `value` attribute. Statsig automatically generates results for each category in addition to the top-level metric.

To view breakdowns for all categories within a metric, select the (+) sign next to the metric.

![dimension results view](https://docs.statsig.com/images/snippets/pulse/read-results/f557dac6-e29f-4cb5-bd6a-19fc2b226193.png)

## Significance level settings

Open the _Comparison & Stats_ panel to view Scorecard results at different significance levels and adjust the statistical settings. To open it, select the pencil icon next to the Test and Control summary row on the Scorecard. The panel also includes **Compare** and relative-to group pickers that control which groups Statsig compares.

- **Confidence Interval**: Changes the confidence interval displayed with the metric deltas. Choose from 80%, 90%, 95%, 98%, or 99%. A lower confidence interval accepts a higher false-positive rate in exchange for faster, directional results.
- **CUPED**: Toggle CUPED on or off. This setting applies only to Scorecard metrics; Statsig doesn't apply CUPED to non-Scorecard metrics.
- **Sequential Testing**: Applies a correction to p-values and confidence intervals to reduce the increased false positive rate caused by evaluating results before the target completion date. This setting appears only for experiments with a set target duration.
- **SPRT**: Toggle the Sequential Probability Ratio Test (SPRT) on or off. SPRT is a sequential testing methodology that supports unlimited peeking without alpha-spending or confidence-interval penalties. Refer to [Sequential Probability Ratio Tests](https://docs.statsig.com/experiments/advanced-setup/sprt) for details, including its configuration options.
- **Power Parameter**: Appears when SPRT is on. Sets the target statistical power (1 − β) that Statsig uses to compute the SPRT decision boundaries. The default is 80%; choose from 80%, 90%, 95%, 98%, or 99%. This isn't the per-metric effect size: set the Minimum Detectable Effect (MDE) and Cohen's d separately during experiment setup, as described in [Power analysis and setting Cohen's d](https://docs.statsig.com/experiments/advanced-setup/sprt#power-analysis-and-setting-cohens-d).

Multiple-hypothesis corrections aren't in this panel. Set [Bonferroni correction](https://docs.statsig.com/experiments/statistical-methods/methodologies/bonferroni-correction) and the [Benjamini-Hochberg procedure](https://docs.statsig.com/experiments/statistical-methods/methodologies/benjamini-hochberg-procedure) in _Advanced Settings_ on the [experiment's _Setup_ tab](https://docs.statsig.com/experiments/setup/analysis-settings#significance-level-adjustments).

## Restarting results

If your experiment has stopped computing results, select **Restart** to resume updates. Understand how Restart behaves before you proceed:

- A Restart isn't a [Reset](https://docs.statsig.com/experiments/ending/reset) of your experiment. A Restart doesn't re-salt (re-randomize) units, and all users continue to receive the same group assignments.
- Statsig begins computing experiment results from the restart point, so your metric results start over. Old results may still appear in time series and Explore query views, but Statsig doesn't carry them forward or update them.
- Your Cumulative Exposures chart updates based on new exposures. The duration of the pause in computations determines whether the chart starts over from zero or includes past exposures.

To avoid needing a Restart, extend experiments while they're running. Watch for email alerts from Statsig and check your experiments regularly.

