Statsig

Statsig is a product observability platform.

Features

Setup guide

Follow our step-by-step Statsig setup guide to connect Statsig with your destination using Fivetran connectors.

Sync overview

To capture new records, we incrementally sync the following tables:

• AUDIT_LOG
• EVENT_CONFIG_CHANGE
• EVENT_UPDATED
• FIRST_EXPOSURES_REPORT
• PULSE_DAILY_REPORT

Schema information

This schema applies to all Statsig connectors.

Explore Statsig schema ERD

Explore the interactive ERD

Fivetran-generated columns

We add the following columns to every table in your destination:

• _fivetran_synced (UTC TIMESTAMP) indicates the time when Fivetran last successfully synced the row.
• _fivetran_id (STRING) is the hash of the non-Fivetran values of each row. It's a unique ID that Fivetran uses to identify rows in tables that do not have a primary key.
• _fivetran_deleted (BOOLEAN) marks rows that were deleted in the source database.

We add these columns to give you insight into the state of your data and the progress of your data syncs.

Primary key usage

We use fivetran_id as the primary key for the following tables:

• AUDIT_LOG_CHANGE_RULE_CONDITION
• EVENT_CONFIG_CHANGE
• EXPERIMENT_GROUP
• FIRST_EXPOSURES_REPORT
• GATE_RULE_CONDITION_TARGET_VALUE
• PULSE_DAILY_REPORT

Statsig API limitations

The Statsig API's Daily Report endpoint has the following restrictions:

• The Daily Reports endpoint is accessible only to customers having an Enterprise plan. To enable this feature, contact Statsig's support team, your sales contact, or through the Slack channel.
• The Daily Report endpoint syncs only 7 day's worth of data for the FIRST_EXPOSURES_REPORT and PULSE_DAILY_REPORT tables.
• For any given date range, we can only fetch up to 10000 records for the AUDIT_LOG table due to source-side limitations.