Skip to content

Commit d5c311f

Browse files
Update src/privacy/consent-management/consent-in-unify.md
Co-authored-by: Casie Oxford <[email protected]>
1 parent 9f1661a commit d5c311f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/privacy/consent-management/consent-in-unify.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ If you use Protocols, the Segment app automatically adds the Segment Consent Pre
5151
5252
### Sharing consent with Actions destinations
5353

54-
In addition to enforcing consent in Connections, you might want these preferences to flow to each destination so your destinations can be aware when an end-user revokes their consent. You can use the [Destination Actions framework](/docs/connections/destinations/destination-actions) to edit the destination's mapping and copy the consent preferences from the Segment Consent Preference Updated event to a destination-specified consent field.
54+
In addition to enforcing consent in Connections, you may want these preferences to flow to each destination so your destinations can be aware when an end-user revokes their consent. You can use the [Destination Actions framework](/docs/connections/destinations/destination-actions) to edit the destination's mapping and copy the consent preferences from the Segment Consent Preference Updated event to a destination-specified consent field.
5555

5656
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.
5757

0 commit comments

Comments
 (0)