update faq fix redirect [netlify-build]

Author: forstisabella

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."

src/protocols/faq.md

@@ -24,6 +24,9 @@ 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).