> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/integrations/feature-flagging/statsig.md).

# Statsig

<div align="left"><figure><img src="https://727226624-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MjFmyReUsbJqDjHEAlW%2Fuploads%2F3KuZqFUki71pfmxTSy5S%2Fstatsig.png?alt=media&amp;token=40bc6a7c-5e73-444d-8586-e85b66b84b2e" alt=""><figcaption></figcaption></figure></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect Statsig**

* Find the **Statsig** integration module under the **Feature Flagging** section
* Click the **Connect** button
* Enter a Statsig **Console API Key**
  * You can access or create a new Console API Key by visiting **Settings > Keys & Environments** in Statsig.

### Configure the Statsig integration

1. Confirm the name of your **Production** environment from the drop down list
2. Enter a release version attribute name. This is the name of the audience attribute you use to segment feature flags by release version (e.g. `app_version`)&#x20;
3. Runway supports the following options for filtering:&#x20;
   1. Target by platform in the flag itself — add a rule on the gate/dynamic config with a condition where *Operating System = Platform* (e.g. iOS or Android). Runway reads these conditions and will correctly associate the flag with the matching Runway app.
   2. Tag the flag with the OS — apply a platform-specific tag (e.g. `ios`, `android`) to the flag in Statsig.