Skip to content

Commit 894a823

Browse files
Apply suggestions from code review
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
1 parent 365a724 commit 894a823

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,13 +96,13 @@ If you're using Consent Management and Profiles, you shouldn't give your custome
9696
9797
### Backfill consent preferences on your Profiles
9898

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.
99+
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.
100100

101101
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.
102102

103103
## Consent preference conflicts
104104

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)).
105+
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)).
106106

107107

108108
### Device-level conflicts

0 commit comments

Comments
 (0)