Skip to content

Commit 78495bf

Browse files
committed
add screenshot [netlify-build]
1 parent 4df27ec commit 78495bf

File tree

2 files changed

+105
-0
lines changed

2 files changed

+105
-0
lines changed
154 KB
Loading

src/engage/journeys/v2/use-cases.md

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,3 +7,108 @@ Event-Triggered Journeys give you the tools to create real-time, personalized fl
77

88
Each example includes a short explanation, key steps to configure, and optional sample event payloads.
99

10+
## Real-time event forwarding
11+
12+
Send a confirmation message immediately after a user takes a key action, like placing an order or submitting a form. This type of journey helps reinforce trust and provides instant feedback by delivering personalized messages based on event details.
13+
14+
This use case is ideal for transactional events that should trigger follow-up communication without delay.
15+
16+
### How to build this journey
17+
18+
1. Set the journey entry condition to `Users perform an event`.
19+
2. Choose the event that represents the user action (for example, `Order_Confirmation`).
20+
3. **(Optional)**: Add event property filters if you only want to trigger the journey under specific conditions.
21+
4. Click **Build**, then add a **Send to Destination** step to forward the event.
22+
5. Configure destination:
23+
- Select the destination you want to send the payload to.
24+
- Enrich the payload with profile traits or journey context as needed.
25+
6. Click **Save** to publish the journey.
26+
27+
The following example shows a `Order_Confirmation` event payload that could trigger this journey. You can customize the event name and properties based on your use case.
28+
29+
```json
30+
{
31+
"userId": "99",
32+
"context": {},
33+
"integrations": {},
34+
"event": "Order_Confirmation",
35+
"properties": {
36+
"productId": "001",
37+
"productName": "T-Shirt",
38+
"productColor": "green",
39+
"productSize": "Large",
40+
"productPrice": "$55.34",
41+
"event_location": "A",
42+
"cart_ID": "123456",
43+
"scenario": "01 Ordered Product"
44+
}
45+
}
46+
```
47+
48+
## Application abandonment campaign
49+
50+
Send a personalized nudge when a user starts an action (like filling out an application) but doesn’t complete it within a certain time window. This type of journey helps recover drop-offs by checking for a completion event and following up only if it's missing.
51+
52+
This use case is ideal for flows like job applications, signups, demo requests, or onboarding forms.
53+
54+
### How to build this journey
55+
56+
1. Set the journey entry condition to `Users perform an event`.
57+
2. Choose the event that indicates the user started the flow (for example, `Application_Started`).
58+
3. (Optional): Add event property filters if you only want to trigger the journey under specific conditions.
59+
4. Click **Build**, then add a **Hold Until** step.
60+
5. In the Hold Until step:
61+
- Specify the completion event (for example, `Application_Completed`) as the condition.
62+
- Set a maximum hold duration.
63+
6. Add a **Send to Destination** step on the "timeout" branch to send a follow-up message.
64+
7. Configure the destination:
65+
- Select the destination you want to send the payload to.
66+
- Enrich the payload with profile traits or journey context as needed.
67+
8. Preview the payload that Segment will send to your destination.
68+
9. Publish the journey.
69+
70+
![Screenshot of the journey setup screen showing the Application_Started entry event selected, with re-entry enabled and Application_id set as the unique identifier.](../images/application_started.png)
71+
72+
73+
### Sample entry and evaluation events
74+
75+
The following example shows both the entry event that starts the journey and the evaluation event that cancels the nudge if the user completes the application.
76+
77+
{% codeexample %}
78+
{% codeexampletab Entry event %}
79+
```json
80+
{
81+
"userId": "88",
82+
"context": {},
83+
"integrations": {},
84+
"event": "Application_Started",
85+
"properties": {
86+
"Category": "A",
87+
"Tier": "Premium",
88+
"VIP": true,
89+
"Application_id": "1234",
90+
"scenario": "Trigger campaign with Application Started"
91+
}
92+
}
93+
```
94+
{% endcodeexampletab %}
95+
96+
{% codeexampletab Evaluation event %}
97+
```json
98+
{
99+
"userId": "88",
100+
"context": {},
101+
"integrations": {},
102+
"event": "Application_Completed",
103+
"properties": {
104+
"Category": "A",
105+
"Tier": "Premium",
106+
"VIP": true,
107+
"Application_id": "1234",
108+
"scenario": "Complete campaign without a nudge b/c Application was Completed"
109+
}
110+
}
111+
```
112+
{% endcodeexampletab %}
113+
{% endcodeexample %}
114+

0 commit comments

Comments
 (0)