Optimizely Advanced Audience Targeting Destination
Optimizely Advanced Audience Targeting allows you to sync your Segment Engage audiences to Optimizely for targeting with Web Experimentation audiences, Feature Experimentation audiences, and CMS Visitor Groups.
This destination is maintained by Optimizely. For any issues with the destination, contact the Optimizely Support team.
Getting started
Within your Optimizely Data Platform Account
- Navigate to the App Directory.
- Use autocomplete to find the Twilio Segment app.
- Click into the app and click INSTALL.
- Click SETTINGS > GENERATE and copy the resulting token to your clipboard.
Within your Twilio Segment Account
- From the Segment web app, navigate to Connections > Catalog and select the Destinations tab of the catalog.
- Select the Destinations Actions tab and search for Optimizely Advanced Audience Targeting.
- Select the Configure Optimizely Advanced Audience Targeting tile.
- Select your Engage Space as a source. Note that this destination only works when an Engage Space is configured as a Source.
- Click Confirm Source.
- Within the Settings tab paste your ODP token into the API Key field, select your region, enable the integration and click Save Changes.
- Click into the Mappings section, then click New Mapping, then click on the Sync Audience tile.
- In section 3 Select Mappings ensure the user identifier you are targeting with your Advanced Audience Targeting integration is mapped to the Optimizely User ID field.
- Click Save.
- Enable the Action by toggling the Status to Enabled.
- Click back to the Settings tab and enable the destination by toggling the Enable Destination toggle to On.
- Click Save changes.
Destination Settings
Setting | Description |
---|---|
Api Key | Required. Api Key used for Optimizely API authorization when sending events |
Region | Required. The Optimizely Region to sync Audience data to. Default is US |
Available Actions
Build your own Mappings. Combine supported triggers with the following Optimizely Advanced Audience Targeting-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Sync Audience
Sync a Segment Engage Audience to Optimizely Data Platform
Sync Audience is a Cloud action. The default Trigger is: type = "track" or type = "identify"
Field | Description |
---|---|
Custom Audience Name* | Type: STRING Name of custom audience to add or remove the user from |
Segment Computation Action* | Type: STRING Segment computation class used to determine payload is for an Audience |
Segment Computation ID* | Type: STRING Segment computation ID |
Optimizely User ID* | Type: STRING The user identifier to sync to the Optimizely Audience |
Timestamp* | Type: STRING Timestamp indicates when the user was added or removed from the Audience |
Notes
-
Ensure the Advanced Audience Targeting integration is configured in your Optimizely Products so that you can access your connected audiences from Segment Engage.
-
If connecting your Segment Engage audiences to Optimizely Web Experimentation ensure the user id mapped to the Optimizely User ID in the Destination mappings area is an identifier available on the browser (client side). This allows Optimizely web to properly check audience membership for visitors included in connected Segment Engage audiences.
Engage
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true
. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false
.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Optimizely Advanced Audience Targeting may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
Setting | Description |
---|---|
Api Key (required) |
password . Api Key used for Optimizely API authorization when sending events |
Region (required) |
select . The Optimizely Region to sync Audience data to. Default is US |
This page was last modified: 18 Oct 2023
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!