Skip to content

Commit b6b10a2

Browse files
authored
remove reference to context features not yet released
1 parent ff51e2e commit b6b10a2

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/engage/journeys/journey-context.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ This page explains Journey context, which can help you dynamically adapt each jo
1111

1212
Unlike traditional audience-based journeys, which rely solely on user progress through predefined steps, event-triggered journeys capture and store the details of user-triggered events. This shift allows you to access the data that caused users to reach a specific step and use it to make more precise decisions throughout the journey.
1313

14-
With journey context, you can:
14+
With journey context you can personalize customer experiences using real-time event data.
1515

1616
<!-- Split journeys based on event attributes or outcomes.-->
17-
- Personalize customer experiences using real-time event data.
18-
- Enable advanced use cases like abandonment recovery, dynamic delays, and more.
17+
<!-- Personalize customer experiences using real-time event data. -->
18+
<!-- Enable advanced use cases like abandonment recovery, dynamic delays, and more. -->
1919

2020
For example:
2121

@@ -154,4 +154,4 @@ Whether you're orchestrating real-time abandonment recovery or personalizing mes
154154

155155
To learn more about how Event-Triggered Journeys work, visit the [Event-Triggered Journeys documentation](/docs/engage/journeys/event-triggered-journeys/).
156156

157-
<!-- PW, 10 December 2024; on PM request, commented out certain sections with functionalities not yet available during public beta. -->
157+
<!-- PW, 10 December 2024; on PM request, commented out certain sections with functionalities not yet available during public beta. -->

0 commit comments

Comments
 (0)