Skip to content

Commit 564a66a

Browse files
committed
Update configure-consent-management.md
1 parent 50f15c2 commit 564a66a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/privacy/configure-consent-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ If you'd like to integrate with any other CMP, Segment requires you to build you
6969

7070
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.
7171

72-
All users can validate these using Segment's [Source Debugger](/docs/connections/sources/debugger/) if already connected to Segment.
72+
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/).
7373

7474
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.
7575

0 commit comments

Comments
 (0)