Use Statsig as a GrowthLoop destination to export Audiences to Statsig ID List segments. You can target those segments in feature gates, experiments, and dynamic configs.

Prerequisites

Before you connect Statsig to GrowthLoop, make sure you have:

• A Statsig project with permission to create API keys.
• A Console API key from Statsig Project Settings → Keys & Environments. The key must start with console-.
• User identifiers in your warehouse that match the Statsig ID type you will use (default userID).

🚧

Important

Do not use a Server Secret key (secret-...) for this destination. Server keys can evaluate gates and log events, but they cannot create or update segments. GrowthLoop needs a Console API key to manage ID List membership.

What GrowthLoop updates in Statsig

When you export an Audience to Statsig, GrowthLoop:

• Creates or reuses an ID List segment named after your GrowthLoop Audience.
• Adds user IDs for members who enter the audience.
• Removes user IDs for members who leave the audience.

GrowthLoop matches each exported row using the User ID (or ID) match field you configure on the export.

Set up destination

1. In GrowthLoop, navigate to Destinations in the left sidebar.

2. Click New Destination in the upper right corner.

3. In the Select Destination window, search for Statsig.

4. Click Add Statsig.

5. Enter the following destination details:

   1. Destination Name: Enter a clear name your team will recognize in GrowthLoop.
   2. Sync Frequency: Choose how often GrowthLoop should export audiences by default.
   3. Console API Key: Paste your Statsig Console API key (console-...).
   4. ID Type (Optional): Defaults to userID. Change this only if your Statsig project uses a different ID type (for example stableID).

6. Click Create. GrowthLoop validates the connection by listing segments with the Console API.

Export to destination

1. Navigate to Audiences in the left sidebar.
2. Open an existing Audience or create a new Audience.
3. Click Export Audience.
4. Select your Statsig destination.
5. In Match Fields, map your source identifier to User ID (or ID).
6. Save and run the export.

After the export succeeds, open the matching ID List segment in the Statsig console and confirm membership.

Troubleshooting

• Credential validation fails: Confirm the key starts with console- and has write access in Statsig.
• Users missing from the segment: Confirm the match field values match the Statsig ID type on the segment.
• Wrong key type: Server Secret keys return a Console API error that only Console keys are accepted.

For Statsig Console API details, see the Statsig Console API overview and ID List segments.