Merge branch 'master' into digioh-oauth-flow

pauljaeinyoo · web-flow · commit 5f155b79cc4d · 2021-06-14T10:26:10.000-06:00
diff --git a/src/_data/products.yml b/src/_data/products.yml
@@ -106,3 +106,11 @@ items:
     team: true
     business: false
     add-on: false
+- product_display_name: Journeys
+  slug: journeys
+  plan-note: "Journeys is available to Personas Advanced customers"
+  plans:
+    free: false
+    team: false
+    business: true
+    add-on: true
diff --git a/src/connections/destinations/catalog/braze/index.md b/src/connections/destinations/catalog/braze/index.md
diff --git a/src/connections/destinations/catalog/google-analytics/ga4-plans.md b/src/connections/destinations/catalog/google-analytics/ga4-plans.md
@@ -6,7 +6,7 @@ strat: google
 Google introduced the new version of Google Analytics, called Google Analytics 4 (GA4), in October 2020. GA4 has some distinct differences from Universal Analytics (UA), which are important to understand before considering migration and the data schema changes that might require.
 
 > success ""
-> Segment expects to release a beta GA4 destination in early 2021. If you are interested in being a beta tester, please complete this short [questionnaire](https://forms.gle/Tt5T6S4eX7Tcaqin6) and someone will be in touch with next steps.
+> Segment expects to release a beta GA4 destination in Q3 2021. Fill out the Segment GA4 [Beta Sign-up Form](https://forms.gle/WzC1dsbxmNVDsYNJ6) to be notified when the destination is available.
 
 We’ll update this page to share the latest on our GA4 destination.
 
@@ -30,12 +30,12 @@ GA4’s out-of-the-box reports are different from UA’s. GA4’s reporting is m
 
 You might not be able to perfectly recreate your UA reports in GA4. One approach is to send your data to both UA and GA4 while you build out your new reports in GA4, and improve those reports over time. Once you are satisfied that your GA4 reports meet your needs, you can gradually migrate away from using the original reporting in UA.
 
+GA4 requires that you use GA4’s recommended events and properties in order to get the new reports. Segment’s GA4 destination will automatically map your Segment spec events to the corresponding recommended GA4 events and properties. If your events do not follow the Segment spec exactly, don’t worry; you’ll be able to modify the mappings. You can also create custom events and properties.
 
-## Client-based or server-based
 
-GA4 is only available using a device-mode (client-based) SDK  such as `gtag.js`, Firebase, and Google Tag Manager. The [Measurement Protocol](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=gtag#send_an_event) that enables server-to-server data syncing for GA4 properties is [currently in alpha](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=gtag#send_an_event).
+## Cloud Mode (Server-based) first
 
-Segment plans to support Device Mode and Cloud Mode for GA4. Availability will depend on the Google Analytics roadmap and our assessment of the stability of these APIs.
+Segment will start by supporting Cloud-mode for GA4. Note that the [Measurement Protocol](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=gtag#send_an_event) that enables server-to-server data syncing for GA4 properties is [currently in alpha](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=gtag#send_an_event).
 
 ## Switching to GA4
 
diff --git a/src/personas/journeys/build-journey.md b/src/personas/journeys/build-journey.md
@@ -1,6 +1,7 @@
 ---
 title: Build a Journey
 ---
+{% include content/plan-grid.md name="journeys" %}
 
 Follow along for the steps required to create a new Journey.
 
diff --git a/src/personas/journeys/faq-best-practices.md b/src/personas/journeys/faq-best-practices.md
@@ -1,6 +1,9 @@
 ---
 title: Journeys Best Practices and FAQ
 ---
+{% include content/plan-grid.md name="journeys" %}
+
+
 ## Best practices
 
 ### Enforce exclusivity in multi-branch splits
@@ -46,3 +49,6 @@ Once published, Journeys displays the number of users are in each step of the Jo
 ### How are users sent to downstream destinations?
 
 The data type you send to a destination depends on whether the destination is an Event Destination or a List Destination. 
+
+### Which roles can access Journeys?
+For Personas Advanced customers, users with either the Personas User or Personas Admin roles can create, edit, and delete journeys. Users with the Personas Read-only role are restricted to view-only access.
diff --git a/src/personas/journeys/index.md b/src/personas/journeys/index.md
@@ -1,6 +1,8 @@
 ---
 title: Journeys Overview
 ---
+{% include content/plan-grid.md name="journeys" %}
+
 
 Journeys, a feature of Segment Personas, provides a way for marketers to personalize experiences through planning how and when to engage customers with the right campaigns and messages.
 
diff --git a/src/personas/journeys/key-terms.md b/src/personas/journeys/key-terms.md
@@ -2,6 +2,9 @@
 title: Journeys Key Terms
 ---
 
+{% include content/plan-grid.md name="journeys" %}
+
+
 Keep the following terms in mind as you begin to explore Journeys.
 
 ## General
diff --git a/src/personas/journeys/send-data.md b/src/personas/journeys/send-data.md
@@ -1,6 +1,8 @@
 ---
 title: Send Journeys data to a Destination
 ---
+{% include content/plan-grid.md name="journeys" %}
+
 
 When you send data to destinations, you send a series of events or user lists, depending on the destination type.
 
diff --git a/src/personas/journeys/use-cases.md b/src/personas/journeys/use-cases.md
@@ -2,6 +2,8 @@
 title: Example Journeys Use Cases
 ---
 
+{% include content/plan-grid.md name="journeys" %}
+
 To help you get underway, you can reference these sample Journeys.
 
 ## E-commerce use cases
diff --git a/src/segment-app/iam/roles.md b/src/segment-app/iam/roles.md
@@ -72,17 +72,17 @@ Read access to all Tracking Plans in Protocols.
 
 #### Personas Admin
 
-Edit access to assigned Personas Space(s), including all audiences and computed traits. Personas admins can update settings from the Personas screens of the Segment App.
+Edit access to assigned Personas Space(s), including all audiences and computed traits. Personas admins can update settings from the Personas screens of the Segment App. For Personas Advanced customers, Personas Admins can create, edit, and delete Journeys.
 
 **Scope:** Can be granted access to either: all current and future Spaces, or a specific list of Spaces, or Spaces with a specific Label (BT only).
 
 #### Personas User
-Edit access to all traits and audiences within assigned Personas Space(s). Cannot change settings in Personas.
+Edit access to all traits and audiences within assigned Personas Space(s). Cannot change settings in Personas. For Personas Advanced customers, Personas Users can create, edit, and delete Journeys.
 
 **Scope:** Can be granted access to either: all current and future Spaces, or a specific list of Spaces, or Spaces with a specific Label (BT only).
 
 #### Personas Read-only
-Read-only access to assigned Personas Space(s), including all audiences and computed traits.
+Read-only access to assigned Personas Space(s), including all audiences and computed traits. For Personas Advanced customers, Personas Read-only users can view Journeys.
 
 **Scope:** Can be granted access to either: all current and future Spaces, or a specific list of Spaces, or Spaces with a specific Label (BT only).
 
