Skip to content

Backfill consent preferences on the Profile docs #7827

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Backfill consent preferences on the Profile docs #7827

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/privacy/consent-management/consent-in-unify.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,17 @@ If you're using Consent Management and Profiles, you shouldn't give your custome
> warning "Storing consent on the Profile is in private beta"
> Reach out to your sales contact or [request a demo](https://segment.com/contact/demo){:target="_blank"} to participate in the private beta.

### Backfill consent preferences on your Profiles

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
If you've stored end-user consent preferences in your warehouse and would like to make them available to your Profiles, 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.


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.

## Consent preference conflicts

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)).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a really long sentence. Is there a way to shorten it or break it up into multiple sentences?



### Device-level conflicts
A device-level conflict occurs when conflicting consent preferences linked to one user ID are collected from two distinct devices.

Expand Down