Consent in Unify

Segment uses Profiles in Unify as the source of truth of an end user’s consent preference when enforcing consent in Twilio Engage. To get consent preference on the Profile, Segment requires the use of the Segment Consent Preference event and Identify events to route events to Unify. The Segment Consent Preference and Identify event should include the consent object.

Segment Consent Preference event

Every time an end user provides or updates their consent preferences, Segment requires you to generate a Segment Consent Preference event. If you are using Segment’s OneTrust consent wrappers, Segment automatically generates a Segment Consent Preference event. This event is required to add the end user’s consent preference on their Profile in Unify.

For example, if an end user agreed to share their information for functional and advertising purposes but not for analytics or data sharing, the Segment Consent Preference Track call demonstrating their new consent preferences would have the following format:

{
  "anonymousId": "23adfd82-aa0f-45a7-a756-24f2a7a4c895",
  "type": "track",
  "event": "Segment Consent Preference",
  "userId": "u123",
  "traits": {
     "email": "peter@example.com",
     "phone": "555-555-5555",
  }
  "timestamp": "2023-01-01T00:00:00.000Z",
  "context": {
    "consent": {
      "categoryPreferences" : {
        "Advertising": true,
        "Analytics": false,
        "Functional": true,
        "DataSharing": false
      }
    }
  }
}

If you use Protocols, the Segment app automatically adds the Segment Consent Preference event to all your existing Tracking Plans and for every new Tracking Plan. Segment recommends you don’t edit or delete the default fields in the Segment Consent Preference events, but you can add new fields as needed.