Skip to content

Commit ca4a13c

Browse files
Merge pull request #6692 from segmentio/consent-object-context-update
Update Consent Object section in Consent Mgmt docs
2 parents ca48678 + 1291478 commit ca4a13c

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

src/privacy/consent-management/configure-consent-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,4 +80,4 @@ Disabling a consent category means that Segment no longer enforces end user cons
8080

8181
1. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
8282
2. On the Consent Management page, disable the toggle for the category you'd like to disable.
83-
3. On the "Disable [category-name]?" popup, enter the category name in the Consent category name field and click **Disable category**.
83+
3. On the "Disable [category-name]?" popup, enter the category name in the Consent category name field and click **Disable category**.

src/privacy/consent-management/consent-in-segment-connections.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,10 @@ If your sources also contain the integrations object, Segment will look at the c
2020
2121
## Consent object
2222

23-
Segment requires every event from all of your sources to include the end user consent preferences, captured by your CMP or your application logic, in the form of the **consent object**. The consent object is a JSON object with the following format:
23+
Segment requires every event from all of your sources to include the end user consent preferences, captured by your CMP or your application logic, in the form of the **consent object**. The consent object is a JSON object nestled inside of the [context object](/docs/connections/spec/common/#context) with the following format:
24+
25+
> success ""
26+
> The JSON keys in the consent object should represent the `categoryId` for each consent category.
2427
2528
```json
2629
{
@@ -38,8 +41,6 @@ Segment requires every event from all of your sources to include the end user co
3841

3942
```
4043

41-
<!-- Not currently in scope: The categories consented to by a user and a flag if a [consent conflict](#reconcile-consent-conflicts) exists are pulled from the consent object and are visible as traits on a user's profile in Unify. For more information about Consent in Unify, see the [Consent in Unify](/docs/privacy/consent-management-in-unify) docs.-->
42-
4344
Events without the consent object will continue to flow to destinations without consent enforcement.
4445

4546
## Reconcile consent conflicts

0 commit comments

Comments
 (0)