Merge pull request #6106 from segmentio/consent-post-ga-updates

forstisabella · web-flow · commit cf07f5588908 · 2024-02-22T12:54:09.000-05:00
Post-GA Consent Mgmt items
diff --git a/src/privacy/consent-management/configure-consent-management.md b/src/privacy/consent-management/configure-consent-management.md
@@ -3,6 +3,7 @@ title: Configure Consent Management
 related:
   - "/privacy/consent-management/"
   - "/privacy/consent-management/consent-in-segment-connections/"
+  - "/privacy/consent-management/consent-in-unify/"
 redirect_from: "/privacy/configure-consent-management"
 ---
 
diff --git a/src/privacy/consent-management/consent-in-segment-connections.md b/src/privacy/consent-management/consent-in-segment-connections.md
@@ -3,6 +3,7 @@ title: Consent in Segment Connections
 related:
   - "/privacy/consent-management/"
   - "/privacy/consent-management/configure-consent-management/"
+  - "/privacy/consent-management/consent-in-unify/"
 redirect_from: "/privacy/consent-in-segment-connections"
 ---
 
diff --git a/src/privacy/consent-management/consent-in-unify.md b/src/privacy/consent-management/consent-in-unify.md
@@ -4,7 +4,7 @@ related:
   - "/privacy/consent-management/"
   - "/privacy/consent-management/configure-consent-management/"
   - "/privacy/consent-management/consent-in-segment-connections/"
-redirect_from: "/privacy/consent-in-unify/"
+redirect_from: "/privacy/consent-in-unify"
 ---
 
 > info "Consent in Unify and Twilio Engage is currently unavailable."
diff --git a/src/privacy/consent-management/index.md b/src/privacy/consent-management/index.md
@@ -3,6 +3,7 @@ title: Consent Management Overview
 related:
   - "/privacy/consent-management/configure-consent-management/"
   - "/privacy/consent-management/consent-in-segment-connections/"
+  - "/privacy/consent-management/consent-in-unify/"
 ---
 
 When an end user visits your web or mobile app, 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. Some common categories include personalization, advertising, and site performance.
diff --git a/src/protocols/faq.md b/src/protocols/faq.md
@@ -24,13 +24,16 @@ You can also use the Slack Actions destination to set event triggers for context
 
 ## Protocols Tracking Plan
 
+### What is the Segment Consent Preference Updated event, and who added it to my Tracking Plans?
+[Consent Management](/docs/privacy/consent-management) users see the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) event automatically added to all existing Tracking Plans after they create their first consent category, or when they create a new Tracking Plan after configuring Consent Management. Segment recommends that you do not remove this event.
+
 ### How do I add Page and Screen events to my Tracking Plan?
 
 To consolidate the views in the Schema tab, Segment automatically converts `page` and `screen` calls into `Page Viewed` and `Screen Viewed` events that appear in the Schema Events view. Segment recommends adding a `Page Viewed` or `Screen Viewed` event to your Tracking Plan with any properties you want to validate against. At this time, to validate that a specific named page/screen (`analytics.page('Homepage') | analytics.screen('Home')`) has a specific set of required properties, you will need to use the [JSON Schema](/docs/protocols/tracking-plan/create/#edit-underlying-json-schema).
 
 ### How can I see who made changes to my Tracking Plan?
 
-Each Tracking Plan includes a Changelog, which shows which changes were made by which users. To view it, open a Tracking Plan, click the **...** button (also known as the dot-dot-dot, or ellipses menu) next to the Edit Tracking Plan button, and click **View Changelog**.
+Each Tracking Plan includes a Changelog, which shows which changes were made by which users. To view it, open a Tracking Plan, click the **...** button (also known as the dot-dot-dot, or ellipses menu) next to the Edit Tracking Plan button, and click **View Changelog**. 
 
 ### How many Sources can I connect to a Tracking Plan?
 
diff --git a/src/protocols/tracking-plan/create.md b/src/protocols/tracking-plan/create.md
@@ -18,13 +18,19 @@ The Segment Tracking Plan feature allows you to validate your expected events ag
 
 Tracking Plans are stored in workspaces and can be connected to one or more Sources.
 
+> info "Segment Consent Preference Updated Event"
+> After setting up a consent category, users of Consent Management see a Segment Consent Preference Updated Event added to all existing Tracking Plans. 
+
 ## Create a Tracking Plan
 
 To create a new Tracking Plan:
 1. Contact your Segment account team to enable the Protocols features in your workspace.
 2. Once enabled, click **Protocols** in the left bar navigation.
 3. Click **New Tracking Plan**.
-4. Add events, properties, traits and filters in the Tracking Plan editor. <br> You'll see an option to import events and traits to your Tracking Plan that your source received in the last 24 hours, 7 days or 30 days. This option is great if you want to get started with your current events. 
+4. Add events, properties, traits and filters in the Tracking Plan editor. <br> You'll see an option to import events and traits to your Tracking Plan that your source received in the last 24 hours, 7 days or 30 days. This option is great if you want to get started with your current events.
+
+> info "Consent Management users see the Segment Consent Preference Updated event on new Tracking Plans"
+> If you are a Consent Management user and have created at least one consent category, Segment automatically adds the [Segment Consent Preference Updated event](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) to all new Tracking Plans. 
 
 ## Copy a Tracking Plan
 
@@ -62,7 +68,7 @@ To create a new Tracking Plan by uploading a CSV file:
 After uploading your CSV file, you are redirected to the Upload & Download History page while the upload is in progress. If the CSV upload fails, you'll be able to either view the error directly in the Reports column on the Upload & Download History page or download the `error_report.csv` file that corresponds to the Tracking Plan you uploaded. 
 
 > success ""
-> Tracking Plans created by an uploaded file are reflected in the [Audit Trail](docs/segment-app/iam/audit-trail/) and [Tracking Plan changelog](/docs/protocols/faq/#how-can-i-see-who-made-changes-to-my-tracking-plan).
+> Tracking Plans created by an uploaded file are reflected in the [Audit Trail](docs/segment-app/iam/audit-trail/) and [Tracking Plan changelog](/docs/protocols/faq/#how-can-i-see-who-made-changes-to-my-tracking-plan). If you are a Consent Management user and have created at least one consent category, Segment automatically adds the [Segment Consent Preference Updated event](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) to all new Tracking Plans. 
 
 ### Update an existing Tracking Plan
 
