Skip to content

Commit 746f126

Browse files
authored
Merge pull request #7696 from segmentio/remove-v2-journeys-beta-alerts
Delete Event-Triggered Journeys beta alerts [DOC-1138]
2 parents c757ec8 + d89fd43 commit 746f126

File tree

4 files changed

+0
-12
lines changed

4 files changed

+0
-12
lines changed

src/engage/journeys/event-triggered-journeys-steps.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@ plan: engage-foundations
77

88
Steps are the building blocks of a journey. This page explains the **Hold Until**, **Send to Destination**, and **Data split** steps, which enable precise control over journey progression and data delivery.
99

10-
> info "Public Beta"
11-
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
12-
1310
## Hold Until: smart pauses in journeys
1411

1512
The **Hold Until** step adds a deliberate pause in a journey, waiting for specific user actions or a predefined time limit before progressing. This lets you create highly personalized experiences by responding to user behavior (or the lack thereof) at the right moment.

src/engage/journeys/event-triggered-journeys.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,6 @@ Unlike traditional audience-based journeys that rely on pre-defined user segment
99

1010
On this page, you'll learn how to create an event-triggered journey, configure entry conditions, and work with published event-triggered journeys.
1111

12-
> info "Public Beta"
13-
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
14-
1512
## Overview
1613

1714
Event-triggered journeys help you create a responsive approach for time-sensitive use cases, like cart abandonment campaigns and transactional messages.

src/engage/journeys/exit-rules.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@ Journey exit rules automatically remove users from a journey when they meet spec
77

88
This page explains how exit rules work, how to configure them, when to use them, and how to track exits in your journey analytics. You'll also find example use cases, best practices, and key behavior notes to help you get started.
99

10-
> info "Public Beta"
11-
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
12-
1310
## How exit rules work
1411

1512
Segment continuously evaluates exit rules as users move through a journey. If a user performs an event that matches one of the configured rules, they exit immediately from their current step.

src/engage/journeys/journey-context.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@ plan: engage-foundations
77

88
This page explains Journey context, which can help you dynamically adapt each journey to individual user interactions, creating highly relevant, real-time workflows.
99

10-
> info "Public Beta"
11-
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
12-
1310
## Overview
1411

1512
Unlike traditional audience-based journeys, which rely solely on user progress through predefined steps, event-triggered journeys capture and store the details of user-triggered events. This shift allows you to access the data that caused users to reach a specific step and use it to make more precise decisions throughout the journey.

0 commit comments

Comments
 (0)