Skip to content

Commit 1c7d444

Browse files
committed
add setup callout
1 parent 0e11fc9 commit 1c7d444

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -326,7 +326,8 @@ This example shows how data is structured and enriched with contextual details s
326326

327327
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.
328328

329-
> info "Before you start"
329+
> info "Setup checklist"
330+
> Before you add warehouse entities, verify that Data Graph is set up and synced. Choose the entity with the attributes you need. Confirm the join ID exists in journey context when the step runs.
330331
331332
#### Configure enrichment
332333

@@ -362,6 +363,7 @@ Here's an example of an enriched payload:
362363
```
363364

364365
> warning "Publish timing for enrichment"
366+
> When you publish a journey with enrichment enabled, Segment starts a job to prepare enrichment.The journey stays in a publishing state until enrichment is available. If the cache isn’t populated within 5 hours, the publish fails. Resolve Data Graph sync or join-ID issues, then publish again.
365367
366368

367369
### Managing activations

0 commit comments

Comments
 (0)