adding to consent management overview, thinking through prereqs,

Author: forstisabella

src/privacy/configure-consent-management.md

@@ -4,8 +4,29 @@ 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.
 
-## Step 1: 
+<!--- note to include: how to find your category ID in tools other than onetrust-->
 
-## Step 2: 
+## 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.
+- **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.
+
+> 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 conflicted 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.
+
+## Step 1: Access the Consent Management feature
+
+## Step 2: Create consent categories 
+
+> info "Segment recommends mapping all destinations to a category"
+> Each destination should be mapped to a category <!---why though?---> to ensure completeness of data in your downstream destinations. Any destination that doesn't have a mapping will not receive events with a consent object. 
+
+## Step 3: 
 
 ## Ingesting consent data

src/privacy/consent-management.md

@@ -1,9 +1,38 @@
 ---
 title: Consent Management Overview
+related:
+  - "/privacy/account-deletion/"
+  - "/privacy/complying-with-the-gdpr/"
 ---
 > 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.
 
-## Consent preferences
+Consent management is a [description]
 
-## Consent object
+> warning "Website sources and event streaming destinations are available to map to consent categories"
+> During the private beta, you can map website sources and event streaming destinations to a consent category. All other sources and destinations will not be affected by consent mappings.
+
+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 (for example, personalization, advertising, and site performance) that describe how your company intends to use that data.
+
+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 consented to by the user.
+
+> success ""
+> Segment collects consent for both registered users and anonymous users.
+
+If a **consent conflict** exists <!-- expand on this better lmao---> Segment resolves them according to the [Enforce Consent](/docs/privacy/enforce-consent) documentation.
+
+## Consent object
+
+Segment requires every event from all of your sources to include the end-user consent preferences, captured by your consent management tool, 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
+		}
+	}
+```
+
+The Segment consent object is 

src/privacy/enforce-consent.md

@@ -2,15 +2,18 @@
 title: Enforce Consent
 ---
 
-Segment sends data only to destinations in categories the end user has consented to sending data to.
+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.
 
 > 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.
 
+## Reconcile consent category trait conflicts
+
+Segment detects when there are conflicting consent categories for a user and 
+
 ## Reconcile consent object and integrations object conflicts
 
-### Integrations object
-The Integrations object is a JSON object you can add to your Segment payloads to control how Segment routes data to your destinations. The Integrations object filters `track`, `page`, `group`, `identify` and `screen` events from client and cloud based sources, and routes or prevents them from going to listed destinations.
+You can add the integrations object and the consent object to your Segment payloads to control how Segment routes data to your downstream destination. 
 
 > success " "
 > For more information about the Integrations object, please see [Filtering your Segment Data](/docs/guides/filtering-data/#filtering-with-the-integrations-object).
@@ -26,6 +29,7 @@ If the consent object and integrations object have conflicting destination infor
 | `{ad: true,` <br>`analytics: false}`<br> <br>//ad = facebook, google ads                                        | `{facebook: false,`<br>`amplitude: false}`  | Message delivered to all ad destinations (Google Ads) but NOT to Facebook. <br> No data delivered to analytics destinations |
 | `{ad: true,` <br>`analytics: false}`<br> <br>//ad = facebook, google ads <br> //analytics = facebook, snowflake |  `{facebook: false,`<br>`amplitude: false}` | Message delivered to all ad destinations (even though Facebook belongs to analytics and user is not consenting to analytics.) Use metadata if provided for Facebook (current behavior)<br>No data delivered to analytics destinations (Snowflake) |
 
+
 ## Reconcile Consent Management tool and Segment tool conflicts
 
 If there is a mismatch in consent categories between your consent management tool and the Segment app, Segment reconciles the consent object according to the following table: