|
| 1 | +--- |
| 2 | +title: OneTrust Source |
| 3 | +id: QhEUZnE5uF |
| 4 | +beta: true |
| 5 | +hidden: true |
| 6 | +--- |
| 7 | + |
| 8 | +OneTrust makes it easy for you to capture, centralize, govern, and sync consented first party data while keeping trust & transparency at the forefront of all consumer interactions. The OneTrust Integration provides data to Segment’s CDP and allows you to view & activate consented data in the appropriate way. |
| 9 | + |
| 10 | +This is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations. |
| 11 | + |
| 12 | +This source is maintained by OneTrust. For any issues with the source, [contact their support team ]([email protected]). |
| 13 | + |
| 14 | +## Getting Started |
| 15 | + |
| 16 | +1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog) click **Add Source**. |
| 17 | + |
| 18 | +2. Search for “OneTrust” in the Sources Catalog, select MoEOneTrustngage, and click **Add Source**. |
| 19 | + |
| 20 | +3. On the next screen, give the Source **a nickname** configure any other settings. |
| 21 | + - The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (like `OneTrust_Prod`, `OneTrust_Staging`, or `OneTrust_Dev`). |
| 22 | + |
| 23 | +4. Copy the **Write key** from the Segment UI and log in to your OneTrust account - navigate to Settings > Integrations > Segment Integration and paste the key after encoding it. |
| 24 | + |
| 25 | +## Stream |
| 26 | + |
| 27 | +OneTrust uses Segment's stream Source component to send Segment event data. It uses a server-side method(s) to send data to Segment. These events are then available in any destination that accepts server-side events and are available in a schema in your data warehouse, so you can query using SQL. |
| 28 | + |
| 29 | +OneTrust allows you to configure the userId from various sources from within the OneTrust platform. |
| 30 | + |
| 31 | +## Events |
| 32 | + |
| 33 | +Use the OneTrust integration to define the events to be sent to Segment These events can be tailored to align with your existing process or particular use case. |
| 34 | + |
| 35 | +## Event Properties |
| 36 | + |
| 37 | +The OneTrust integration allows you to define event properties within the following constraints: |
| 38 | + |
| 39 | +- Use `Track` events to define the `properties` object |
| 40 | +- Use `Identify` events to define the `traits` object |
| 41 | + |
| 42 | + |
| 43 | +## Adding Destinations |
| 44 | + |
| 45 | +Now that your Source is set up, you can connect it with Destinations. |
| 46 | + |
| 47 | +Log into your downstream tools and verify that events and properties appear the way you expect. If events and properties don’t appear as you expect them to, check the [Event Delivery](https://segment.com/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting. |
| 48 | + |
| 49 | +If there are any issues with how the events are arriving to Segment, [contact the OneTrust support team ]([email protected]). |
0 commit comments