Statsig WHN queries now carry cost attribution tags in your warehouse, so you can see exactly what Statsig activity is driving your compute costs.
Every query is stamped with is_whn, a type (experiment, gate, etc.), the experiment or gate name, a job type, and the reload ID. Tags land natively in each warehouse — nothing leaves your account:
Snowflake — session QUERY_TAG in ACCOUNT_USAGE.QUERY_HISTORY and QUERY_ATTRIBUTION_HISTORY
BigQuery — job labels (type=whn_query) in INFORMATION_SCHEMA.JOBS
Redshift — query_group in SYS_QUERY_HISTORY.query_label
Databricks — statement comment in system.query.history
Before , you could see total spend but had no way to attribute it to a specific experiment or job type in Statsig. Now, you can point one query at your warehouse's usage view, filter to Statsig WHN queries, group by experiment, and get per-experiment reload cost, making it straightforward to spot expensive reloads and change your schedule.
Filter your warehouse usage view to is_whn:"True" (or type=whn_query on BigQuery) and group by experiment to see per-experiment reload costs.
Learn more in the Statsig Warehouse Native docs.