Question
Why are Consent Traits showing on an Engage profile, and where does this data originate from within Segment?
Product
Twilio Segment
Environment
Segment Console
Answer
The Consent Traits visible on an Engage user profile are not generated by Engage itself; instead, they are extracted from the incoming categoryPreferences object within the event payloads (such as identify, track, or page calls) landing in your connected sources.
When an event call containing consent data is processed, Segment parses the payload and maps those preferences directly to the customer's profile traits in Unify/Engage.
Example Walkthrough
1. In the Source Debugger
When a user updates their privacy settings, an event call is sent to Segment containing a consent object under the context field, structured like this:
2. On the Engage User Profile
Once processed, Engage reads that categoryPreferences data and displays it dynamically under the Consent Traits section of that specific user's profile:
Additional Information
To ensure your consent data updates successfully on profiles, confirm that your Consent Management Platform (CMP) wrapper is properly appending the structured
categoryPreferencesobject to your event calls.For a deeper dive into data structures, see the Segment Consent Management Documentation.