Merge pull request #6371 from segmentio/DOC-872

Pass SCPU track event ignoring consent preferences [DOC-872]

Author: forstisabella

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

@@ -48,3 +48,12 @@ If you use Protocols, the Segment app automatically adds the Segment Consent Pre
 > Segment has standardized a series of reserved event names that have special semantic meaning and maps these events to tools that support them.
 >
 > See the [Semantic Events](/docs/connections/spec/semantic/) docs for more details.
+
+### Sharing consent with Actions destinations
+
+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. 
+
+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.