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.

src/engage/journeys/send-data.md renamed to src/engage/journeys/v1/send-data.md

@@ -1,6 +1,8 @@
 ---
 title: Event-Triggered Journeys
 plan: engage-foundations
+redirect_from:
+  - "/engage/journeys/event-triggered-journeys"
 ---
 
 With Event-Triggered Journeys, you can build real-time, event-based marketing workflows to automate and personalize customer journeys. 
@@ -96,6 +98,44 @@ For example, in an abandonment journey, suppose a user starts two applications (
 - **Supported destinations:** Only Actions Destinations in the Segment catalog are supported.  
 - **Data mapping:** Ensure all required keys for the destination are properly mapped to avoid errors.
 
+## Duplicate a journey
+
+To save time and avoid recreating steps from scratch, you can duplicate any existing journey.
+
+Duplicating a journey creates a copy of the configuration and opens it in **Draft** mode. You can duplicate both draft and published journeys, but journey names must be unique.
+
+### What gets copied
+
+When you duplicate a journey, Segment copies the following:
+
+- Entry conditions and filters  
+- All journey steps and structure  
+- Destination actions, including:
+  - Event names
+  - Payload configuration
+  - Trait and context enrichment
+  - Attribute mappings
+
+Segment **doesn't** copy the following:
+
+- Journey name (you must enter a new, unique name)
+- Activation destination keys (Segment will regenerate these)
+
+> warning ""
+> If a destination action was disabled in the original journey, it will be enabled by default in the duplicated version.
+
+### How to duplicate a journey
+
+1. Go to **Engage > Journeys** and find the journey you want to duplicate.
+2. Click the **•••** (Options menu), either in the list view or from within the journey.
+3. Select **Duplicate**.
+4. Enter a new name when prompted.
+5. Review the duplicated journey and make any needed changes.
+6. If your journey includes destination sends, be sure to copy the new destination keys into your destination system.
+
+> warning
+> Currently, you can only duplicate journeys within the same Engage space. Duplicating across spaces or workspaces is not supported.
+
 ## Best practices
 
 Follow the best practices in this table to optimize your event-triggered journeys:
@@ -115,9 +155,8 @@ Segment built Event-Triggered Journeys to respond instantly to events, offering
 - **Entry event requirements**: The entry event you use must already exist in your Segment workspace for it to appear as a selection in journey setup. Make sure that you've already created the event before setting up your journey.
 - **Event property filters**: You can filter event properties using the `equals` or `equals any of` operators. When you apply multiple conditions, filters operate with `AND` logic, meaning all conditions must be true for the event to trigger entry into the journey.
 - **Audience filtering**: You can only use active, pre-existing audience records as filters. For more complex filtering, like specific profile traits or multiple audiences, first [create the audience](/docs/engage/audiences/#building-an-audience) in **Engage > Audiences**, then apply it as a filter once it’s live.
-- **Destination options**: While Event-Triggered Journeys support all [actions-based destinations](/docs/connections/destinations/actions/) and Destination Functions, you can only add one destination per Send to Destination step. If you need to send to multiple destinations, you can use multiple Send to Destination steps.
+- **Destination options**: Event-Triggered Journeys support all [actions-based destinations](/docs/connections/destinations/actions/) and Destination Functions.
 - **Event payload structure**: Each payload sent to a destination includes a unique key to identify the specific send step within the journey, rather than the journey instance itself. You can also set a custom event name to make it easier to identify the specific event instance you want to track in your destination.
-- **Editing and versioning**: After you publish an event-triggered journey, you won't be able to edit it. To modify a journey, create a new journey. 
 - **Real-time delivery**: Event-Triggered Journeys aim for an expected delivery time of under 5 minutes from the moment an event is performed to when the payload reaches the destination, assuming there is no delay step in the journey. However, external factors outside of Segment's control may occasionally introduce latency.
 
 ## Observability
@@ -176,3 +215,5 @@ Start by setting the `checkout_started` event as the trigger and specify a uniqu
 Say you want to follow up with users after they engage with specific content, like downloading an e-book or watching a demo video. Event-Triggered Journeys can help you send timely, personalized messages based on these interactions.
 
 To do this, set the entry event to `content_downloaded` or `video_watched` and configure the journey to send a follow-up email. You could even personalize the email with details from the triggering event, like the content title or timestamp, by configuring your destination payload to enrich the message with event-specific context.
+
+For detailed instructions on setting up journeys for these use cases, see [Journeys (V2) Use Cases](/docs/engage/journeys/v2/use-cases)

src/engage/journeys/step-types.md renamed to src/engage/journeys/v1/step-types.md

@@ -1,6 +1,8 @@
 ---
 title: Journey Context
 plan: engage-foundations
+redirect_from:
+  - "/engage/journeys/journey-context"
 ---
 
 [Event-Triggered Journeys](/docs/engage/journeys/event-triggered-journeys/) redefine how you orchestrate and personalize customer experiences.