Statsig
BetaThis source is currently in beta. It works end to end, but you may still hit rough edges. Let us know if you do.
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Connect Statsig to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter a Console API key from Statsig Project Settings. The key needs read access to the tables you select. The users table contains project members.
Configuration
| Option | Type | Required |
|---|---|---|
Console API key | password | Yes |
Linking Statsig to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Statsig
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
gates | Feature gates with targeting rules, status, and rollout settings. | Full refresh | — | id |
experiments | Experiments with groups, allocation, metrics, and lifecycle status. | Full refresh | — | id |
dynamic_configs | Dynamic configurations with default values, targeting rules, and enabled status. | Full refresh | — | id |
layers | Experiment layers with shared parameters and ownership metadata. | Full refresh | — | id |
segments | User segments defined by rules or identifier lists. | Full refresh | — | id |
metrics | Metric definitions with types, directionality, and event lineage. This table does not contain measured values. | Full refresh | — | id |
audit_logs | Project changes with action types, affected objects, and the members who made them. | Full refresh | — | id |
users | Statsig project members and their roles. This table does not contain tracked end users. | Full refresh | — | userID |