Merge pull request #7701 from segmentio/evt-journeys-ga

Event-Triggered Journeys/Journeys V2 GA

Author: pwseg

src/_data/sidenav/main.yml

@@ -470,29 +470,36 @@ sections:
     section:
     - path: '/engage/journeys'
       title: Journeys Overview
-    - path: '/engage/journeys/build-journey'
-      title: 'Build a Journey'
-    - path: '/engage/journeys/step-types'
-      title: 'Journey Step Types'
-    - path: '/engage/journeys/journeys-edits'
-      title: 'Journey Edits and Versioning'
-    - path: '/engage/journeys/send-data'
-      title: Send Data to Destinations
-    - path: '/engage/journeys/journeys-analytics'
-      title: Journeys Analytics
-    - section_title: Event-Triggered Journeys
-      slug: '/engage/journeys/event-triggered-journeys'
+    - section_title: Journeys V1
+      slug: '/engage/journeys/v1'
+      section: 
+      - path: '/engage/journeys/v1/build-journey'
+        title: 'Build a Journey'
+      - path: '/engage/journeys/v1/step-types'
+        title: 'Journey Step Types'
+      - path: '/engage/journeys/v1/send-data'
+        title: Send Data to Destinations
+    - section_title: Journeys V2
+      slug: '/engage/journeys/v2'
       section: 
-      - path: /engage/journeys/event-triggered-journeys
+      - path: /engage/journeys/v2/
         title: Overview
-      - path: /engage/journeys/event-triggered-journeys-steps
+      - path: /engage/journeys/v2/event-triggered-journeys-steps
         title: Event-Triggered Journeys Steps
-      - path: /engage/journeys/journey-context
+      - path: /engage/journeys/v2/exit-rules
+        title: Exit Rules
+      - path: /engage/journeys/v2/journey-context
         title: Journey Context
+      - path: /engage/journeys/v2/use-cases
+        title: Use Cases
+      - path: /engage/journeys/v2/limits
+        title: Product Limits
+    - path: '/engage/journeys/journeys-edits'
+      title: 'Journey Edits and Versioning'
+    - path: '/engage/journeys/journeys-analytics'
+      title: Journeys Analytics
     - path: '/engage/journeys/faq-best-practices'
       title: Journeys Best Practices and FAQ
-    - path: '/engage/journeys/use-cases'
-      title: Example Journeys Use Cases
     - path: '/engage/journeys/journeys-logic'
       title: Understand Journeys Logic
     - path: '/engage/journeys/key-terms'

src/engage/journeys/images/application_started.png

@@ -1,6 +1,7 @@
 ---
 title: Example Journeys Use Cases
 plan: engage-foundations
+hidden: true
 redirect_from:
   - "/personas/journeys/use-cases"
 ---

src/engage/journeys/images/cart_abandonment.png

@@ -3,6 +3,7 @@ title: Build a Journey
 plan: engage-foundations
 redirect_from:
   - "/personas/journeys/build-journey"
+  - "/engage/journeys/build-journey"
 ---
 
 ## Before you begin

src/engage/journeys/images/multi_step_loopback.png

@@ -3,6 +3,7 @@ title: Send Journeys data to a Destination
 plan: engage-foundations
 redirect_from:
   - '/personas/journeys/send-data'
+  - '/engage/journeys/send-data'
 ---
 
 When you send data to destinations, you send a series of events or user lists, depending on the destination type.

src/engage/journeys/use-cases.md

@@ -1,6 +1,8 @@
 ---
 title: Journeys Step Types
 plan: engage-foundations
+redirect_from:
+  - "/engage/journeys/step-types"
 ---
 
 On this page, you'll find information about the steps you can add to a Journey.

src/engage/journeys/build-journey.md renamed to src/engage/journeys/v1/build-journey.md

@@ -1,6 +1,8 @@
 ---
 title: Event-Triggered Journeys Steps
 plan: engage-foundations
+redirect_from:
+  - "/engage/journeys/event-triggered-journeys-steps"
 ---
 
 [Event-Triggered Journeys](/docs/engage/journeys/event-triggered-journeys/) in Engage use steps to control how users move through a journey based on their actions or predefined conditions.
@@ -195,25 +197,25 @@ Segment evaluates each journey instance independently. This means a user could b
 
 You can configure a Randomized Split step with the following options:
 
-| Setting                      | Description                                                                  |
-| ---------------------------- | ---------------------------------------------------------------------------- |
-| Branches                     | Add up to five branches. Each branch must be assigned a percentage.          |
-| Distribution percentages     | Define what portion of users should go down each branch. Total must be 100%. |
-| Branch naming                | Branches are labeled alphabetically (for example, Branch A, Branch B).       |
-| Consistent branch assignment | Optionally ensure a user always enters the same branch on re-entry.          |
+| Setting                  | Description                                                                  |
+| ------------------------ | ---------------------------------------------------------------------------- |
+| Branches                 | Add up to five branches. Each branch must be assigned a percentage.          |
+| Distribution percentages | Define what portion of users should go down each branch. Total must be 100%. |
+| Branch naming            | Branches are labeled alphabetically (for example, Branch A, Branch B).       |
+| Assign same branch       | Optionally ensure a user always enters the same branch on re-entry.          |
 
-Segment won't publish your journey if the percentages don’t add up to 100%, or if any percentage is left blank.
+Segment won't let you save or publish your journey if the percentages don’t add up to 100%, or if any percentage is left blank.
 
-> info "Branch assignment is random"  
-> The Randomized Split step uses probabilistic logic to assign users to branches. At lower volumes, actual distribution may not exactly match your configured percentages, but it tends to even out at scale.
+> info "Actual branch counts may differ from percentages"  
+> The Randomized Split step assigns users to branches based on probability, not fixed rules. At lower volumes, the actual distribution may not match your configured percentages exactly, but results typically even out with more traffic.
 
 To add a Randomized Split to your journey:
 
 1. From the journey canvas, click **+** to add a new step.
 2. Select **Randomized Split**.
 3. Give the step a unique name.
 4. Add up to five branches and assign a percentage to each one.
-5. (Optional) Enable **Keep branch assignment consistent** if you want users to always go down the same branch on re-entry.
+5. (Optional) Enable **Assign same branch** if you want users to always go down the same branch on re-entry.
 6. Click **Save**.
 
 Once configured, Segment routes profiles through this step based on your distribution settings.