From 365a724b0be9952671d0931bf8ed972457d11f2d Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 11 Aug 2025 14:07:51 -0400 Subject: [PATCH 1/2] Update consent-in-unify.md --- src/privacy/consent-management/consent-in-unify.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/privacy/consent-management/consent-in-unify.md b/src/privacy/consent-management/consent-in-unify.md index 5ed25b9b31..a907bb9617 100644 --- a/src/privacy/consent-management/consent-in-unify.md +++ b/src/privacy/consent-management/consent-in-unify.md @@ -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. + +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)). + + ### Device-level conflicts A device-level conflict occurs when conflicting consent preferences linked to one user ID are collected from two distinct devices. From 894a82334f374ba3cea8a293b8da341ddc85b787 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 14 Aug 2025 13:43:28 -0400 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- src/privacy/consent-management/consent-in-unify.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/privacy/consent-management/consent-in-unify.md b/src/privacy/consent-management/consent-in-unify.md index a907bb9617..426576c265 100644 --- a/src/privacy/consent-management/consent-in-unify.md +++ b/src/privacy/consent-management/consent-in-unify.md @@ -96,13 +96,13 @@ If you're using Consent Management and Profiles, you shouldn't give your custome ### 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. +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)). +When collecting end user consent, you can occasionally capture multiple consent preferences linked to the same user. For example, you might collect consent from a user's cell phone browser and the web browser on their laptop (called a [device-level conflict](#device-level-conflict)) or merge two distinct Unify profiles together (called a [profile-level conflict](#profile-level-conflict)). ### Device-level conflicts