Integration steps
- Collect consent at the edge — OneTrust captures the visitor's choices on the site or app.
- Send the signal — pass consent to AEP, usually through Web SDK and a datastream.
- Store it in a schema — yes, you need a consent field (for example a consent and preferences field group) in a profile schema.
- Enforce it — enable data usage and consent policies so segmentation and activation respect the values.
- Keep it current — update the profile whenever preferences change.
Consent vs governance labels
| Consent | Governance labels | |
|---|---|---|
| What it describes | A person's permission | The sensitivity and contract terms of data |
| Where it lives | Profile attribute per person | Schema, dataset or field labels |
| When it is applied | Ingested first; enforced at segmentation and activation | At schema or dataset level, before or during ingestion |
Common mistakes
- Adding consent at the end of the project instead of during schema design
- Applying governance labels after data has already been activated
- Forgetting that downstream custom actions and integrations must also respect consent
Frequently asked questions
Do I need a new schema for consent?
You need a consent field in a profile schema; it can be added to an existing schema through a field group.
When should governance labels be applied?
At schema or dataset level, before or during ingestion - not after the data has been used.
Last updated: