> 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/optimizely.md).

# Optimizely

<div align="left"><figure><img src="/files/cwpnBVFVLSmFuPsMRYdb" 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 Optimizely**

* Find the **Optimizely** integration module under the **Feature Flagging** section
* Click the **Connect** button
* Enter an Optimizely **Personal API Access Token**
  * You can access or create a new Personal API Access Token by visiting **Profile > API Access** in Optimizely. :link:[Optimizely documentation: Generating a personal access token](https://support.optimizely.com/hc/en-us/articles/4410282713997-Generate-a-personal-access-token-in-Optimizely)

### Configure the Optimizely integration

1. Select the desired Optimizely project from the drop down list
2. Confirm the name of your **Production** environment from the drop down list
3. 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;
4. Runway supports filtering via the Audience field. Create (or reuse) an audience that represents the platform and attach it to the flag's rule. Runway surfaces audience-based targeting, so flags scoped to an iOS-only or Android-only audience will only be associated with the matching app.


---

# 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/optimizely.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.