|
| 1 | +--- |
| 2 | +title: Optimizely Data Platform Destination |
| 3 | +--- |
| 4 | + |
| 5 | +Sync your Twilio Segment customer data to Optimizely Data Platform (ODP) for real-time segmentation, reporting, and to enrich customer profiles in ODP. |
| 6 | + |
| 7 | +After you complete the setup below, this integration syncs your Twilio Segment customer data to ODP in near real-time. |
| 8 | + |
| 9 | +Prerequisites |
| 10 | +------------- |
| 11 | + |
| 12 | +* Twilio Segment account |
| 13 | +* ODP or [ODP Lite](https://support.optimizely.com/hc/en-us/articles/8359093735309-Welcome-to-ODP-Lite) account |
| 14 | + |
| 15 | +Enable the integration |
| 16 | +---------------------- |
| 17 | + |
| 18 | +1. In ODP, go to the **App Directory**. |
| 19 | +2. Select the **Twilio Segment** app. |
| 20 | +3. Click **Install App**. |
| 21 | +4. On the **Settings** tab, click **Generate** and copy the token that displays. |
| 22 | +5. In Twilio Segment, go to **Connections > Destinations**. |
| 23 | +6. Search for and select **Optimizely Data Platform**. |
| 24 | +7. Complete the following fields on the **Settings** tab: |
| 25 | + - **Name** – Enter a name for the destination, like _Optimizely Data Platform_. |
| 26 | + - **Api Key** – Paste your ODP API token from step 4. |
| 27 | + - **Region** – Select your region. |
| 28 | + - **Enable Destination** – Toggle to **On**. |
| 29 | +8. Click **Save Changes**. |
| 30 | + |
| 31 | +Configure the event mappings |
| 32 | +---------------------------- |
| 33 | +After you enable the integration, you must map the events that you want Twilio Segment to send to ODP. |
| 34 | + |
| 35 | +In Twilio Segment, on the **Mappings** tab of the Optimizely Data Platform destination, there is a list of pre-built mappings that you can enable or disable. For example, if you enable the **Email Opened** mapping, each email opened event syncs from Twilio Segment to ODP going forward. |
| 36 | + |
| 37 | +If you want to map an event that is not listed: |
| 38 | +1. Click **New Mapping > Custom Event**. |
| 39 | +2. (Optional) Enter a descriptive name for the event. |
| 40 | +3. In section 1, select the event that you want to send to ODP. |
| 41 | +4. In section 2, click **Load Test Event from Source**. This generates the raw data for the selected event and populates the mappings in section 3. |
| 42 | +5. In section 3, the ID and timestamp field mappings auto-populate, but you can edit them as desired. Ensure you 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. |
| 43 | + > 📘 Note |
| 44 | + > |
| 45 | + > In ODP, each event requires an ID, timestamp, and event type. The event action is optional. See [Events](https://docs.developers.optimizely.com/optimizely-data-platform/docs/thebasics-events) in the ODP documentation. |
| 46 | +6. (Optional) To ensure the custom event is configured correctly, in section 4, click **Send test event to destination**. |
| 47 | +7. Click Save. |
| 48 | +8. Toggle the **Status** to **Enabled** for the custom event you created. |
| 49 | + |
| 50 | +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. |
| 51 | + |
0 commit comments