-
Notifications
You must be signed in to change notification settings - Fork 357
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
921e394
commit ad03deb
Showing
1 changed file
with
16 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,12 @@ | ||
--- | ||
Optimizely Advanced Audience Targeting Destination | ||
title: Optimizely Advanced Audience Targeting Destination | ||
id: 64edeb2bee24614fe52ede34 | ||
beta: true | ||
--- | ||
|
||
{% include content/plan-grid.md name="actions" %} | ||
|
||
[Optimizely Advanced Audience Targeting](https://optimizely.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) allows you to sync your Segment Engage audiences to Optimizely for targeting with Web Experimentation audiences, Feature Experimentation audiences, and CMS Visitor Groups. | ||
[Optimizely Advanced Audience Targeting](https://optimizely.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target=”blank”} 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 their Support team](mailto:[email protected]). | ||
|
||
|
@@ -13,6 +15,7 @@ This destination is maintained by Optimizely. For any issues with the destinatio | |
## Getting started | ||
|
||
**Within your Optimizely Data Platform Account** | ||
|
||
1. Navigate to the **App Directory** in the top right (small boxes with + sign icon) | ||
2. Use the autocomplete to find the **Twilio Segment** App | ||
3. Click into the app and click the blue **INSTALL** button in the top left | ||
|
@@ -21,24 +24,21 @@ This destination is maintained by Optimizely. For any issues with the destinatio | |
**Within your Twilio Segment Account** | ||
|
||
1. From the Segment web app, click **Catalog**, then click **Destinations**. | ||
2. Find the Destinations Actions item in the left navigation, and click it. | ||
3. Click **Configure Optimizely Advanced Audience Targeting**. | ||
4. Select your **Personas** source as the source (The app will not work with any other source) | ||
2. Click on the Destinations Actions tab and search for **Optimizely Advanced Audience Targeting**. | ||
3. Click on the **Configure Optimizely Advanced Audience Targeting** tile. | ||
4. Select your **Engage Space** as a source. Note that this destination will only work when an Engage Space is configured as a Source. | ||
5. Click **Confirm Source** | ||
6. Within the **Settings** tab paste your ODP token into the **API Key** field, select your region, enable the integration and click **Save** | ||
7. Click into the **Mappings** section and click **New Mapping** | ||
6. Within the **Settings** tab paste your ODP token into the **API Key** field, select your region, enable the integration and click **Save Changes** | ||
7. Click into the **Mappings** section, then click **New Mapping**, then click on the **Sync Audience** tile. | ||
8. 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. | ||
9. Click the Save button to save the Action. | ||
10. Enable the Action by toggling the Status to **Enabled** | ||
11. Click back to the **Settings** tab and enabled the Destination by Toggling the **Enable Destination** toggle to “On”, then click “Save Changes”. | ||
|
||
{% include components/actions-fields.html %} | ||
|
||
### **Notes for Using the Destination** | ||
|
||
- Ensure the Advanced Audience Targeting integration is configured in your Optimizely Products so that you can access your connected audiences from Twilio Segment in your Optimizely Product (Web Experimentation, Feature Experimentation, and CMS Visitor Groups). Documentation: | ||
|
||
[Web Experimentation Advanced Audience Targeting](https://docs.developers.optimizely.com/web-experimentation/docs/configure-odp-audience-targeting#integrate-with-other-cdps) | ||
|
||
[Feature Experimentation Advanced Audience Targeting](https://docs.developers.optimizely.com/feature-experimentation/docs/optimizely-data-platform-advanced-audience-targeting) | ||
**Notes for Using the Destination** | ||
|
||
[CMS Visitor Groups Advanced Audience Targeting](https://github.com/unrvld/ODP.VisitorGroups) | ||
- Ensure the Advanced Audience Targeting integration is configured in your Optimizely Products so that you can access your connected audiences from Segment Engage. Documentation: | ||
|
||
- If connecting audiences to **Optimizely Web Experimentation** ensure the user id you map to the Optimizely User ID in the destination mappings area is an identifier available on the browser (client side) | ||
- 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 will allow Optimizely web to properly check audience membership for visitors included in connected Segment Engage audiences. |