Skip to content

Commit 36d7cd5

Browse files
authored
typo fix
1 parent ee1a766 commit 36d7cd5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Event-Triggered Journeys includes advanced options to help you tailor journey be
5555

5656
Unique identifiers in event-triggered journeys help you manage multiple journey instances when a user triggers the same event more than once.
5757

58-
When you select **Re-enter every time event occurs** when you create an event-triggered journeys, you can choose an event property as a unique identifier. Selecting this option does two things:
58+
When you select **Re-enter every time event occurs** when you create an event-triggered journey, you can choose an event property as a unique identifier. Selecting this option does two things:
5959

6060
- It creates a separate journey instance for each unique identifier value, allowing multiple instances to run in parallel for the same user.
6161
- It ensures that any follow-up events link back to the right journey instance, preserving context for tracking and personalization.
@@ -110,4 +110,4 @@ Start by setting the `checkout_started` event as the trigger and specify a uniqu
110110

111111
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.
112112

113-
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.
113+
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.

0 commit comments

Comments
 (0)