Skip to content

Commit 787575c

Browse files
committed
add information on unique identifiers
1 parent 1ee9470 commit 787575c

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

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

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,20 @@ To set up an Event-triggered Journey:
3737
5. Configure entry rules:
3838
- **Re-enter every time event occurs** (default): Users enter the journey each time they trigger the specified event.
3939
- **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.
40+
6. **If you chose Re-enter every time event occurs in Step 5**, select a [unique identifier](#unique-identifiers).
4141
7. Configure event delivery to destinations by selecting a destination or setting up a custom destination function.
4242
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.
43+
9. After you've finished setting up your journey, click **Publish**, then click **Publish** again in the popup.
44+
45+
## Working with Event-trigged Journeys
46+
47+
#### Unique identifiers
48+
49+
Unique identifiers in Event-triggered Journeys help you manage multiple journey instances when a user triggers the same event more than once.
50+
51+
You can configure unique identifiers if you select **Re-enter every time event occurs** when you create an event-triggered journey. Choose an event property as the unique identifier to ensure downstream events link back to the right journey instance.
52+
53+
By defining an identifier, you ensure that follow-up events within the journey get matched to the correct instance, preserving context for tracking and personalization.
54+
55+
For example, in an abandonment journey, suppose a user starts two applications (like `application_started`), each with a different `application_id`. By setting `application_id` as the unique identifier, Segment can match follow-up events (like `application_completed`) to the correct application journey. This way, each journey instance only receives the completion event for its specific application.
56+

0 commit comments

Comments
 (0)