init GA docs

Author: forstisabella

src/_data/sidenav/main.yml

@@ -506,6 +506,16 @@ sections:
       title: Complying With GDPR
     - path: /privacy/user-deletion-and-suppression
       title: User Deletion and Suppression
+  - section_title: Consent Management
+    slug: /privacy/consent-management
+    expanded: true
+    section:
+      - path: /privacy/consent-management/consent-management
+        title: Consent Management Overview
+      - path: /privacy/consent-management/consent-in-segment-connections
+        title: Consent in Segment Connections
+      - path: /privacy/consent-management/configure-consent-management
+        title: Configure Consent Management
   - path: /privacy/account-deletion
     title: Account & Data Deletion
   - path: /privacy/hipaa-eligible-segment

src/connections/delivery-overview.md

@@ -24,7 +24,7 @@ The pipeline view shows the following steps:
 - **Successfully received**: Events that Segment ingested from your source
 - **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules
 - **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) Tracking Plans
-- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. <!--- Beta users of [Consent Management](/docs/privacy/consent-management/) also see events discarded due to consent preferences.--->
+- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. Users of [Consent Management](/docs/privacy/consent-management/) also see events discarded due to consent preferences.
 - **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements
 - **Successful delivery**: Events that were successfully delivered to the destination
 

src/privacy/configure-consent-management.md renamed to src/privacy/consent-management/configure-consent-management.md

@@ -5,6 +5,7 @@ related:
   - "/privacy/consent-management/"
   - "/privacy/consent-in-segment-connections/"
   - "/privacy/consent-in-unify/"
+redirect_from: "/privacy/configure-consent-management/"
 ---
 > info "Consent Management is in private beta"
 > This means that 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.
@@ -52,6 +53,7 @@ Segment provides a OneTrust wrapper for the following sources:
 - **Analytics.js**: Please follow the instructions from the README in the [@segment/analytics-consent-wrapper-onetrust](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} repository.
 - **Kotlin**: Please follow the instructions from the README in the [@segment-integrations/analytics-kotlin-consent](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"} repository.
 - **Swift**: Please follow the instructions from the README in the [@segment-integrations/analytics-swift-consent](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"} repository.
+- **React Native**: Please follow the instructions from the README in the [](){:target="_blank"} repository.
 
 If you'd like to integrate with any other CMP, Segment requires you to build your own wrapper or use any mechanism provided it meets the above requirements of data and event generation.
 

src/privacy/consent-in-segment-connections.md renamed to src/privacy/consent-management/consent-in-segment-connections.md

@@ -1,15 +1,12 @@
 ---
 title: Consent in Segment Connections
-hidden: true
 related:
   - "/privacy/consent-management/"
   - "/privacy/configure-consent-management/"
   - "/privacy/consent-in-unify/"
+redirect_from: "/privacy/consent-in-segment-connections/"
 ---
 
-> info "Consent Management is in private beta"
-> This means that 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 Connections users can add the [consent object](#consent-object) to their sources to stamp events with the end user consent preferences captured by your consent management platform (CMP) and send them downstream to destinations in categories that an end user consented to share data with. Events without the consent object continue to flow to destinations without consent enforcement. 
 
 For more information about configuring consent categories, see the [Configure Consent Management](/docs/privacy/configure-consent-management/#step-1-create-consent-categories-in-the-segment-app) documentation.

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

@@ -5,6 +5,7 @@ related:
   - "/privacy/consent-management/"
   - "/privacy/configure-consent-management/"
   - "/privacy/consent-in-segment-connections/"
+redirect_from: "/privacy/consent-in-unify/"
 ---
 
 > info "Consent in Unify and Twilio Engage is currently unavailable."

src/privacy/consent-management.md renamed to src/privacy/consent-management/consent-management.md

@@ -14,7 +14,7 @@ When an end user visits your web or mobile app, they set **consent preferences**
 
 Segment integrates with your commercial third-party or bespoke consent management platform (CMP) that captures an end user's consent preferences and enforces those preferences by only routing events to the categories consented to by an end user.
 
-![Diagram outlining information flowing from an end user to Segment destinations](/docs/privacy/images/consent-overview.png)
+![Diagram outlining information flowing from an end user to Segment destinations](/images/consent-overview.png)
 
 After a user sets their consent preferences on your web or mobile app, Segment requires you to add the [consent object](/docs/privacy/consent-in-segment-connections/#consent-object) to all events. If you are using OneTrust, Segment provides a wrapper for your web and mobile libraries that can add the consent object to your events. If you are using another CMP, you are required to add the consent object to your events by either creating your own wrapper or using another mechanism. For more information, see the [Configure Consent Management documentation](/docs/privacy/configure-consent-management/#step-2-integrating-your-cmp-with-segment).