Skip to content

Commit 4c1e08d

Browse files
Apply suggestions from code review
Co-authored-by: rchinn-segment <[email protected]>
1 parent b73f487 commit 4c1e08d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/privacy/configure-consent-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,9 @@ If you'd like to integrate with any other CMP, Segment requires you to build you
6767

6868
### Validate your CMP integration
6969

70-
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.
70+
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 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.
72+
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.
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).
7575

0 commit comments

Comments
 (0)