Skip to content

Commit df456b7

Browse files
committed
[netlify-build]
1 parent c2f0bdb commit df456b7

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
@@ -4,7 +4,7 @@ plan: consent-management
44
redirect_from: "/privacy/consent-in-unify"
55
---
66

7-
Segment uses the [consent object](#consent-object) on Segment events, including the [Segment Consent Preference Updated](#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on the Profile. Consent on the Profiles serves as the source of truth of an end user’s consent preference when enforcing consent in Twilio Engage or Linked Audiences.
7+
Segment uses the [consent object](#consent-object) on Segment events, including the [Segment Consent Preference Updated](#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on the Profile. Consent on the Profiles serves as the source of truth of an end user’s consent preference when enforcing consent in Twilio Engage.
88

99
## Consent object
1010

@@ -90,7 +90,7 @@ If you use Destination Actions to send consent information to your destinations,
9090
Segment stamps consent preference on every Segment event from streaming and Reverse ETL sources as a trait to store them on the Profile.
9191

9292
> info "Storing consent on the Profile is in public beta"
93-
> Consent in Unify is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
93+
> Storing consent preferences on a Unify Profile is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
9494
9595
If you're using Consent Management and Profiles, you shouldn't give your customers a Custom Trait value that matches one of the consent categories that you set up in the Segment app, as this can lead to unexpected Audience behavior. For example, if your end user consented to the "Marketing" destination category, you shouldn't give them a custom trait of `segment_consent_preference.categories.marketing.<value>`, as this can lead your user to unexpectedly enter or leave an Audience.
9696

0 commit comments

Comments
 (0)