making requested changes [netlify-build]

Author: forstisabella

src/_data/sidenav/main.yml

@@ -463,8 +463,6 @@ sections:
       title: Consent Management Overview
     - path: /privacy/configure-consent-management
       title: Configure Consent Management
-    - path: /privacy/reconcile-consent
-      title: Reconcile Consent Conflicts
   - path: /privacy/account-deletion
     title: Account & Data Deletion
   - path: /privacy/hipaa-eligible-segment

src/privacy/configure-consent-management.md

@@ -3,8 +3,13 @@ title: Configure Consent Management
 ---
 > info "Consent Management is currently in private beta"
 > This means that the Consent Management features are in active development, and some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
+>
+> During the private beta, Consent Management only supports website sources and event streaming destinations. All other sources and destinations are not impacted.
+
+After setting up a third-party consent management platform (CMP,) you can enforce the consent collected from your users by configuring consent categories in your your Segment workspace and adding the [consent object](/docs/privacy/consent-management/#consent-object) to your web libraries. After you've configured consent in the Segment app, your events will be routed only to those streaming destinations consented to by your users.
 
 <!--- note to include: how to find your category ID in tools other than onetrust-->
+<!--- Folks need to do some prereq setup, there are two docs - read through and setup ourselves before including information -->
 
 ## Prerequisites
 
@@ -13,37 +18,30 @@ Before you can configure consent in Segment, take the following steps:
 - **Know how your company maps each destination**. You need to know which destinations map to which categories. 
 - **Update your web libraries with the consent object**. You need access to your web libraries so you can include the consent object in every event.
 
-<!-- Ask Aaron about consent object order of ops/can it be tested??? Can you undo or pause this?? -->
-
-> error "After adding the consent object to your events, your data is immediately impacted"
-> If you disable a consent category, events are not sent to mapped destinations.
->  
-> If a destination is mapped to multiple categories, and the end user has conflicting preferences, data will be sent to the destination.
-> 
-> If Segment receives an API call with both an integrations object and a consent object, the consent object takes preference.
-
-<!-- does this need to be added to multiple pages-->
-
 ## Step 1: Create consent categories
 
-> warning "You can map website sources and event streaming destinations to consent categories during the private beta"
-> All other sources and destinations are not affected by consent mappings.
-
 <!-- Add note that category ID is case sensitive--->
 
 1. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
 2. On the Consent management page, click **Get started**.
 3. 
 
 
+## Step 2: Map destinations to consent categories
+
 <br/>
 > warning "Segment recommends mapping all destinations to a category"
 > Any destination that doesn't have a mapping won't receive events with a consent object. 
 
 
-## Step 2: 
+## Step 3: Add the consent object to your web libraries
 
 
-## Step 3: 
+> error "After adding the consent object to your events, your data is immediately impacted"
+> If you disable a consent category, events are not sent to mapped destinations.
+>  
+> If a destination is mapped to multiple categories, and the end user has conflicting preferences, data will be sent to the destination.
+> 
+> If Segment receives an API call with both an integrations object and a consent object, the consent object takes preference.
 
 ## Ingesting consent data

src/privacy/consent-management.md

@@ -7,18 +7,22 @@ related:
 > info "Consent Management is currently in private beta"
 > This means that the Consent Management features are in active development, and some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
 
-Segment works with your third party consent management platform to capture the categories consented to by an end user, map each of your Segment destinations to a consent category, and route events only to the appropriate categories.
+Segment works with your third-party consent management platform to capture the categories consented to by an end user and route events to the streaming destinations in the categories consented to by a user. 
 
 ![Diagram outlining information flowing from an end user to Segment destinations](/docs/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.
 
-After a user sets their consent preferences, Segment updates the [consent object](#consent-object) with a user's preferences. The events are then sent downstream to any destinations in categories that a user consented to share data with.
+Segment captures and then enforces an end user's consent preferences. To collect your users' preferences, you must use a third-party consent management platform (CMP), like OneTrust.
+
+After a user sets their consent preferences, Segment updates the [consent object](#consent-object) with that information. The events are then sent downstream to any streaming destinations in categories that a user consented to share data with.
 
 > 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.
+If a user changes the categories they consent to or if they consent using a different device or identifier, any new events will contain the updated consent information. 
+
+<!--- rewrite above sentence. Also need to note that they need to make these changes available to Segment, new events are generated that will send updated consent--->
 
 For example: 
 
@@ -46,7 +50,11 @@ For example:
 }
 ```
 
-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.
+<!--- UNHIDE DURING PUBLIC BETA: Segment sends the information about their consent, using a [Track call](/docs/connections/spec/track), to your downstream destinations and storage destinations.
+
+This will be added to the profile and used in Engage for auditing purposes. Every message is stamped with preferences.
+
+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]() documentation. --->
 
 Consent information and a consent conflict flag are visible as traits on a user's profile in Unify.
 
@@ -55,15 +63,15 @@ Consent information and a consent conflict flag are visible as traits on a user'
 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:
 
 ```json
-context {
-		consentCategories {
-			"functional": true,
-			“advertising”: true,
-      "personalization": false
-		}
-	}
-```
+{
+  "categoryPreferences" : {
+    "Advertising": true,
+    "Analytics": false,
+    "Functional": true,
+    "DataSharing": false
+  }
+}
 
-<!-- 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.
+To learn more about configuring consent management in your workspace, see the [Configure Consent Management docs](/docs/src/privacy/configure-consent-management).

src/privacy/reconcile-consent.md

@@ -1,5 +1,6 @@
 ---
 title: Reconciling Consent Conflicts
+hidden: true
 ---
 
 Segment sends data only to destinations in categories consented to by the end user. When conflicts arise between the consent object and integrations object or your consent management tool, Segment reconciles consent according to the following tables.