Skip to content

Commit 4eb161b

Browse files
committed
typo fix [netlify-build]
1 parent 91e0a7f commit 4eb161b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -324,7 +324,7 @@ This example shows how data is structured and enriched with contextual details s
324324

325325
### Warehouse enrichment (Data Graph)
326326

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 shows the added fiels in the payload preview. Enrichment doesn’t change the underlying journey events.
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 shows the added fields in the payload preview. Enrichment doesn’t change the underlying journey events.
328328

329329
For more information on join keys and event relationships, see [Linked Events overview](/docs/unify/data-graph/linked-events/).
330330

@@ -336,10 +336,10 @@ For more information on join keys and event relationships, see [Linked Events ov
336336
Follow these steps to add attributes from the warehouse:
337337

338338
1. Select the Data Graph entity you want to pull attributes from.
339-
2. Choose the join ID in journey context that matches the entity’s primary key.
339+
2. Choose the join ID in the journey context that matches the entity’s primary key.
340340
3. Pick the attributes to include; the preview updates as you add them.
341-
4. Check the payload preview. Attributes appear under `properties.journey_context.<EntityName>`.
342-
5. (Optional:) Map the enriched fields to your destination schema.
341+
4. Use the **Preview event** panel to confirm names and nesting. Attributes appear under `properties.journey_context.<EntityName>`, and the preview reflects what Segment sends.
342+
5. (Optional:) Map the enriched fields to your destination schema.
343343

344344
Here's an example of an enriched payload:
345345

0 commit comments

Comments
 (0)