From c2fe446c05c27a86056e98cf97c5bc8deba77f68 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 17 Jun 2025 11:20:25 -0400 Subject: [PATCH 01/18] Create consent-in-engage.md --- .../consent-management/consent-in-engage.md | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 src/privacy/consent-management/consent-in-engage.md diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md new file mode 100644 index 0000000000..ddf45a39cb --- /dev/null +++ b/src/privacy/consent-management/consent-in-engage.md @@ -0,0 +1,46 @@ +--- +title: Consent in Twilio Engage +plan: consent-management +--- + +Segment uses the [consent object](/docs/privacy/consent-in-unify/#segment-consent-preference-event) on Segment events, including the [Segment Consent Preference Updated](/docs/privacy/consent-in-unify/#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on an end user's Profile. + +Once an end user's consent preferences are stored on their Profile, you can create Audiences that respect end user consent preferences to better comply with privacy regulations. + +> 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. + +## Enforce consent preferences in your Audience + +### Prerequisites + +Before using an end user's consent preferences to create your Audiences, you must complete the following prerequisites: +- + +### Step 1: Enable consent in your Unify space + +### Step 2: Create your Audience + +> info "Consent preferences can affect Audience sync size" +> The number of profiles that sync to your Audience depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. + + +## Verify that your Audiences respect consent preferences + +After you've enabled consent management in your Unify space and created a new audience, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. + +However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or check Delivery Overview for a "filtered at destination" event. + +### Compare an end user profile to your mapped categories +To verify that your end user's consent preferences match the category that you mapped to your destination: + +1. Navigate to the connected destination and select an end user profile. +2. Return to Segment and compare the consent preferences of that profile against the consent category of the connected destination. +3. Verify that the consent preferences of your selected user match the consent category that you mapped to your destination. + +### Use Delivery Overview + +You can use Delivery Overview to verify that your destination is enforcing your user's consent preferences. + +To + From e68a330f95044ee8548c89bc0eb089dca19a0381 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 11 Jul 2025 15:45:57 -0400 Subject: [PATCH 02/18] first pass --- .../consent-management/consent-in-engage.md | 58 ++++++++++++++----- .../consent-management/consent-in-unify.md | 20 ++++--- src/privacy/consent-management/index.md | 4 +- 3 files changed, 61 insertions(+), 21 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index ddf45a39cb..a447c4d8b3 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -1,35 +1,63 @@ --- -title: Consent in Twilio Engage +title: Consent in Engage Audiences plan: consent-management --- Segment uses the [consent object](/docs/privacy/consent-in-unify/#segment-consent-preference-event) on Segment events, including the [Segment Consent Preference Updated](/docs/privacy/consent-in-unify/#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on an end user's Profile. -Once an end user's consent preferences are stored on their Profile, you can create Audiences that respect end user consent preferences to better comply with privacy regulations. +Once an end user's consent preferences are stored on their Profile, you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. -> 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. +> warning "Consent in Engage Audiences is in public beta" +> Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. +> +> During the public beta, only Profiles Audiences are supported by Consent in Engage Audiences. -## Enforce consent preferences in your Audience - -### Prerequisites +## Enforce consent preferences in your Audiences Before using an end user's consent preferences to create your Audiences, you must complete the following prerequisites: -- +- You've previously set up [Consent in Segment Connections](/docs/privacy/consent-management/consent-in-segment-connections) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. +- You've previously set up [Consent in Unify](/docs/privacy/consent-management/consent-in-unify) and stamped all of your Profiles with end user consent preferences. ### Step 1: Enable consent in your Unify space +Once your consent categories are set up and mapped and each of your Profiles is stamped with the consent object, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like to enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment will continue to stamp consent preferences on your Profiles. + +> info "" +> In order to enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). + +To enable Consent Management in your Unify space: +1. Navigate to Unify and select the space where you'd like to enable Consent Management. +2. Select **Unify settings** and navigate to the **Space management** tab. +3. Select the **Consent management** setting and enable the toggle to turn on Consent Management for your Unify space. +4. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. + +After you've enabled Consent Management in your Unify space, you can create an Audience that only includes users that have consented to the use of their data for a particular purpose. + +> warning "Consent enforcement is not automatically applied to Audiences that existed prior to the enablement of Consent Management in your Unify space" +> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter an Audience after you enable Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync: only Profiles that consented to the category mapped to your destination will re-enter the Audience and be sent downstream to your destination. All Audiences created after you enable Consent Management for a space only contain Profiles that consented to the use of their data for the mapped destination. + + ### Step 2: Create your Audience -> info "Consent preferences can affect Audience sync size" -> The number of profiles that sync to your Audience depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. +> info "Consent preferences can affect Audience sync size" +> The number of profiles that sync to your Audience depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. To see the impact of consent on your Audience, add consent traits to the Audience builder. + +During the public beta, you can create Profiles Audiences from your users' consent preferences. + +To create a Profiles Audience that includes consent traits: +1. Navigate to **Engage > Audiences** and click **+ New audience**, then select **Audience**. +2. On the Select Audience Type screen, select **Profiles audience** then click **Next**. +3. Add a condition and select **Have a consent trait**, then select your intended consent category, operator, and true/false value. +4. Continue building your Audience, adding additional conditions as you see fit. When you're satisfied with your Audience conditions, click **Next**. +5. Select one or more destinations that you'd like to receive your Audience. +Destinations mapped to a consent category only receive the Profiles of users that have consented to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. If opt to send your Audience to multiple destinations belonging to multiple categories then each destination receives data for the Profiles that have consent to the destination’s mapped category. For example, if you have an audience mapped to Google Ads (mapped to the Ads consent category) and Snowflake (mapped to the Analytics consent category), then Google Ads receives all profiles that have consent to Ads independent of users consent preferences to Analytics, and Snowflake receives all profiles that have consented to Analytics independent of their Ads preferences. ## Verify that your Audiences respect consent preferences After you've enabled consent management in your Unify space and created a new audience, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. -However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or check Delivery Overview for a "filtered at destination" event. +However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a`FILTERED_BY_END_USER_CONSENT` event. ### Compare an end user profile to your mapped categories To verify that your end user's consent preferences match the category that you mapped to your destination: @@ -40,7 +68,11 @@ To verify that your end user's consent preferences match the category that you m ### Use Delivery Overview -You can use Delivery Overview to verify that your destination is enforcing your user's consent preferences. +You can use Delivery Overview to verify that your destination is enforcing your user's consent preferences by checking for the presence of a `FILTERED_BY_END_USER_CONSENT` discard reason. -To +To verify that your events are being filtered by end user consent: +1. Select the destination connected your Engage Audience. +2. On the Delivery Overview page, select **Filtered at destination**. +3. Search through the table of discarded events until you find an event with a discard reason of `FILTERED_BY_END_USER_CONSENT`. +If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point in your data pipeline where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. If you cannot find a `FILTERED_BY_END_USER_CONSENT` discard reason, either wait a few minutes for more events to flow to your destination before reviewing the discard reasons again or revisit the consent settings for your Unify space. diff --git a/src/privacy/consent-management/consent-in-unify.md b/src/privacy/consent-management/consent-in-unify.md index bcae9b9169..25becf6dfc 100644 --- a/src/privacy/consent-management/consent-in-unify.md +++ b/src/privacy/consent-management/consent-in-unify.md @@ -77,20 +77,26 @@ If you use Protocols, the Segment app automatically adds the Segment Consent Pre > > See the [Semantic Events](/docs/connections/spec/semantic/) docs for more details. -### Sharing consent with Actions destinations +### Share consent with Actions destinations In addition to enforcing consent in Connections, you may want these preferences to flow to each destination so your destinations can be aware when an end-user revokes their consent. You can use the [Destination Actions framework](/docs/connections/destinations/actions) to edit the destination's mapping and copy the consent preferences from the Segment Consent Preference Updated event to a destination-specified consent field. 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" +> warning "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. +## Store consent preferences on the Profile +Segment stamps consent preference on every Segment event from streaming and Reverse ETL sources as a trait to store them on the Profile. -> 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. +> info "Storing consent on the Profile is in public beta" +> Consent in Unify is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. + +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. + +## 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. @@ -128,7 +134,7 @@ To avoid Profile-level conflicts, Segment recommends that you take the following > Profile conflicts only impact Profiles used in Engage spaces. ## Enforcing consent in Twilio Engage -Segment stores consent preferences as traits on the Profile, which you can use to [build Audiences](/docs/engage/audiences/#building-an-audience). +Segment stores consent preferences as traits on the Profile, which you can use to [build Audiences](/docs/privacy/consent-management/consent-in-engage). ## Validating consent preferences stored on a Profile You can validate consent is present on the Profile by looking for the consent trait provided for a Profile on the consent tab. diff --git a/src/privacy/consent-management/index.md b/src/privacy/consent-management/index.md index 7f8c3698e2..ba10f23938 100644 --- a/src/privacy/consent-management/index.md +++ b/src/privacy/consent-management/index.md @@ -18,4 +18,6 @@ The events, stamped with the consent object, are then sent downstream to any des For more information about consent in Segment Connections, see the [Consent in Segment Connections](/docs/privacy/consent-management/consent-in-segment-connections) documentation. -If you are a Unify user, you can also see the [Consent in Unify](/docs/privacy/consent-management/consent-in-unify) for more information about the Segment Consent Preference Updated event, which Segment uses to add consent preference to the Profile. +If you are a Unify user, you can also see [Consent in Unify](/docs/privacy/consent-management/consent-in-unify) for more information about the Segment Consent Preference Updated event, which Segment uses to add consent preference to the Profile. + +Twilio Engage users can learn more about creating Audiences that respect end-user consent preferences in the [Consent in Twilio Engage](/docs/privacy/consent-management/consent-in-engage) documentation. From 85903193b8d5c36ba7b6bb128fed50dab0afc98e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 14 Jul 2025 08:14:33 -0400 Subject: [PATCH 03/18] editing pass --- .../consent-management/consent-in-engage.md | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index a447c4d8b3..509454c158 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -16,11 +16,11 @@ Once an end user's consent preferences are stored on their Profile, you can crea Before using an end user's consent preferences to create your Audiences, you must complete the following prerequisites: - You've previously set up [Consent in Segment Connections](/docs/privacy/consent-management/consent-in-segment-connections) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. -- You've previously set up [Consent in Unify](/docs/privacy/consent-management/consent-in-unify) and stamped all of your Profiles with end user consent preferences. +- You generate the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event) Track event each time a user updates their consent preferences. This event stamps each Profile with a user's consent preferences. ### Step 1: Enable consent in your Unify space -Once your consent categories are set up and mapped and each of your Profiles is stamped with the consent object, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like to enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment will continue to stamp consent preferences on your Profiles. +Once your consent categories are set up and mapped and each of your Profiles is stamped with the Segment Consent Preference Updated event, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like to enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment will continue to stamp consent preferences on your Profiles. > info "" > In order to enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). @@ -34,7 +34,7 @@ To enable Consent Management in your Unify space: After you've enabled Consent Management in your Unify space, you can create an Audience that only includes users that have consented to the use of their data for a particular purpose. > warning "Consent enforcement is not automatically applied to Audiences that existed prior to the enablement of Consent Management in your Unify space" -> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter an Audience after you enable Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync: only Profiles that consented to the category mapped to your destination will re-enter the Audience and be sent downstream to your destination. All Audiences created after you enable Consent Management for a space only contain Profiles that consented to the use of their data for the mapped destination. +> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync: only Profiles that consented to the category mapped to your destination will re-enter the Audience and be sent downstream to your destination. All Audiences created after you enable Consent Management for a space only contain Profiles that consented to the use of their data for the mapped destination(s). ### Step 2: Create your Audience @@ -51,19 +51,19 @@ To create a Profiles Audience that includes consent traits: 4. Continue building your Audience, adding additional conditions as you see fit. When you're satisfied with your Audience conditions, click **Next**. 5. Select one or more destinations that you'd like to receive your Audience. -Destinations mapped to a consent category only receive the Profiles of users that have consented to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. If opt to send your Audience to multiple destinations belonging to multiple categories then each destination receives data for the Profiles that have consent to the destination’s mapped category. For example, if you have an audience mapped to Google Ads (mapped to the Ads consent category) and Snowflake (mapped to the Analytics consent category), then Google Ads receives all profiles that have consent to Ads independent of users consent preferences to Analytics, and Snowflake receives all profiles that have consented to Analytics independent of their Ads preferences. +Destinations mapped to a consent category only receive the Profiles of users that have consented to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. If opt to send your Audience to multiple destinations belonging to multiple categories, then each destination receives data for the Profiles that have consent to the destination’s mapped category. For example, if you have an audience mapped to Google Ads (mapped to the Advertising consent category) and Snowflake (mapped to the Analytics consent category), then Google Ads receives all profiles that have consented to Advertising consent category, independent of users' who consented to Analytics, and Snowflake receives all profiles that have consented to Analytics, independent of their Advertising preferences. ## Verify that your Audiences respect consent preferences -After you've enabled consent management in your Unify space and created a new audience, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. +After you've enabled consent management in your Unify space and created a new audience with a consent trait, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. -However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a`FILTERED_BY_END_USER_CONSENT` event. +However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a `FILTERED_BY_END_USER_CONSENT` event. -### Compare an end user profile to your mapped categories -To verify that your end user's consent preferences match the category that you mapped to your destination: +### Compare an end user Profile to your mapped categories -1. Navigate to the connected destination and select an end user profile. -2. Return to Segment and compare the consent preferences of that profile against the consent category of the connected destination. +To verify that your end user's consent preferences match the category that you mapped to your destination: +1. Navigate to the connected destination and select a Profile. +2. Return to Segment and compare the consent preferences of that Profile against the consent category of the connected destination. 3. Verify that the consent preferences of your selected user match the consent category that you mapped to your destination. ### Use Delivery Overview @@ -71,8 +71,8 @@ To verify that your end user's consent preferences match the category that you m You can use Delivery Overview to verify that your destination is enforcing your user's consent preferences by checking for the presence of a `FILTERED_BY_END_USER_CONSENT` discard reason. To verify that your events are being filtered by end user consent: -1. Select the destination connected your Engage Audience. +1. Select the destination connected to your Engage Audience. 2. On the Delivery Overview page, select **Filtered at destination**. 3. Search through the table of discarded events until you find an event with a discard reason of `FILTERED_BY_END_USER_CONSENT`. -If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point in your data pipeline where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. If you cannot find a `FILTERED_BY_END_USER_CONSENT` discard reason, either wait a few minutes for more events to flow to your destination before reviewing the discard reasons again or revisit the consent settings for your Unify space. +If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. If you cannot find a `FILTERED_BY_END_USER_CONSENT` discard reason, either wait a few minutes for more events to flow to your destination before reviewing the discard reasons again or revisit the conditions that you used to generate your Audience. From df456b7a116f1417a19eb66fc0a9c6ea78ef0f58 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 14 Jul 2025 08:19:48 -0400 Subject: [PATCH 04/18] [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 cbd51e0736..c46ebb40e5 100644 --- a/src/privacy/consent-management/consent-in-unify.md +++ b/src/privacy/consent-management/consent-in-unify.md @@ -4,7 +4,7 @@ plan: consent-management redirect_from: "/privacy/consent-in-unify" --- -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. +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. ## Consent object @@ -90,7 +90,7 @@ If you use Destination Actions to send consent information to your destinations, Segment stamps consent preference on every Segment event from streaming and Reverse ETL sources as a trait to store them on the Profile. > info "Storing consent on the Profile is in public beta" -> Consent in Unify is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. +> 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. 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. From d125bcf3665ebd08dcb28dfede120585c50e6e4e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 14 Jul 2025 08:56:12 -0400 Subject: [PATCH 05/18] add to sidebar [netlify-build] --- src/_data/sidenav/main.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index 43d04ab97e..9554a60e4d 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -614,7 +614,9 @@ sections: - path: /privacy/consent-management/consent-in-unify title: Consent Stored on the Profile - path: /privacy/consent-management/consent-in-retl - title: Consent in Reverse ETL + title: Consent in Reverse + - path: /privacy/consent-management/consent-in-engage + title: Consent in Engage Audiences - path: /privacy/consent-management/consent-faq title: Consent FAQs - path: /privacy/data-retention-policy From 73f216835c7690a3f7fc0b66597e6ab860322c73 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 14 Jul 2025 09:15:37 -0400 Subject: [PATCH 06/18] fix [netlify-build] --- src/_data/sidenav/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index 9554a60e4d..319fb119cc 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -614,7 +614,7 @@ sections: - path: /privacy/consent-management/consent-in-unify title: Consent Stored on the Profile - path: /privacy/consent-management/consent-in-retl - title: Consent in Reverse + title: Consent in Reverse ETL - path: /privacy/consent-management/consent-in-engage title: Consent in Engage Audiences - path: /privacy/consent-management/consent-faq From 7cb55bba137c1ab9e7131d1abc679369d3964e37 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 15 Jul 2025 08:57:34 -0400 Subject: [PATCH 07/18] Apply suggestions from code review Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- .../consent-management/consent-in-engage.md | 18 +++++++++++------- .../consent-management/consent-in-unify.md | 2 +- src/privacy/consent-management/index.md | 2 +- 3 files changed, 13 insertions(+), 9 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index 509454c158..3c6c0b5d2e 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -7,7 +7,7 @@ Segment uses the [consent object](/docs/privacy/consent-in-unify/#segment-consen Once an end user's consent preferences are stored on their Profile, you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. -> warning "Consent in Engage Audiences is in public beta" +> info "Consent in Engage Audiences is in public beta" > Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. > > During the public beta, only Profiles Audiences are supported by Consent in Engage Audiences. @@ -20,20 +20,20 @@ Before using an end user's consent preferences to create your Audiences, you mus ### Step 1: Enable consent in your Unify space -Once your consent categories are set up and mapped and each of your Profiles is stamped with the Segment Consent Preference Updated event, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like to enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment will continue to stamp consent preferences on your Profiles. +Once your consent categories are set up and mapped and each of your Profiles is stamped with the Segment Consent Preference Updated event, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like to enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. > info "" > In order to enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). To enable Consent Management in your Unify space: -1. Navigate to Unify and select the space where you'd like to enable Consent Management. +1. Navigate to **Unify** and select the space where you'd like to enable Consent Management. 2. Select **Unify settings** and navigate to the **Space management** tab. 3. Select the **Consent management** setting and enable the toggle to turn on Consent Management for your Unify space. 4. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. After you've enabled Consent Management in your Unify space, you can create an Audience that only includes users that have consented to the use of their data for a particular purpose. -> warning "Consent enforcement is not automatically applied to Audiences that existed prior to the enablement of Consent Management in your Unify space" +> warning "Consent enforcement does not automatically apply to Audiences that existed prior to the enablement of Consent Management in your Unify space" > Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync: only Profiles that consented to the category mapped to your destination will re-enter the Audience and be sent downstream to your destination. All Audiences created after you enable Consent Management for a space only contain Profiles that consented to the use of their data for the mapped destination(s). @@ -51,11 +51,15 @@ To create a Profiles Audience that includes consent traits: 4. Continue building your Audience, adding additional conditions as you see fit. When you're satisfied with your Audience conditions, click **Next**. 5. Select one or more destinations that you'd like to receive your Audience. -Destinations mapped to a consent category only receive the Profiles of users that have consented to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. If opt to send your Audience to multiple destinations belonging to multiple categories, then each destination receives data for the Profiles that have consent to the destination’s mapped category. For example, if you have an audience mapped to Google Ads (mapped to the Advertising consent category) and Snowflake (mapped to the Analytics consent category), then Google Ads receives all profiles that have consented to Advertising consent category, independent of users' who consented to Analytics, and Snowflake receives all profiles that have consented to Analytics, independent of their Advertising preferences. +Destinations mapped to a consent category only receive the Profiles of users who have given consent to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. + +If you opt to send your Audience to multiple destinations belonging to multiple categories, then each destination receives data for the Profiles that have consent to the destination’s mapped category. For example, if you have an audience mapped to Google Ads (mapped to the Advertising consent category) and Snowflake (mapped to the Analytics consent category), then: +* Google Ads receives all profiles that have consented to Advertising consent category, independent of users' who consented to Analytics +* Snowflake receives all profiles that have consented to Analytics, independent of their Advertising preferences. ## Verify that your Audiences respect consent preferences -After you've enabled consent management in your Unify space and created a new audience with a consent trait, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. +After you enable consent management in your Unify space and create a new audience with a consent trait, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a `FILTERED_BY_END_USER_CONSENT` event. @@ -75,4 +79,4 @@ To verify that your events are being filtered by end user consent: 2. On the Delivery Overview page, select **Filtered at destination**. 3. Search through the table of discarded events until you find an event with a discard reason of `FILTERED_BY_END_USER_CONSENT`. -If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. If you cannot find a `FILTERED_BY_END_USER_CONSENT` discard reason, either wait a few minutes for more events to flow to your destination before reviewing the discard reasons again or revisit the conditions that you used to generate your Audience. +If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. If you can't find a `FILTERED_BY_END_USER_CONSENT` discard reason, either wait a few minutes for more events to flow to your destination before reviewing the discard reasons again or revisit the conditions that you used to generate your Audience. diff --git a/src/privacy/consent-management/consent-in-unify.md b/src/privacy/consent-management/consent-in-unify.md index c46ebb40e5..dde6d3a570 100644 --- a/src/privacy/consent-management/consent-in-unify.md +++ b/src/privacy/consent-management/consent-in-unify.md @@ -87,7 +87,7 @@ If you use Destination Actions to send consent information to your destinations, > Segment only supports sharing consent with Actions Destinations. ## Store consent preferences on the Profile -Segment stamps consent preference on every Segment event from streaming and Reverse ETL sources as a trait to store them on the Profile. +Segment stamps consent preferences on every Segment event from streaming and Reverse ETL sources as a trait to store them on the Profile. > info "Storing consent on the Profile is in public beta" > 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. diff --git a/src/privacy/consent-management/index.md b/src/privacy/consent-management/index.md index 15380d2d5b..6c4fd8ea4d 100644 --- a/src/privacy/consent-management/index.md +++ b/src/privacy/consent-management/index.md @@ -24,6 +24,6 @@ The events, stamped with the consent object, are then sent downstream to any des For more information about consent in Segment Connections, see the [Consent in Segment Connections](/docs/privacy/consent-management/consent-in-segment-connections) documentation. -If you are a Unify user, you can also see [Consent in Unify](/docs/privacy/consent-management/consent-in-unify) for more information about the Segment Consent Preference Updated event, which Segment uses to add consent preference to the Profile. +If you're a Unify user, you can also see [Consent in Unify](/docs/privacy/consent-management/consent-in-unify) for more information about the Segment Consent Preference Updated event, which Segment uses to add consent preference to the Profile. Twilio Engage users can learn more about creating Audiences that respect end-user consent preferences in the [Consent in Twilio Engage](/docs/privacy/consent-management/consent-in-engage) documentation. From cf19988913d054eb5e0da4cb11606d4e4efe5418 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 15 Jul 2025 13:54:59 -0400 Subject: [PATCH 08/18] initial draft --- .../consent-management/consent-in-engage.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index 3c6c0b5d2e..47785195a0 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -3,35 +3,36 @@ title: Consent in Engage Audiences plan: consent-management --- -Segment uses the [consent object](/docs/privacy/consent-in-unify/#segment-consent-preference-event) on Segment events, including the [Segment Consent Preference Updated](/docs/privacy/consent-in-unify/#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on an end user's Profile. +Segment uses the [consent object](/docs/privacy/consent-in-unify/#segment-consent-preference-event) on Segment events, including the [Segment Consent Preference Updated](/docs/privacy/consent-in-unify/#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on an [end user's Profile](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event). Once an end user's consent preferences are stored on their Profile, you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. > info "Consent in Engage Audiences is in public beta" > Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. > -> During the public beta, only Profiles Audiences are supported by Consent in Engage Audiences. +> Only Profiles Audiences are supported by Consent in Engage Audiences. Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, and Journeys. ## Enforce consent preferences in your Audiences Before using an end user's consent preferences to create your Audiences, you must complete the following prerequisites: -- You've previously set up [Consent in Segment Connections](/docs/privacy/consent-management/consent-in-segment-connections) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. +- You've previously set up [Consent in Segment Connections](/docs/privacy/consent-management/configure-consent-management) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. - You generate the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event) Track event each time a user updates their consent preferences. This event stamps each Profile with a user's consent preferences. ### Step 1: Enable consent in your Unify space -Once your consent categories are set up and mapped and each of your Profiles is stamped with the Segment Consent Preference Updated event, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like to enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. +Once your consent categories are set up and mapped and each of your Profiles is stamped with your end user's consent preferences, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. If you enable or disable a Unify space, Segment doesn't automatically enforce consent in your Audiences, but continues to store consent preferences on your Profiles. > info "" > In order to enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). To enable Consent Management in your Unify space: -1. Navigate to **Unify** and select the space where you'd like to enable Consent Management. -2. Select **Unify settings** and navigate to the **Space management** tab. -3. Select the **Consent management** setting and enable the toggle to turn on Consent Management for your Unify space. -4. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. +1. Navigate to **Privacy > Consent Management** and select the Settings tab. +2. Enable the toggle under the Status column to turn on Consent Management for your Unify space. +3. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. -After you've enabled Consent Management in your Unify space, you can create an Audience that only includes users that have consented to the use of their data for a particular purpose. +After you’ve enabled Consent Management in your Unify space, you can create an Audience as you normally would and Segment automatically enforces your end users' consent preferences. When Segment enforces consent preferences, allow or block profiles from being sent to downstream Engage destinations based on end-user consent preference for that category. + + > warning "Consent enforcement does not automatically apply to Audiences that existed prior to the enablement of Consent Management in your Unify space" > Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync: only Profiles that consented to the category mapped to your destination will re-enter the Audience and be sent downstream to your destination. All Audiences created after you enable Consent Management for a space only contain Profiles that consented to the use of their data for the mapped destination(s). From f510efbd3890f906c1c12c48ce5074ab51714014 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Jul 2025 10:01:25 -0400 Subject: [PATCH 09/18] addtl updates [netlify-build] --- .../consent-management/consent-in-engage.md | 25 ++++++++----------- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index 47785195a0..e7bceef5d7 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -25,32 +25,27 @@ Once your consent categories are set up and mapped and each of your Profiles is > info "" > In order to enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). +Before you enable consent in your Unify space, you can verify that your Profiles have consent preferences by creating an Audience with a consent trait condition. If the majority of Profiles have consent preferences on them, you're ready to enable consent enforcement in your Unify space. + +If you have Profiles with consent preferences for some, but not all consent categories, Segment adds all categories to a `categoryPreferences` object on an Identify or Track call and considers consent categories without current consent preferences to be `false`. If you have Profiles with no consent preferences, Segment automatically adds an empty `categoryPreferences` object on an Identify or Track call and prevents those Profiles from flowing downstream to your destination. + To enable Consent Management in your Unify space: 1. Navigate to **Privacy > Consent Management** and select the Settings tab. 2. Enable the toggle under the Status column to turn on Consent Management for your Unify space. 3. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. -After you’ve enabled Consent Management in your Unify space, you can create an Audience as you normally would and Segment automatically enforces your end users' consent preferences. When Segment enforces consent preferences, allow or block profiles from being sent to downstream Engage destinations based on end-user consent preference for that category. - - +After you’ve enabled Consent Management in your Unify space, you can create an Audience as you normally would and Segment automatically allows or blocks profiles from flowing to your downstream destinations, based on end-user preferences and your destination mapping. > warning "Consent enforcement does not automatically apply to Audiences that existed prior to the enablement of Consent Management in your Unify space" -> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync: only Profiles that consented to the category mapped to your destination will re-enter the Audience and be sent downstream to your destination. All Audiences created after you enable Consent Management for a space only contain Profiles that consented to the use of their data for the mapped destination(s). +> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync. All Audiences created after you enable Consent Management for a space automatically enforce consent preferences when sharing their data with mapped destination(s). ### Step 2: Create your Audience > info "Consent preferences can affect Audience sync size" -> The number of profiles that sync to your Audience depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. To see the impact of consent on your Audience, add consent traits to the Audience builder. - -During the public beta, you can create Profiles Audiences from your users' consent preferences. +> The number of profiles that sync to your Engage destination(s) depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. To see the impact of consent on your Audience, add consent traits to the Audience builder. -To create a Profiles Audience that includes consent traits: -1. Navigate to **Engage > Audiences** and click **+ New audience**, then select **Audience**. -2. On the Select Audience Type screen, select **Profiles audience** then click **Next**. -3. Add a condition and select **Have a consent trait**, then select your intended consent category, operator, and true/false value. -4. Continue building your Audience, adding additional conditions as you see fit. When you're satisfied with your Audience conditions, click **Next**. -5. Select one or more destinations that you'd like to receive your Audience. +During the public beta, you can create a Profiles Audiences as you normally would and Segment automatically enforces consent in your downstream destinations. If you don't want Segment to automatically enforce consent, disable consent enforcement in your Unify space and manually add the consent trait Audience condition when building your Audiences. Destinations mapped to a consent category only receive the Profiles of users who have given consent to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. @@ -60,7 +55,7 @@ If you opt to send your Audience to multiple destinations belonging to multiple ## Verify that your Audiences respect consent preferences -After you enable consent management in your Unify space and create a new audience with a consent trait, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. +After you enable consent management in your Unify space and create a new audience, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a `FILTERED_BY_END_USER_CONSENT` event. @@ -80,4 +75,4 @@ To verify that your events are being filtered by end user consent: 2. On the Delivery Overview page, select **Filtered at destination**. 3. Search through the table of discarded events until you find an event with a discard reason of `FILTERED_BY_END_USER_CONSENT`. -If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. If you can't find a `FILTERED_BY_END_USER_CONSENT` discard reason, either wait a few minutes for more events to flow to your destination before reviewing the discard reasons again or revisit the conditions that you used to generate your Audience. +If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. From d70e365c1b37e9de3197be8cf1aefe471945dfd4 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Jul 2025 13:19:56 -0400 Subject: [PATCH 10/18] add unsupported destinations [netlify-build] --- src/privacy/consent-management/consent-in-engage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index e7bceef5d7..a53983bcb7 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -10,7 +10,7 @@ Once an end user's consent preferences are stored on their Profile, you can crea > info "Consent in Engage Audiences is in public beta" > Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. > -> Only Profiles Audiences are supported by Consent in Engage Audiences. Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, and Journeys. +> Only Profiles Audiences are supported by Consent in Engage Audiences. Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, and Journeys. Segment does not automatically enforce consent for the [LiveRamp Audiences](/docs/connections/destinations/catalog/actions-liveramp-audiences/) and [The Trade Desk CRM](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/) destinations. ## Enforce consent preferences in your Audiences From 2026da72d72cc1cd4b8cb3a121b76263495d78c3 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 17 Jul 2025 10:42:43 -0400 Subject: [PATCH 11/18] Apply suggestions from code review --- src/privacy/consent-management/consent-in-engage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index a53983bcb7..6ee109d17f 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -10,7 +10,7 @@ Once an end user's consent preferences are stored on their Profile, you can crea > info "Consent in Engage Audiences is in public beta" > Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. > -> Only Profiles Audiences are supported by Consent in Engage Audiences. Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, and Journeys. Segment does not automatically enforce consent for the [LiveRamp Audiences](/docs/connections/destinations/catalog/actions-liveramp-audiences/) and [The Trade Desk CRM](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/) destinations. +> Only Profiles Audiences are supported by Consent in Engage Audiences. Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, Computed Traits, and Journeys. Segment does not automatically enforce consent for the [LiveRamp Audiences](/docs/connections/destinations/catalog/actions-liveramp-audiences/) and [The Trade Desk CRM](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/) destinations. ## Enforce consent preferences in your Audiences @@ -20,7 +20,7 @@ Before using an end user's consent preferences to create your Audiences, you mus ### Step 1: Enable consent in your Unify space -Once your consent categories are set up and mapped and each of your Profiles is stamped with your end user's consent preferences, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. If you enable or disable a Unify space, Segment doesn't automatically enforce consent in your Audiences, but continues to store consent preferences on your Profiles. +Once your consent categories are set up, you've mapped your destinations to a consent category, and each of your Profiles is stamped with your end user's consent preferences, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. If you enable or disable consent enforcement in your Unify space, you are only enabling or disabling automatic consent enforcement in Engage Audiences: Segment will continue to store consent preferences on your Profiles even if you've disabled consent enforcement in your Unify space. > info "" > In order to enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). From 6865b18d1a33095743baa0d3d1d811a13ff68cd4 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 18 Jul 2025 12:07:23 -0400 Subject: [PATCH 12/18] Update src/privacy/consent-management/consent-in-engage.md --- src/privacy/consent-management/consent-in-engage.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index 6ee109d17f..75265b90ae 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -61,10 +61,7 @@ However, if you'd like to confirm that this behavior is working as intended, you ### Compare an end user Profile to your mapped categories -To verify that your end user's consent preferences match the category that you mapped to your destination: -1. Navigate to the connected destination and select a Profile. -2. Return to Segment and compare the consent preferences of that Profile against the consent category of the connected destination. -3. Verify that the consent preferences of your selected user match the consent category that you mapped to your destination. +You can verify that your Audiences are respecting consent preferences by selecting a user Profile, identifying one category they consented to, and confirming that the user's Profile appears in one of the destinations mapped to that category. ### Use Delivery Overview From aab2c6f175c990f0001d2bc51869951fcd20ac58 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 18 Jul 2025 12:08:14 -0400 Subject: [PATCH 13/18] [netlify-build] --- src/privacy/consent-management/consent-in-engage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index 6ee109d17f..7727de904a 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -75,4 +75,4 @@ To verify that your events are being filtered by end user consent: 2. On the Delivery Overview page, select **Filtered at destination**. 3. Search through the table of discarded events until you find an event with a discard reason of `FILTERED_BY_END_USER_CONSENT`. -If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. +If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. \ No newline at end of file From 89ad32e00d268b01d7faca1126ff71d71d52f2c8 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 18 Jul 2025 12:16:05 -0400 Subject: [PATCH 14/18] [netlify-build] --- src/privacy/consent-management/consent-in-engage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index 863f3f3d78..75265b90ae 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -72,4 +72,4 @@ To verify that your events are being filtered by end user consent: 2. On the Delivery Overview page, select **Filtered at destination**. 3. Search through the table of discarded events until you find an event with a discard reason of `FILTERED_BY_END_USER_CONSENT`. -If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. \ No newline at end of file +If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. From f6b54b96378cf2dbe2b897848c9848702e4b00bc Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 18 Jul 2025 13:39:45 -0400 Subject: [PATCH 15/18] reorganize content [netlify-build] --- .../consent-management/consent-in-engage.md | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index 75265b90ae..c404fcf420 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -5,7 +5,7 @@ plan: consent-management Segment uses the [consent object](/docs/privacy/consent-in-unify/#segment-consent-preference-event) on Segment events, including the [Segment Consent Preference Updated](/docs/privacy/consent-in-unify/#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on an [end user's Profile](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event). -Once an end user's consent preferences are stored on their Profile, you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. +Once an end user's consent preferences are stored on their Profile, you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. > info "Consent in Engage Audiences is in public beta" > Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. @@ -15,49 +15,49 @@ Once an end user's consent preferences are stored on their Profile, you can crea ## Enforce consent preferences in your Audiences Before using an end user's consent preferences to create your Audiences, you must complete the following prerequisites: -- You've previously set up [Consent in Segment Connections](/docs/privacy/consent-management/configure-consent-management) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. -- You generate the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event) Track event each time a user updates their consent preferences. This event stamps each Profile with a user's consent preferences. +- You set up [Consent in Segment Connections](/docs/privacy/consent-management/configure-consent-management) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. +- You generate the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event) Track event each time a user updates their consent preferences. This event stamps each Profile with a user's consent preferences. +- You verified that your Profiles have consent preferences by creating an Audience with a consent trait condition. If the majority of Profiles have consent preferences on them, you're ready to enable consent enforcement in your Unify space. + +> info "How does Segment handle Profiles with missing consent preferences?" +> If you have Profiles with consent preferences for some, but not all consent categories, Segment adds all categories to a `categoryPreferences` object on an Identify or Track call and considers consent categories without current consent preferences to be `false`. If you have Profiles with no consent preferences, Segment automatically adds an empty `categoryPreferences` object on an Identify or Track call and prevents those Profiles from flowing downstream to your destination. ### Step 1: Enable consent in your Unify space -Once your consent categories are set up, you've mapped your destinations to a consent category, and each of your Profiles is stamped with your end user's consent preferences, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but you've previously set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. If you enable or disable consent enforcement in your Unify space, you are only enabling or disabling automatic consent enforcement in Engage Audiences: Segment will continue to store consent preferences on your Profiles even if you've disabled consent enforcement in your Unify space. +Once your consent categories are set up, you've mapped your destinations to a consent category, and each of your Profiles is stamped with your end user's consent preferences, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. > info "" -> In order to enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). - -Before you enable consent in your Unify space, you can verify that your Profiles have consent preferences by creating an Audience with a consent trait condition. If the majority of Profiles have consent preferences on them, you're ready to enable consent enforcement in your Unify space. - -If you have Profiles with consent preferences for some, but not all consent categories, Segment adds all categories to a `categoryPreferences` object on an Identify or Track call and considers consent categories without current consent preferences to be `false`. If you have Profiles with no consent preferences, Segment automatically adds an empty `categoryPreferences` object on an Identify or Track call and prevents those Profiles from flowing downstream to your destination. +> To enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). To enable Consent Management in your Unify space: 1. Navigate to **Privacy > Consent Management** and select the Settings tab. 2. Enable the toggle under the Status column to turn on Consent Management for your Unify space. 3. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. -After you’ve enabled Consent Management in your Unify space, you can create an Audience as you normally would and Segment automatically allows or blocks profiles from flowing to your downstream destinations, based on end-user preferences and your destination mapping. - -> warning "Consent enforcement does not automatically apply to Audiences that existed prior to the enablement of Consent Management in your Unify space" -> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync. All Audiences created after you enable Consent Management for a space automatically enforce consent preferences when sharing their data with mapped destination(s). +After you’ve enabled Consent Management in your Unify space, you can create an Audience as you normally would and Segment automatically enforces consent in your downstream destinations. +> info "" +> If you choose not to enable Consent Management for a Unify space but you've set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. If you enable or disable consent enforcement in your Unify space, you are only enabling or disabling automatic consent enforcement in Engage Audiences: Segment will continue to store consent preferences on your Profiles even if you've disabled consent enforcement in your Unify space. ### Step 2: Create your Audience -> info "Consent preferences can affect Audience sync size" -> The number of profiles that sync to your Engage destination(s) depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. To see the impact of consent on your Audience, add consent traits to the Audience builder. - -During the public beta, you can create a Profiles Audiences as you normally would and Segment automatically enforces consent in your downstream destinations. If you don't want Segment to automatically enforce consent, disable consent enforcement in your Unify space and manually add the consent trait Audience condition when building your Audiences. - -Destinations mapped to a consent category only receive the Profiles of users who have given consent to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. +During the public beta, you can create a Profiles Audiences as you normally would and Segment automatically allows or blocks profiles from flowing to your downstream destinations, based on end-user preferences and your destination mapping. If you don't want Segment to automatically enforce consent, disable consent enforcement in your Unify space and manually add the consent trait Audience condition when building your Audiences. If you opt to send your Audience to multiple destinations belonging to multiple categories, then each destination receives data for the Profiles that have consent to the destination’s mapped category. For example, if you have an audience mapped to Google Ads (mapped to the Advertising consent category) and Snowflake (mapped to the Analytics consent category), then: * Google Ads receives all profiles that have consented to Advertising consent category, independent of users' who consented to Analytics * Snowflake receives all profiles that have consented to Analytics, independent of their Advertising preferences. +> info "Consent preferences can affect Audience sync size" +> The number of profiles that sync to your Engage destination(s) depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. To see the impact of consent on your Audience, add consent traits to the Audience builder. + ## Verify that your Audiences respect consent preferences After you enable consent management in your Unify space and create a new audience, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. -However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a `FILTERED_BY_END_USER_CONSENT` event. +However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user Profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a `FILTERED_BY_END_USER_CONSENT` event. + +> warning "Consent enforcement does not automatically apply to Audiences that existed prior to the enablement of Consent Management in your Unify space" +> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync. All Audiences created after you enable Consent Management for a space automatically enforce consent preferences when sharing their data with mapped destination(s). ### Compare an end user Profile to your mapped categories @@ -72,4 +72,4 @@ To verify that your events are being filtered by end user consent: 2. On the Delivery Overview page, select **Filtered at destination**. 3. Search through the table of discarded events until you find an event with a discard reason of `FILTERED_BY_END_USER_CONSENT`. -If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. +If the discard reason `FILTERED_BY_END_USER_CONSENT` is present in the point where your destination discards events, your destination is enforcing your end users' consent preferences appropriately. \ No newline at end of file From 66554875cbc32fe221980027e21289a916579e5f Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 21 Jul 2025 10:57:40 -0400 Subject: [PATCH 16/18] content update [netlify-build] --- .../consent-management/consent-in-engage.md | 34 +++++++++---------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index c404fcf420..fac97d694d 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -3,28 +3,26 @@ title: Consent in Engage Audiences plan: consent-management --- -Segment uses the [consent object](/docs/privacy/consent-in-unify/#segment-consent-preference-event) on Segment events, including the [Segment Consent Preference Updated](/docs/privacy/consent-in-unify/#segment-consent-preference-updated-event) Track event, to evaluate and store consent preferences on an [end user's Profile](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event). +Once an end user's consent preferences are [stored on their Profile](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event), you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. -Once an end user's consent preferences are stored on their Profile, you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. - -> info "Consent in Engage Audiences is in public beta" +> info "Consent in Engage Profiles Audiences is in public beta" > Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. > -> Only Profiles Audiences are supported by Consent in Engage Audiences. Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, Computed Traits, and Journeys. Segment does not automatically enforce consent for the [LiveRamp Audiences](/docs/connections/destinations/catalog/actions-liveramp-audiences/) and [The Trade Desk CRM](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/) destinations. +> Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, Computed Traits, and Journeys. Segment does not automatically enforce consent for the [LiveRamp Audiences](/docs/connections/destinations/catalog/actions-liveramp-audiences/) and [The Trade Desk CRM](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/) destinations. ## Enforce consent preferences in your Audiences -Before using an end user's consent preferences to create your Audiences, you must complete the following prerequisites: -- You set up [Consent in Segment Connections](/docs/privacy/consent-management/configure-consent-management) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. -- You generate the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify#segment-consent-preference-updated-event) Track event each time a user updates their consent preferences. This event stamps each Profile with a user's consent preferences. -- You verified that your Profiles have consent preferences by creating an Audience with a consent trait condition. If the majority of Profiles have consent preferences on them, you're ready to enable consent enforcement in your Unify space. +Before enforcing consent preferences in your Profiles Audiences, you must complete the following prerequisites: +- Set up [Consent in Segment Connections](/docs/privacy/consent-management/configure-consent-management) or [Consent in Reverse ETL](/docs/privacy/consent-management/consent-in-retl) and have events stamped with the [consent object](/docs/privacy/consent-management/consent-in-segment-connections#consent-object) streaming from your source or available in your data warehouse. +- Map your Engage Destinations to consent categories. Segment assumes all Engage Destinations not mapped to a consent category do not require consent and will recieve all events containing a consent object. +- Verify that your Profiles have consent preferences by creating an Audience with a consent trait condition. If the majority of Profiles have consent preferences on them, you're ready to enable consent enforcement in your Unify space. > info "How does Segment handle Profiles with missing consent preferences?" > If you have Profiles with consent preferences for some, but not all consent categories, Segment adds all categories to a `categoryPreferences` object on an Identify or Track call and considers consent categories without current consent preferences to be `false`. If you have Profiles with no consent preferences, Segment automatically adds an empty `categoryPreferences` object on an Identify or Track call and prevents those Profiles from flowing downstream to your destination. ### Step 1: Enable consent in your Unify space -Once your consent categories are set up, you've mapped your destinations to a consent category, and each of your Profiles is stamped with your end user's consent preferences, you're ready to enable Consent Management in your Unify space. You must enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. +You can enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but have set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. > info "" > To enable Consent Management in your Unify space, you must have a [Workspace Owner role](/docs/segment-app/iam/roles/). @@ -34,14 +32,14 @@ To enable Consent Management in your Unify space: 2. Enable the toggle under the Status column to turn on Consent Management for your Unify space. 3. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. -After you’ve enabled Consent Management in your Unify space, you can create an Audience as you normally would and Segment automatically enforces consent in your downstream destinations. +### Step 2: Create your Audience -> info "" -> If you choose not to enable Consent Management for a Unify space but you've set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. If you enable or disable consent enforcement in your Unify space, you are only enabling or disabling automatic consent enforcement in Engage Audiences: Segment will continue to store consent preferences on your Profiles even if you've disabled consent enforcement in your Unify space. +You can create a Profiles Audiences as you normally would and Segment automatically enforces consent in your downstream destinations. If you don't want Segment to automatically enforce consent, disable consent enforcement in your Unify space and manually add the consent trait Audience condition when building your Audiences. -### Step 2: Create your Audience +> warning "Consent enforcement doesn't automatically apply to Audiences that existed prior to the enablement of Consent Management in your Unify space" +> Audiences that existed before you enabled Consent Management in a Unify space only enforce consent preferences for new Profiles that enter the Audience after you enabled Consent Management. If you want to ensure each of your Audiences only includes consenting Profiles, request a resync. All Audiences created after you enable Consent Management for a space automatically enforce consent preferences when sharing their data with mapped destination(s). -During the public beta, you can create a Profiles Audiences as you normally would and Segment automatically allows or blocks profiles from flowing to your downstream destinations, based on end-user preferences and your destination mapping. If you don't want Segment to automatically enforce consent, disable consent enforcement in your Unify space and manually add the consent trait Audience condition when building your Audiences. +Destinations mapped to a consent category only receive the Profiles of users who have given consent to that category. Destinations not mapped to a consent category receive all Profiles in an Audience, regardless of the Profile's consent preferences. If you opt to send your Audience to multiple destinations belonging to multiple categories, then each destination receives data for the Profiles that have consent to the destination’s mapped category. For example, if you have an audience mapped to Google Ads (mapped to the Advertising consent category) and Snowflake (mapped to the Analytics consent category), then: * Google Ads receives all profiles that have consented to Advertising consent category, independent of users' who consented to Analytics @@ -50,9 +48,11 @@ If you opt to send your Audience to multiple destinations belonging to multiple > info "Consent preferences can affect Audience sync size" > The number of profiles that sync to your Engage destination(s) depends on the number of end users that consented to their data being shared with the destinations connected to your Audience. To see the impact of consent on your Audience, add consent traits to the Audience builder. +If you have Profiles with consent preferences for some, but not all consent categories, Segment adds all available categories to the `categoryPreferences` object on all Identify and/or Track calls and considers missing consent categories to be `false`. If you have Profiles with no consent preferences, Segment automatically adds an empty `categoryPreferences` object and prevents those Profiles from flowing downstream to your destination. + ## Verify that your Audiences respect consent preferences -After you enable consent management in your Unify space and create a new audience, Segment automatically filters out data from end users that have not consented to the category that you mapped to your connected destination. +After you enable consent management in your Unify space, Segment automatically filters out end users that have not consented to the category that you mapped to your connected destination. However, if you'd like to confirm that this behavior is working as intended, you can either [compare an end user Profile against your mapped categories](#compare-an-end-user-profile-to-your-mapped-categories) or verify that [Delivery Overview](#use-delivery-overview) contains a `FILTERED_BY_END_USER_CONSENT` event. @@ -65,7 +65,7 @@ You can verify that your Audiences are respecting consent preferences by selecti ### Use Delivery Overview -You can use Delivery Overview to verify that your destination is enforcing your user's consent preferences by checking for the presence of a `FILTERED_BY_END_USER_CONSENT` discard reason. +You can use [Delivery Overview](/docs/connections/delivery-overview/) to verify that your destination is enforcing your user's consent preferences by checking for the presence of a `FILTERED_BY_END_USER_CONSENT` discard reason. To verify that your events are being filtered by end user consent: 1. Select the destination connected to your Engage Audience. From 968dac285576f62d275f4412ae2d80cda45fa730 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 21 Jul 2025 11:25:27 -0400 Subject: [PATCH 17/18] addtl fixes [netlify-build] --- src/privacy/consent-management/consent-in-engage.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index fac97d694d..de52ca2ac0 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -17,9 +17,6 @@ Before enforcing consent preferences in your Profiles Audiences, you must comple - Map your Engage Destinations to consent categories. Segment assumes all Engage Destinations not mapped to a consent category do not require consent and will recieve all events containing a consent object. - Verify that your Profiles have consent preferences by creating an Audience with a consent trait condition. If the majority of Profiles have consent preferences on them, you're ready to enable consent enforcement in your Unify space. -> info "How does Segment handle Profiles with missing consent preferences?" -> If you have Profiles with consent preferences for some, but not all consent categories, Segment adds all categories to a `categoryPreferences` object on an Identify or Track call and considers consent categories without current consent preferences to be `false`. If you have Profiles with no consent preferences, Segment automatically adds an empty `categoryPreferences` object on an Identify or Track call and prevents those Profiles from flowing downstream to your destination. - ### Step 1: Enable consent in your Unify space You can enable Consent Management in each Unify space that you'd like Segment to automatically enforce consent preferences. If you've chosen not to enable Consent Management for a Unify space but have set up Consent Management for Reverse ETL or Segment Connections, Segment continues to stamp consent preferences on your Profiles. From 5aa78fb9025316b881058441bd84a7642035961a Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 29 Jul 2025 12:52:12 -0400 Subject: [PATCH 18/18] Liveramp and TTD CRM destinations now supported --- src/privacy/consent-management/consent-in-engage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/consent-management/consent-in-engage.md b/src/privacy/consent-management/consent-in-engage.md index de52ca2ac0..a206bd8c98 100644 --- a/src/privacy/consent-management/consent-in-engage.md +++ b/src/privacy/consent-management/consent-in-engage.md @@ -8,7 +8,7 @@ Once an end user's consent preferences are [stored on their Profile](/docs/priva > info "Consent in Engage Profiles Audiences is in public beta" > Consent in Engage Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. > -> Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, Computed Traits, and Journeys. Segment does not automatically enforce consent for the [LiveRamp Audiences](/docs/connections/destinations/catalog/actions-liveramp-audiences/) and [The Trade Desk CRM](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/) destinations. +> Consent in Engage Audiences does **not** support Engage Accounts Audiences, Linked Audiences, Predictions, Computed Traits, and Journeys. ## Enforce consent preferences in your Audiences