Skip to content

Commit 861a57d

Browse files
committed
final cleanup [netlify-build]
1 parent 474713a commit 861a57d

File tree

2 files changed

+4
-0
lines changed

2 files changed

+4
-0
lines changed

src/_data/sidenav/main.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -490,6 +490,8 @@ sections:
490490
title: Exit Rules
491491
- path: /engage/journeys/v2/journey-context
492492
title: Journey Context
493+
- path: /engage/journeys/v2/use-cases
494+
title: Use Cases
493495
- path: /engage/journeys/v2/limits
494496
title: Product Limits
495497
- path: '/engage/journeys/journeys-edits'

src/engage/journeys/v2/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,3 +216,5 @@ Start by setting the `checkout_started` event as the trigger and specify a uniqu
216216
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.
217217

218218
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.
219+
220+
For detailed instructions on setting up journeys for these use cases, see [Journeys (V2) Use Cases](/docs/engage/journeys/v2/use-cases)

0 commit comments

Comments
 (0)