From f7c285dbd10e8e6159e4e1b5d74cb6aafd8258fe Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 27 Jun 2025 10:50:34 -0400 Subject: [PATCH 1/2] add info about custom traits/audience interaction --- src/privacy/consent-management/consent-in-unify.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/privacy/consent-management/consent-in-unify.md b/src/privacy/consent-management/consent-in-unify.md index bcae9b9169..88901714ea 100644 --- a/src/privacy/consent-management/consent-in-unify.md +++ b/src/privacy/consent-management/consent-in-unify.md @@ -89,6 +89,8 @@ If you use Destination Actions to send consent information to your destinations, ## Storing consent preferences on the Profile Segment stamps consent preference on every Segment event from streaming and Reverse ETL sources to store them on the Profile. +If you're using Consent Management and Profiles, you should not 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 should not give them a custom trait of `segment_consent_preference.categories.marketing`, as this can lead your user to unexpectedly enter or leave an Audience. + > 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. From 7deccfb7617e07a6946737d04c5ca95880b156a6 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 27 Jun 2025 13:33:02 -0400 Subject: [PATCH 2/2] [netlify-build] --- 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 88901714ea..5ed25b9b31 100644 --- a/src/privacy/consent-management/consent-in-unify.md +++ b/src/privacy/consent-management/consent-in-unify.md @@ -83,13 +83,13 @@ In addition to enforcing consent in Connections, you may want these preferences If you use Destination Actions to send consent information to your destinations, the Segment Consent Preference Updated event should **only** include information about a user's consent preferences because this event is sent regardless of an end-user's consent preferences. -> info "Sharing consent with Classic Destinations is not available" +> info "Sharing consent with Classic Destinations isn't available" > Segment only supports sharing consent with Actions Destinations. ## Storing consent preferences on the Profile Segment stamps consent preference on every Segment event from streaming and Reverse ETL sources to store them on the Profile. -If you're using Consent Management and Profiles, you should not 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 should not give them a custom trait of `segment_consent_preference.categories.marketing`, as this can lead your user to unexpectedly enter or leave an Audience. +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.`, as this can lead your user to unexpectedly enter or leave an Audience. > 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.