Exposure forwarding FAQ

This page answers common questions about SDK-generated exposures Statsig forwards to a warehouse, including Warehouse Native experiments. It covers the daily export separately from best-effort exposure updates during results reloads. For setup and monitoring steps, go to Data warehouse exports.

Why do exposures appear in Diagnostics but not in my warehouse

Diagnostics shows exposures Statsig received. It doesn't confirm that an exposure qualifies for warehouse forwarding or has reached your warehouse. The daily export contains eligible first exposures and excludes experiment groups at 0% or 100% traffic share by default. For forwarding requirements, go to Forwarded Data.

Does 100% overall allocation stop exposure forwarding

No. Overall allocation controls how much eligible traffic enters the experiment. The group split controls how that traffic divides between variants. An experiment at 100% overall allocation with a 50/50 group split passes the group-percentage check. Other forwarding requirements still apply.

Why do some rows arrive for an experiment with a 0% or 100% group split

Results reloads may forward recent exposures before the daily export. These updates are best-effort and may arrive incomplete. The daily export may replace them. Rows arriving during a reload don't confirm that the experiment qualifies for the daily export. If you need exposures from experiment groups at 0% or 100%, contact Statsig Support.

Does a full reload recover missing historical exposures

A full reload recalculates experiment results. It doesn't rebuild or backfill the forwarded exposures table. A reload may also forward recent exposures before the daily export, but these updates are best-effort and may arrive incomplete. Use the daily export as the authoritative record of eligible forwarded exposures.

Does changing the reload schedule fill earlier exposure gaps

Changing the schedule controls when experiment results reload. It doesn't change forwarding eligibility or backfill the forwarded exposures table. Reload-time exposure updates are best-effort. Use the daily export as the authoritative record of eligible exposures.

How do I request exposures from experiment groups at 0% or 100%

Contact Statsig Support. Include the experiment link, affected dates and timezone, and destination table. The feature gate settings in the next question don't enable forwarding for experiment groups at 0% or 100%.

How do I turn on exposure tracking for feature gates at 0% or 100%

A project admin goes to Settings > Project Configuration > Feature Management and turns on Enable exposure tracking for 0/100% rolled out Gates. On each gate that needs these exposures, turn on Store 0/100 Exposures. Statsig bills these exposures as analytic events. The project setting doesn't turn on tracking for every gate. For details, go to Viewing Feature Gate exposures.

Does this restriction apply to every outgoing integration

This FAQ covers warehouse exposure forwarding. Other integrations have their own event selection and filtering controls. Selecting outgoing events for an integration doesn't override warehouse forwarding requirements. For integration controls, go to Event Filtering.

What should I check before reporting missing exposures

Confirm the project, experiment, destination table, dates, and timezone. Check the group split separately from overall allocation, review the forwarding requirements, and compare export history with the destination rows. A completed results reload doesn't confirm that the expected exposures reached the warehouse. Include these details when you contact Statsig Support.

Is the results SQL View the same as the forwarded exposures table

No. The forwarded exposures table stores eligible first exposures. The results SQL View stores Scorecard metric results and metadata. Statsig updates the view each time you load an experiment. Export Report creates a one-time CSV report. For details, go to Export Pulse results.

How do I monitor warehouse exports in Cloud and Warehouse Native

Check the export history for your project:

1. For scheduled data warehouse exports, including Cloud, go to Help and Tools > Exports List > Scheduled and open the connection card.
2. For Warehouse Native forwarded data, go to Settings > Data Connection > Export and use the exposure and event history charts.

For status details, failure notifications, and checks through the Console API or Statsig MCP, go to Monitor your export status. A missing status alone doesn't confirm whether data reached the destination. Check the destination rows.