Early Diagnostics

Exposures from Statsig SDKs

When Pulse is loaded, Statsig performs a just-in-time update of exposures in your warehouse for the first 1 million exposures per experiment. After that threshold, updates occur on a daily cadence.

After launching an experiment, you may want to check certain results (such as page load time, impressions on key pages, and business-critical metrics) as early as possible to detect crashes or bugs.

If you are using the Statsig SDK to generate exposures, Statsig updates exposures in your warehouse before computing Pulse results when Pulse is loaded soon after the experiment starts. This lets you see Pulse results as fresh as approximately 15 minutes (assuming events and metrics arrive at the same speed).

After the first 1 million exposures, Statsig batches, deduplicates, and writes exposures to your warehouse once a day. The daily job also includes additional fields that the just-in-time write doesn't include (for example, Group Names).

Custom Events from Statsig SDKs

Statsig exports custom event logs to your warehouse hourly, plus a short processing delay. You can see Pulse results on metrics derived from those events as fresh as approximately 1 hour.