> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Optimizely
## Overview
Optimizely is a web personalisation platform that can run personalised web campaigns. Integrated with Zeotap it enhances Optimizely's offering, allowing businesses to deliver highly personalised and engaging experiences to their website visitors, driving improved conversion rates and customer satisfaction.
## Supported Identifiers
This integration supports Optimizely IDs.
## Available Actions and Supported Features
The following table lists the available action types for the integration and the supported features for each action type:
| Action Name | [ID EXTENSION](/articles/segment-customer/extend-your-audience#id-extension) | [DELETE](https://docs.zeotap.com/articles/#!integrate-customer/delta-upload-and-delete-functions) | [DELTA UPLOAD](https://docs.zeotap.com/articles/#!integrate-customer/delta-upload-and-delete-functions) |
| :----------------------------- | :--------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------ |
| Send identifiers to Optimizely | ✅ | ✅ | - |
## Components of Optimizely
Ensure that you have the Access Token obtained from your Optimizely POC before starting this integration.
### Access Token
An Access Token is a unique identifier that grants authorised access to the Optimizely REST APIs, through which the data communication is established between Zeotap and Optimizely. Reach out to your Optimizely POC to obtain this information.
## Create a Destination for Optimizely
Perform the following steps to create a Destination for Optimizely:
Log into the Zeotap CDP App and go to the **DESTINATIONS** application.
Click **+ Create Destination.**
Under the **All Destinations** section, search for **Optimizely**.
Click **Optimizely.** A screen appears displaying details about the particular destination towards the left. On the right-hand side of the screen find a list of fields that are required for the integration to be established. Enter the required details as mentioned in the following steps:
a. Enter a name for the Destination.
b. Enter the **Access Token** that you have obtained from Optimizely.
c. Review all the values entered above and then click **Next** to proceed.
In the new screen that appears, choose the appropriate Action and mapping as explained below.
a. Choose the desired [action](/articles/integrate-customer/destinations#actionsanchor) under **Choose your Action** and then choose any identifier from your Catalogue that you wish to send as Optimizely ID under **Map the Fields**. For more information about mapping, refer [here](/articles/integrate-customer/destinations#mappingsanchor).
b. Review the fields you have mapped and click **Create Destination**. The created Destination gets listed in the **Audiences** application, which can be linked to an Audience/segment.
## Link an Audience to the Optimizely Destination
For information about how to link an Audience or segment to the created Destination in the **Audiences** application, refer [here](/articles/integrate-customer/link-an-audience-to-the-destination). Note that it can take up to three business days for segments to be available at the Optimizely seat.
**Note:**
The terms *Audiences* and *Segments* are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an Audience or a segment could be a specific group of customers who are over 18 years of age and who have performed an *`addToCart`* event within the last 30 days.
## User Disqualification from Audiences
This integration supports user disqualification from audiences. That is, a user can be disqualified from an audience (segment) for various reasons, such as not meeting audience criteria, consent requirements or other conditions set for a particular audience.
* When a user disqualifies from an audience, Zeotap CDP initiates a user deletion request in the next refresh cycle. These requests are sent to the audiences linked to the specific destination.
* The disqualified users are excluded from the audiences based on the configured refresh frequency for a particular audience.
* User disqualification is a programmatic process that works automatically. You do not need to specify anything to trigger the disqualification and exclusion of users from audiences.