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

1. In ODP, open the App Directory.
2. Select the Twilio Segment app.
3. Click Install App.
4. On the Settings tab, click Generate and copy the displayed token.
5. Open the Segment app and navigate to the Destination catalog page.
6. Search for and select Optimizely Data Platform.
7. Click Add destination and select a source to connect to the Optimizely Data Platform destination.
8. Enter a name for your destination and click Create destination.
9. 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
10. 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:

1. Click New Mapping > Custom Event.
2. (Optional): Enter a descriptive name for the event.
3. Select the event that you want to send to ODP.
4. 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.
5. 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.

6. (Optional): To ensure the custom event is configured correctly, click Send test event to destination.

7. Click Save.

8. 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

Available Presets

Optimizely Data Platform has the following presets:

Available Actions

Build your own Mappings. Combine supported triggers with the following Optimizely Data Platform-supported actions:

• Upsert Contact

• Email Event

• Ecommerce Event

• Custom Event

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"

Click to show / hide fields

Email Event

Send email related Segment track() events to Optimizely Data Platform

Email Event is a Cloud action.

Click to show / hide fields

Ecommerce Event

Send Segment Ecommerce track() events to Optimizely Data Platform

Ecommerce Event is a Cloud action.

Click to show / hide fields

Custom Event

Send Segment custom track() events to Optimizely Data Platform

Custom Event is a Cloud action.

Click to show / hide fields

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.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.