Skip to content

Update Consent Object section in Consent Mgmt docs #6692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 13, 2024
Merged

Update Consent Object section in Consent Mgmt docs #6692

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7079263
Update consent-in-segment-connections.md
forstisabella Jun 11, 2024
50b9898
[netlify-build]
forstisabella Jun 11, 2024
1291478
make requested updates
forstisabella Jun 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/privacy/consent-management/configure-consent-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,4 +85,4 @@ Disabling a consent category means that Segment no longer enforces end user cons

1. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
2. On the Consent Management page, disable the toggle for the category you'd like to disable.
3. On the "Disable [category-name]?" popup, enter the category name in the Consent category name field and click **Disable category**.
3. On the "Disable [category-name]?" popup, enter the category name in the Consent category name field and click **Disable category**.
7 changes: 4 additions & 3 deletions src/privacy/consent-management/consent-in-segment-connections.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,10 @@ If your sources also contain the integrations object, Segment will look at the c

## Consent object

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:
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:

> success ""
> The JSON keys in the consent object should represent the `categoryId` for each consent category.

```json
{
Expand All @@ -42,8 +45,6 @@ Segment requires every event from all of your sources to include the end user co

```

<!-- 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.-->

Events without the consent object will continue to flow to destinations without consent enforcement.

## Reconcile consent conflicts
Expand Down
Loading