From 6f41c6eaa6de99885a80b35538924e2cc50cabf8 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 17 Oct 2023 12:56:09 -0400 Subject: [PATCH 1/7] init validate consent integration docs --- src/privacy/configure-consent-management.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md index ba87f66e6b..7f259c8dcb 100644 --- a/src/privacy/configure-consent-management.md +++ b/src/privacy/configure-consent-management.md @@ -65,6 +65,13 @@ If you'd like to integrate with any other CMP, Segment requires you to build you ---> +### Validate your consent integration + +To validate your consent management integration was correctly set up, select one of the following options: + +- **Analytics.js 2.0 users**: Use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to validate that consent events contain the consent event details. +- **Kotlin and Analytics.js 2.0 users**: View the events in [Delivery Overview](/docs/connections/delivery-overview/) to confirm that the events flowing to your destinations have the same format as the consent object example in the [Consent in Segment Connections](/docs/privacy/consent-in-segment-connsctions) documentation. + ## Edit consent categories If you need to make changes to your consent categories, you can edit them on the Consent Management page. You may experience some latency between making the changes and having the changes take effect. From 56052c5f3f42a43c91795fe174ee95457a7fcd3d Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 17 Oct 2023 12:59:56 -0400 Subject: [PATCH 2/7] [netlify-build] --- src/privacy/configure-consent-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md index 7f259c8dcb..43c532b942 100644 --- a/src/privacy/configure-consent-management.md +++ b/src/privacy/configure-consent-management.md @@ -70,7 +70,7 @@ If you'd like to integrate with any other CMP, Segment requires you to build you To validate your consent management integration was correctly set up, select one of the following options: - **Analytics.js 2.0 users**: Use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to validate that consent events contain the consent event details. -- **Kotlin and Analytics.js 2.0 users**: View the events in [Delivery Overview](/docs/connections/delivery-overview/) to confirm that the events flowing to your destinations have the same format as the consent object example in the [Consent in Segment Connections](/docs/privacy/consent-in-segment-connsctions) documentation. +- **Kotlin and Analytics.js 2.0 users**: View the events in [Delivery Overview](/docs/connections/delivery-overview/) to confirm that the events flowing to your destinations have the same format as the consent object example in the [Consent in Segment Connections](/docs/privacy/consent-in-segment-connsctions) documentation. ## Edit consent categories From 7f43503cfd15bdc8497759ef4158045005a3070e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 17 Oct 2023 19:38:38 -0400 Subject: [PATCH 3/7] [netlify-build] --- src/privacy/configure-consent-management.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md index 43c532b942..de62d465c5 100644 --- a/src/privacy/configure-consent-management.md +++ b/src/privacy/configure-consent-management.md @@ -65,12 +65,14 @@ If you'd like to integrate with any other CMP, Segment requires you to build you ---> -### Validate your consent integration +### Validate your CMP integration -To validate your consent management integration was correctly set up, select one of the following options: +Customers with Analytics.js 2.0 sources can use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to confirm that events from their source contain the [consent object](/docs/privacy/consent-in-segment-connections) and, for Unify/Engage users, the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) emits every time end users update their consent preferences. + +All users can validate their consent integration with Segment by using the [Source Debugger](/docs/connections/delivery-overview/) to confirm that events contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify/Engage users should also confirm their sources emit the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) every time end users update their consent preferences. + +You can also confirm your events flow to destinations or are blocked from destinations according to the consent categories you created in [Step 1: Create consent categories in the Segment App](#step-1-create-consent-categories-in-the-segment-app). -- **Analytics.js 2.0 users**: Use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to validate that consent events contain the consent event details. -- **Kotlin and Analytics.js 2.0 users**: View the events in [Delivery Overview](/docs/connections/delivery-overview/) to confirm that the events flowing to your destinations have the same format as the consent object example in the [Consent in Segment Connections](/docs/privacy/consent-in-segment-connsctions) documentation. ## Edit consent categories From b73f487fd1927f298dc7d85eb75a9921a934424e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 17 Oct 2023 19:42:04 -0400 Subject: [PATCH 4/7] fix source debugger link [netlify-build] --- src/privacy/configure-consent-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md index de62d465c5..da6fd1e065 100644 --- a/src/privacy/configure-consent-management.md +++ b/src/privacy/configure-consent-management.md @@ -69,7 +69,7 @@ If you'd like to integrate with any other CMP, Segment requires you to build you Customers with Analytics.js 2.0 sources can use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to confirm that events from their source contain the [consent object](/docs/privacy/consent-in-segment-connections) and, for Unify/Engage users, the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) emits every time end users update their consent preferences. -All users can validate their consent integration with Segment by using the [Source Debugger](/docs/connections/delivery-overview/) to confirm that events contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify/Engage users should also confirm their sources emit the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) every time end users update their consent preferences. +All users can validate their consent integration with Segment by using the [Source Debugger](/docs/connections/sources/debugger/) to confirm that events contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify/Engage users should also confirm their sources emit the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) every time end users update their consent preferences. You can also confirm your events flow to destinations or are blocked from destinations according to the consent categories you created in [Step 1: Create consent categories in the Segment App](#step-1-create-consent-categories-in-the-segment-app). From 4c1e08d19803fecd5327bcc21304ab5113fd00ab Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 19 Oct 2023 17:59:06 -0400 Subject: [PATCH 5/7] Apply suggestions from code review Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> --- src/privacy/configure-consent-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md index da6fd1e065..d7d2c34160 100644 --- a/src/privacy/configure-consent-management.md +++ b/src/privacy/configure-consent-management.md @@ -67,9 +67,9 @@ If you'd like to integrate with any other CMP, Segment requires you to build you ### Validate your CMP integration -Customers with Analytics.js 2.0 sources can use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to confirm that events from their source contain the [consent object](/docs/privacy/consent-in-segment-connections) and, for Unify/Engage users, the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) emits every time end users update their consent preferences. +Customers with Analytics.js 2.0 sources can use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to confirm that events from their source contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify and Engage users can also verify that the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) emits every time end users update their consent preferences. -All users can validate their consent integration with Segment by using the [Source Debugger](/docs/connections/sources/debugger/) to confirm that events contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify/Engage users should also confirm their sources emit the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) every time end users update their consent preferences. +All users can validate their consent integration by using Segment's [Source Debugger](/docs/connections/sources/debugger/) to confirm that events contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify/Engage users should also confirm their sources emit the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) every time end users update their consent preferences. You can also confirm your events flow to destinations or are blocked from destinations according to the consent categories you created in [Step 1: Create consent categories in the Segment App](#step-1-create-consent-categories-in-the-segment-app). From 50f15c2020fe64d335c52ae143190cb100abbdb2 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 19 Oct 2023 18:35:29 -0400 Subject: [PATCH 6/7] [netlify-build] --- src/privacy/configure-consent-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md index d7d2c34160..8f334e13f1 100644 --- a/src/privacy/configure-consent-management.md +++ b/src/privacy/configure-consent-management.md @@ -69,9 +69,9 @@ If you'd like to integrate with any other CMP, Segment requires you to build you Customers with Analytics.js 2.0 sources can use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to confirm that events from their source contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify and Engage users can also verify that the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) emits every time end users update their consent preferences. -All users can validate their consent integration by using Segment's [Source Debugger](/docs/connections/sources/debugger/) to confirm that events contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify/Engage users should also confirm their sources emit the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) every time end users update their consent preferences. +All users can validate these using Segment's [Source Debugger](/docs/connections/sources/debugger/) if already connected to Segment. -You can also confirm your events flow to destinations or are blocked from destinations according to the consent categories you created in [Step 1: Create consent categories in the Segment App](#step-1-create-consent-categories-in-the-segment-app). +You can also confirm your events flow to destinations or are blocked from destinations according to the consent categories you created in [Step 1: Create consent categories in the Segment App](#step-1-create-consent-categories-in-the-segment-app), if already connected to the destination. ## Edit consent categories From 564a66a055148fac824b3a17afb9ab5a11331616 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 19 Oct 2023 18:46:29 -0400 Subject: [PATCH 7/7] Update configure-consent-management.md --- src/privacy/configure-consent-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md index 8f334e13f1..f1c27c78df 100644 --- a/src/privacy/configure-consent-management.md +++ b/src/privacy/configure-consent-management.md @@ -69,7 +69,7 @@ If you'd like to integrate with any other CMP, Segment requires you to build you Customers with Analytics.js 2.0 sources can use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to confirm that events from their source contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify and Engage users can also verify that the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) emits every time end users update their consent preferences. -All users can validate these using Segment's [Source Debugger](/docs/connections/sources/debugger/) if already connected to Segment. +All users can validate that events contain the consent object and that the Segment Consent Preference event is present using Segment's [Source Debugger](/docs/connections/sources/debugger/). You can also confirm your events flow to destinations or are blocked from destinations according to the consent categories you created in [Step 1: Create consent categories in the Segment App](#step-1-create-consent-categories-in-the-segment-app), if already connected to the destination.