Consent in Engage Audiences (public beta) #7763
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
stayseesong
requested changes
Jul 14, 2025
|
|
||
| Once an end user's consent preferences are stored on their Profile, you can create Engage Audiences that respect end user consent preferences to better comply with privacy regulations. | ||
|
|
||
| > warning "Consent in Engage Audiences is in public beta" |
There was a problem hiding this comment.
are public beta info bubbles now warnings? I thought they've been info bubbles
There was a problem hiding this comment.
no you're right - it should be an info bubble!
| 1. Navigate to Unify and select the space where you'd like to enable Consent Management. | ||
| 2. Select **Unify settings** and navigate to the **Space management** tab. | ||
| 3. Select the **Consent management** setting and enable the toggle to turn on Consent Management for your Unify space. | ||
| 4. On the **Enable consent enforcement for [Space Name]?** popup, enter the name of your Unify space and click **Enable enforcement**. |
There was a problem hiding this comment.
Is the ? supposed to be there?
There was a problem hiding this comment.
yes - in the UI it reads "Disable consent enforcement for Space Name?" so I copied the title of the popup here
forstisabella
commented
Jul 15, 2025
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
stayseesong
previously approved these changes
Jul 16, 2025
forstisabella
commented
Jul 17, 2025
forstisabella
commented
Jul 18, 2025
stayseesong
previously approved these changes
Jul 22, 2025
forstisabella
commented
Jul 29, 2025
stayseesong
approved these changes
Jul 29, 2025
stayseesong
previously approved these changes
Jul 29, 2025
forstisabella
commented
Sep 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Added docs for Consent in Engage Audiences public beta release. Also updated the Consent Stored on the Profile docs, given some of the updates that are happening for the Engage release
Merge timing
July 18, 2025August 22, 2025?Related issues (optional)