Skip to content

Commit 7593481

Browse files
committed
close code block
1 parent 5659560 commit 7593481

File tree

1 file changed

+9
-17
lines changed

1 file changed

+9
-17
lines changed

src/engage/journeys/contextual-journeys.md

Lines changed: 9 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,11 @@ With journey context, you can:
1717
> info "Private Beta"
1818
> Event-Triggered Journeys is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. During private beta, Event-Triggered Journeys is not HIPAA eligible.
1919
20-
## What is Journey Context?
20+
## What is Journey context?
2121

2222
Journey context is a flexible data structure that captures key details about the events and conditions that shape a customer’s journey. Journey context provides a point-in-time snapshot of event properties, ensuring accurate and reliable data is available throughout the journey.
2323

2424
Journey context stores:
25-
2625
- **Event properties**: Information tied to specific user actions, like `Appointment ID` or `Order ID`.
2726
- **Split evaluations**: Results of branch decisions made during the journey, enabling future steps to reference these outcomes.
2827

@@ -46,13 +45,13 @@ Event properties are the foundation of Journey context. Examples of event proper
4645
- `Order ID`
4746
- An array of cart contents
4847

49-
Each event’s properties are captured as a point-in-time snapshot when the event occurs. This ensures the data remains consistent for use in personalization, branching, and other advanced workflow steps.
48+
Segment captures each event’s properties as a point-in-time snapshot when the event occurs, ensuring that the data remains consistent for use in personalization, branching, and other advanced workflow steps.
5049

5150
## Using Journey context in Event-Triggered Journeys
5251

53-
Journey context is a system for capturing and referencing data about events and conditions within a customer journey. It allows Event-Triggered Journeys to respond dynamically to user behavior by making event-specific data available for decisions and actions at each step.
52+
Journey context provides the framework for capturing and referencing data about events and conditions within a journey. It allows Event-Triggered Journeys to dynamically respond to user behavior by making event-specific data available for decisions and actions at each step.
5453

55-
Journey context helps you create workflows that use real-time data, instead of relying on predefined, static rules. This is useful for scenarios like:
54+
This is useful for scenarios like:
5655

5756
- **Abandonment recovery:** Checking whether a user completed a follow-up action, like a purchase.
5857
- **Customizing messages:** Using event properties to include relevant details in communications.
@@ -130,25 +129,18 @@ The following example shows how journey context might look during a workflow. In
130129
"discount_percentage": 15
131130
}
132131
}
132+
```
133133

134134
This payload contains:
135135

136136
- **Event properties**: Captured under the `appointment_scheduled` key.
137137
- **Split outcomes**: Documented in the `split_decision` object.
138138
- **Function results**: Stored in the `function_output` object for use in later steps.
139139

140-
<!--
140+
## Next steps
141141

142-
5. Context Structure
143-
Explanation of context organization and data flow.
144-
Include a sample payload for reference.
145-
6. Best Practices
146-
Tips for optimizing journeys with context (e.g., using filters, testing).
147-
7. Example Use Cases
148-
Illustrative scenarios demonstrating the power of journey context in real-world applications.
149-
8. Troubleshooting and FAQs
150-
Common issues and resolutions.
151-
Clarifications about limitations (e.g., context doesn’t store dynamic traits).
142+
Journey context underpins the flexibility and precision of Event-Triggered Journeys. By capturing key details about events and decisions as they happen, journey context lets workflows respond dynamically to user actions and conditions.
152143

144+
Whether you're orchestrating real-time abandonment recovery, scheduling contextual delays, or personalizing messages with event-specific data, journey context provides the tools to make your workflows more relevant and effective.
153145

154-
-->
146+
To learn more about how Event-Triggered Journeys work and how journey context fits into the bigger picture, visit the [Event-Triggered Journeys documentation](/docs/engage/journeys/event-triggered-journeys/).

0 commit comments

Comments
 (0)