Skip to content

Commit 1ee9470

Browse files
committed
add structure and first few sections
1 parent 6154f28 commit 1ee9470

File tree

1 file changed

+43
-0
lines changed

1 file changed

+43
-0
lines changed
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
title: Event-Triggered Journeys
3+
plan: engage-foundations
4+
---
5+
6+
With Event-triggered Journeys, you can build real-time, event-based marketing workflows to automate and personalize customer journeys.
7+
8+
Unlike traditional audience-based journeys that rely on pre-defined user segments, these journeys start automatically when users perform specific actions on your website or app.
9+
10+
On this page, you'll learn how to create an Event-triggered Journey, configure entry conditions, and apply best practices.
11+
12+
## Overview
13+
14+
Event-triggered Journeys help you create a responsive approach for time-sensitive use cases, like cart abandonment campaigns and transactional messages. Where audience-based journeys activate based on aggregated conditions, Event-triggered Journeys respond instantly to individual events, delivering personalized experiences based on the full context of each event.
15+
16+
Opt for an event-triggered journey in situations like these:
17+
18+
- When campaigns require real-time action in response to user behavior.
19+
- For transactional messages (like receipts and confirmations) that require specific event-based triggers.
20+
- In abandonment campaigns where a follow-up is needed if a corresponding completion event doesn’t occur.
21+
22+
## Build an Event-triggered Journey
23+
24+
Before you begin building an Event-triggered Journey, make sure that:
25+
26+
- You've enabled all [destinations](/docs/connections/destinations/) intended for event delivery in [Connections](/docs/connections/).
27+
- The events you want to use as triggers are already available in your Segment workspace.
28+
29+
To set up an Event-triggered Journey:
30+
31+
1. In your Segment workspace, navigate to **Engage > Journeys**, then click **+ Create journey**.
32+
2. On the **Create journey** page, select **User performs an event**, then click **Next**.
33+
3. Give your new journey a name and, optionally, a description.
34+
4. Select entry event:
35+
- Choose the event that will trigger user entry into the journey.
36+
- (Optional:) Apply filters based on event property values to refine entry conditions. For example, enter only if `{property} = value A, value B, or value C`.
37+
5. Configure entry rules:
38+
- **Re-enter every time event occurs** (default): Users enter the journey each time they trigger the specified event.
39+
- **Enter one time**: Users enter the journey once only, regardless of repeated event triggers.
40+
6. **If you chose Re-enter every time event occurs in Step 5**, select a unique identifier.
41+
7. Configure event delivery to destinations by selecting a destination or setting up a custom destination function.
42+
8. Preview the contextual payload that Segment will send to your destination(s).
43+
9. After you've finished setting up your journey, click **Publish**, then click **Publish** again in the popup.

0 commit comments

Comments
 (0)