small additions

Author: forstisabella

src/privacy/configure-consent-management.md

@@ -9,7 +9,7 @@ title: Configure Consent Management
 ## Prerequisites
 
 Before you can configure consent in Segment, you'll need to take the following steps:
-- **Access your consent management tool**. You'll need a list of your consent categories and the key or ID associated with each topic.
+- **Access your consent management tool and set up consent categories**. You'll need a list of your consent categories and the key or ID associated with each topic.
 - **Know how your company maps each destination**. You'll need to know which destinations map to each categories. 
 - **Update your web libraries with the consent object**. To ensure Segment is receiving your end-user consent preferences, you'll need access to your web libraries so you can include the consent object to every event.
 

src/privacy/consent-management.md

@@ -9,7 +9,7 @@ related:
 
 Segment works with your third party consent management platform to collect the categories an end user consents to, map each of your Segment destinations to a consent category, and route events only to the categories consented to by a user.
 
-![Diagram outlining information flowing from an end user to Segment destinations](/images/consent-overview.png)
+![Diagram outlining information flowing from an end user to Segment destinations](src/privacy/images/consent-overview.png)
 
 When an end user visits your site, they set **consent preferences**, or make decisions about the types of data they want you to collect, use, and share. These consent preferences are typically presented as a set list of categories that describe how your company intends to use that data. Common categories include personalization, advertising, and site performance.
 
@@ -18,8 +18,38 @@ After a user sets their consent preferences, Segment updates the [consent object
 > success ""
 > Segment collects consent for both registered users and anonymous users.
 
+If a user changes the categories they consent to or if they consent using a different device or identifier, Segment sends the information about their consent, using a [Track call](docs/connections/spec/track), to your downstream destinations and storage destinations.
+
+For example: 
+
+``` json
+{
+  "anonymousId": "23adfd82-aa0f-45a7-a756-24f2a7a4c895",
+  "type": "track",
+  "event": "Consent Change",
+  "userId": "u123",
+  "traits": {
+     "email": "[email protected]",
+     "phone": "555-555-5555",
+  }
+  "timestamp": "2023-01-01T00:00:00.000Z",
+  "context": {
+    "consent": {
+      "categoryPreferences" : {
+   "Advertising": true,
+   "Analytics": false,
+   "Functional": true,
+   "DataSharing": false
+}
+    }
+  }
+}
+```
+
 If a **consent conflict** exists (for example, one user on two different devices consented to two different categories), Segment resolves the conflict according to the [Reconcile Consent](/docs/privacy/reconcile-consent) documentation.
 
+You can view more information about a user's consent preferences on their profile in Unity. Consent information and a consent conflict flag are visible as traits on a user's profile in Unity.
+
 ## Consent object
 
 Segment requires every event from all of your sources to include the end-user consent preferences, captured by your consent management tools or your application logic, in the form of the **consent object**. The consent object is a JSON object with the following format:
@@ -34,4 +64,6 @@ context {
 	}
 ```
 
+<!-- settings are here: https://github.com/segmentio/analytics-schemas/commit/3497903b49664c82d1e6749fbb1d794f2f197f6d--->
+
 Once you've added the consent object to your web libraries and started collecting user data, you can use the Consent Management tab in the Segment app to [map your destinations to the consent categories](/docs/src/privacy/configure-consent-management) you set up in your third-party consent management platform.