Skip to content
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

How to override data being sent to Engage via Consent Manager #6489

Closed
wants to merge 1 commit into from
+10 −1
Closed

How to override data being sent to Engage via Consent Manager #6489

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 10 additions & 1 deletion src/privacy/consent-management/consent-in-unify.md
View file
Original file line number Diff line number Diff line change
@@ -56,4 +56,13 @@ In addition to enforcing consent in Connections, you may want these preferences
If you use Destination Actions to send consent information to your destinations, the Segment Consent Preference Updated event should **only** include information about a user's consent preferences because this event is sent regardless of an end-user's consent preferences.

> info "Sharing consent with Classic Destinations is not available"
> Segment only supports sharing consent with Actions Destinations.
> Segment only supports sharing consent with Actions Destinations.

### FAQ

**Q. How can your override data being sent to an Engage space?**

A. By default Personas is set to true in the consent manager, but this can be overridden by passing Personas false in the integrations object in all events.
```analytics.identify(71661,{favoriteFood:"cheese burgers"},{"integrations":{"Personas":false}})```