Optimizely Data Platform Destination
Sync your Twilio Segment customer data to Optimizely Data Platform (ODP) for real-time segmentation, reporting, and to enrich customer profiles in ODP.
After you set up your Optimizely Data Platform destination, Segment syncs your customer data to ODP in near real-time.
This destination is maintained by Optimizely. For any issues with the destination, contact Optimizely Support team.
Prerequisites
- Twilio Segment workspace
- ODP or ODP Lite account
Enable the integration
- In ODP, open the App Directory.
- Select the Twilio Segment app.
- Click Install App.
- On the Settings tab, click Generate and copy the displayed token.
- Open the Segment app and navigate to the Destination catalog page.
- Search for and select Optimizely Data Platform.
- Click Add destination and select a source to connect to the Optimizely Data Platform destination.
- Enter a name for your destination and click Create destination.
- On the destination’s Settings tab, enter the following information:
- Api Key – Paste your ODP API token from step 4
- Region – Select your region
- Enable Destination – Toggle to On
- Click Save Changes.
Configure event mappings
After you enable the Optimizely Data Platform destination, you must map the events that you want Twilio Segment to send to ODP.
In Twilio Segment, on the Mappings tab of the Optimizely Data Platform destination, Segment displays a list of pre-built mappings that you can enable or disable. For example, if you enabled the Email Opened mapping, each email opened event Segment ingested after you enabled the mapping would sync to ODP.
If you want to map an event that is not listed:
- Click New Mapping > Custom Event.
- (Optional): Enter a descriptive name for the event.
- Select the event that you want to send to ODP.
- Click Load Test Event from Source. This generates the raw data for the selected event and populates your mappings. The ID and timestamp field mappings auto-populate, but you can edit them as desired.
- Select the event type and, optionally, the event action. For example, if you are configuring a custom event to track button clicks, select button for the event type and click for the event action.
Required fields
In ODP, each event requires an ID, timestamp, and event type. The event action is optional. See ODP’s Events documentation for more details.
-
(Optional): To ensure the custom event is configured correctly, click Send test event to destination.
-
Click Save.
-
Toggle your custom event’s status to Enabled.
The event data sends from Twilio Segment to ODP starting after you enable the mapping in the destination. It does not retroactively send events that occurred prior to configuring the integration and enabling the mappings.
Destination Settings
Setting | Description |
---|---|
Api Key | Required. Api Key used for Optimizely API authorization when sending events |
Region | Required. Optimizely Region to sync data to. Default is US |
Available Presets
Optimizely Data Platform has the following presets:
Preset Name | Trigger | Default Action |
---|---|---|
Email Sent | Event type = "track" and event = "Email Sent" |
Email Event |
Product Removed | Event type = "track" and event = "Product Removed" |
Ecommerce Event |
Email Marked as Spam | Event type = "track" and event = "Email Marked as Spam" |
Email Event |
Product Added | Event type = "track" and event = "Product Added" |
Ecommerce Event |
Email Opened | Event type = "track" and event = "Email Opened" |
Email Event |
Product Viewed | Event type = "track" and event = "Product Viewed" |
Ecommerce Event |
Email Link Clicked | Event type = "track" and event = "Email Link Clicked" |
Email Event |
Order Completed | Event type = "track" and event = "Order Completed" |
Ecommerce Event |
Unsubscribed | Event type = "track" and event = "Unsubscribed" |
Email Event |
Available Actions
Build your own Mappings. Combine supported triggers with the following Optimizely Data Platform-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Upsert Contact
Send user profile data from Segment to Optimizely Data Platform. Creates or updates a user profile in Optimzely Data Platform
Upsert Contact is a Cloud action. The default Trigger is: type = "identify"
Field | Description |
---|---|
User identifiers* | Type: OBJECT User identifier details to send to Optimizely. |
Company Name | Type: STRING The name of the company associated with the Contact |
Title | Type: STRING The Contact’s Title |
Name | Type: STRING Contact’s full name |
First Name | Type: STRING Contact’s first name |
Last Name | Type: STRING Contact’s last name |
Gender | Type: STRING Contact’s gender |
Birthday | Type: DATETIME Contact’s birthday. The format should be datetime |
Phone | Type: STRING Contact’s phone number. |
Age | Type: NUMBER Contact’s age. |
Address | Type: OBJECT Address details object |
avatar | Type: STRING The user’s avatar image URL. |
Addition User Traits | Type: OBJECT Additional user profile details |
Email Event
Send email related Segment track() events to Optimizely Data Platform
Email Event is a Cloud action.
Field | Description |
---|---|
User identifiers* | Type: OBJECT User identifier details to send to Optimizely. |
Optimizely Event Action* | Type: STRING The name of the Optimizely Event Action. |
Campaign Name* | Type: STRING The campaign name |
Campaign ID | Type: STRING The campaign unique identifier |
Link URL | Type: STRING URL of the link which was clicked |
Timestamp* | Type: STRING Event timestamp |
Ecommerce Event
Send Segment Ecommerce track() events to Optimizely Data Platform
Ecommerce Event is a Cloud action.
Field | Description |
---|---|
User identifiers* | Type: OBJECT User identifier details to send to Optimizely. |
Optimizely Event Type | Type: STRING The Optimizely Event Type. Defaults to “custom” if not provided |
Optimizely Event Action* | Type: STRING The name of the Optimizely Event Action. |
Product details | Type: OBJECT Product details to associate with the event. Product ID field is required for each product |
Order ID | Type: STRING Identifier for the order |
Order Total | Type: STRING Total value of the order |
Timestamp* | Type: STRING Event timestamp |
Custom Event
Send Segment custom track() events to Optimizely Data Platform
Custom Event is a Cloud action.
Field | Description |
---|---|
User identifiers* | Type: OBJECT User identifier details to send to Optimizely. |
Optimizely Event Type | Type: STRING The Optimizely Event Type. Defaults to “custom” if not provided |
Optimizely Event Action | Type: STRING The name of the Optimizely Event Action. |
Event Properties | Type: OBJECT Additional information to send with your custom event |
Timestamp* | Type: STRING Event timestamp |
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 Data Platform 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 , defaults to US. Optimizely Region to sync data to. Default is US |
This page was last modified: 05 Apr 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!