Skip to content

Commit 0e11fc9

Browse files
committed
add payload example
1 parent 038211c commit 0e11fc9

File tree

1 file changed

+42
-0
lines changed

1 file changed

+42
-0
lines changed

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

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -322,6 +322,48 @@ Here’s a detailed example of a payload structure, highlighting the journey con
322322

323323
This example shows how data is structured and enriched with contextual details so that destinations receive the information they need to act effectively.
324324

325+
### Warehouse enrichment (Data Graph)
326+
327+
If your workspace uses [Data Graph](/docs/unify/data-graph/), you can add attributes from warehouse entities to the destination payload. Segment joins entity data using an ID in journey context and includes the selected attributes alongside existing journey context. Enrichment doesn’t change the underlying journey events.
328+
329+
> info "Before you start"
330+
331+
#### Configure enrichment
332+
333+
Follow these steps to add attributes from the warehouse:
334+
335+
1. Select the Data Graph entity you want to pull attributes from.
336+
2. Choose the join ID in journey context that matches the entity’s primary key.
337+
3. Pick the attributes to include; the preview updates as you add them.
338+
4. Check the payload preview. Attributes appear under `properties.journey_context.<EntityName>`.
339+
5. (Optional:) Map the enriched fields to your destination schema.
340+
341+
Here's an example of an enriched payload:
342+
343+
```json
344+
{
345+
"properties": {
346+
"journey_context": {
347+
"Reservation Booked": {
348+
"reservation_id": 12345,
349+
"hotel_id": 67890
350+
},
351+
"Reservations": {
352+
"check_in_time": "2025-11-01T20:00:00Z",
353+
"check_out_time": "2025-11-04T15:00:00Z"
354+
},
355+
"Hotels": {
356+
"hotel_name": "Hotel California",
357+
"hotel_address": "1000 Sunset Boulevard, Los Angeles, CA"
358+
}
359+
}
360+
}
361+
}
362+
```
363+
364+
> warning "Publish timing for enrichment"
365+
366+
325367
### Managing activations
326368

327369
Activations control the configuration for sending data to destinations, including the destination type, selected action, and mapped attributes. Managing activations allow you to adjust how data flows to a destination without altering the overall journey logic.

0 commit comments

Comments
 (0)