Skip to content

Commit 365a724

Browse files
committed
Update consent-in-unify.md
1 parent 444e384 commit 365a724

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

src/privacy/consent-management/consent-in-unify.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,17 @@ If you're using Consent Management and Profiles, you shouldn't give your custome
9494
> warning "Storing consent on the Profile is in private beta"
9595
> Reach out to your sales contact or [request a demo](https://segment.com/contact/demo){:target="_blank"} to participate in the private beta.
9696
97+
### Backfill consent preferences on your Profiles
98+
99+
If you've stored end-user consent preferences in your warehouse and would like to make them available to your Profiles, you can use [Reverse ETL](/docs/privacy/consent-management/consent-in-retl/) and [Segment Profiles](/docs/connections/destinations/catalog/actions-segment-profiles/) to extract the consent information from your warehouse and load the information into Segment.
100+
101+
If you want to use end-user consent coming directly from your single source of truth, you can generate an Identify, Track, or [Segment Consent Preferences Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) Track event to add [consent information to the `context` object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object). For more information about the requirements for data collection, see the [Configure Consent Management](/docs/privacy/consent-management/configure-consent-management/#step-2-integrating-your-cmp-with-segment) documentation.
102+
103+
## Consent preference conflicts
104+
105+
When collecting end user consent, you can occasionally capture multiple consent preferences linked to the same user, for example, from a user's cell phone browser and the web browser on their laptop (called a [device-level conflict](#device-level-conflict)) or when two distinct Unify profiles are merged together (called a [profile-level conflict](#profile-level-conflict)).
106+
107+
97108
### Device-level conflicts
98109
A device-level conflict occurs when conflicting consent preferences linked to one user ID are collected from two distinct devices.
99110

0 commit comments

Comments
 (0)