On this page

Export Pulse Results to Your Warehouse in Warehouse Native

Access and interpret Statsig Warehouse Native experiment results in the console, including Pulse, scorecard, drill-down, and exported analysis views.

How to access Pulse data in Warehouse Native

WHN lets you access exposures and metric results across all experiments directly in your warehouse through SQL Views defined in your Statsig project using a metric source.

Exposures

Statsig automatically writes exposures to your warehouse to the table configured in your project setup. To find the table's location, go to Settings > Data Connection. The table should be located at the {Database Name}.{Schema Name}.{Exposures Forwarding Table Name}, e.g. experimentation.statsig.exposures.

Results

With a SQL View, you have access to experiment metadata (such as experiment team, tags, target duration, and settings like CUPED and Sequential testing), each metric’s metadata (such as metric tags), and all metric lifts: the same set of results visible on the Console. To start using this feature, enable it at Project Settings > Data Connection > Export. After enabling it, Statsig automatically sets up the SQL View in your warehouse and creates the metric source in your Statsig project.

Statsig automatically exports scorecard metric results to your data warehouse each time an experiment is loaded, generating a new copy. To differentiate result versions, use the ds column, which contains the timestamp when Statsig wrote the data to your warehouse.

Project settings data connection export interface

Schema of the results data export table

The default table name used is statsig_daily_results. When exports are enabled, Statsig also autocreates a metric source with this name in your Statsig project.

Report types

There are three types of exports:

  1. Exposures - A table of all exposed users and their first exposures. This is useful for joining on your own internal data, and running custom queries within your own data warehouse. You can also use it to verify who was in the experiment, what group they were assigned to, and when they were first exposed (around 1-25MB). This contains:

    1. <experiment\>_first_exposures.csv - contains a list of users and their first exposure to the experiment.
  2. Pulse Summary - This provides precomputed summary experimental data for all metrics and test groups including everything that's visible on Pulse (around 10-100 kb). This contains:

    1. <experiment\>_pulse_summary.csv - contains Pulse aggregate metrics computed over the duration of the experiment.
  3. Raw Data - This provides raw exposures and metrics data at the user-day level. This is best used for manually inspecting data, or recomputing your own statistics (around 10MB-1GB). This contains:

    1. <experiment\>_first_exposures.csv - contains a list of users and their first exposure to the experiment. If this is the only file you are interested in, you can get this by exporting an "Exposures" report which is much smaller in size.
    2. <experiment\>_user_metrics.csv - contains a list of experimental users, and their calculated metrics for each day they were enrolled in the experiment.
In WHN, only the Pulse Summary can be exported, because the other two types of data are only stored in your warehouse. The availability of these exports is subject to the retention policy. Statsig holds exposures data for up to 90 days after an experiment is concluded, and holds raw user-level metrics data for 90 days.

Pulse Summary file description - for Feature Gates

Pulse Summary file description - for experiments

First exposures file description

Unit metrics file description

Was this helpful?