> 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="/files/Gu9YZKDmaOrz4BSjE2S7" 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.runway.team/integrations/feature-flagging/statsig.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.