From 99af8ecd9d70ed36bab290adc61d503d8407b088 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 22 Sep 2025 12:50:06 -0400 Subject: [PATCH 01/10] audience size alerts ga --- src/engage/audiences/index.md | 3 --- src/monitor/alerts/custom-alerts.md | 3 --- 2 files changed, 6 deletions(-) diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md index 060cbb2817..a17b6a94a5 100644 --- a/src/engage/audiences/index.md +++ b/src/engage/audiences/index.md @@ -334,9 +334,6 @@ To delete a Activation event health spikes or drops alert, select the icon in th You can create an Audience size change alert that notifies you when your audience increases or decreases by a certain threshold. For example, if you set a change percentage of 4% and your destination had 100 members over the first 24 hours, Segment would notify you the following day if your audience had fewer than 96 or more than 104 members. -> info "Audience size change alerts currently only support Linked Audiences" -> Audience size change alerts are in public beta, and Segment is actively working on this feature. During the public beta, Audience size change alerts only support Linked Audiences. Some functionality may change before it becomes generally available. - To create an Audience size change alert: 1. From your Segment workspace's home page, navigate to **Engage > Audiences**. 2. Select the Linked Audience you want to create an alert for, select the Alerts tab, and click **Create alert**. diff --git a/src/monitor/alerts/custom-alerts.md b/src/monitor/alerts/custom-alerts.md index 977d0f9098..f63d4f72ad 100644 --- a/src/monitor/alerts/custom-alerts.md +++ b/src/monitor/alerts/custom-alerts.md @@ -92,9 +92,6 @@ To create an Activation event health spikes or drops alert: ## Audience size change You can create an Audience size change alert that notifies you when your audience increases or decreases by a certain threshold. For example, if you set a change percentage of 4% and your destination had 100 members over the first 24 hours, Segment would notify you the following day if your audience had fewer than 96 or more than 104 members. -> info "Audience size change alerts currently only support Linked Audiences" -> Audience size change alerts are in public beta, and Segment is actively working on this feature. During the public beta, Audience size change alerts only support Linked Audiences. Some functionality may change before it becomes generally available. - To create an Audience size change alert: 1. From your Segment workspace’s home page, navigate to **Engage > Audiences**. From 0e11fc9cc3b0733c6f2a5165481fc39430b72946 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 28 Sep 2025 19:55:12 -0500 Subject: [PATCH 02/10] add payload example --- .../v2/event-triggered-journeys-steps.md | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index df6c4e2b34..1f22a41e31 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -322,6 +322,48 @@ Here’s a detailed example of a payload structure, highlighting the journey con This example shows how data is structured and enriched with contextual details so that destinations receive the information they need to act effectively. +### Warehouse enrichment (Data Graph) + +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. + +> info "Before you start" + +#### Configure enrichment + +Follow these steps to add attributes from the warehouse: + +1. Select the Data Graph entity you want to pull attributes from. +2. Choose the join ID in journey context that matches the entity’s primary key. +3. Pick the attributes to include; the preview updates as you add them. +4. Check the payload preview. Attributes appear under `properties.journey_context.`. +5. (Optional:) Map the enriched fields to your destination schema. + +Here's an example of an enriched payload: + +```json +{ + "properties": { + "journey_context": { + "Reservation Booked": { + "reservation_id": 12345, + "hotel_id": 67890 + }, + "Reservations": { + "check_in_time": "2025-11-01T20:00:00Z", + "check_out_time": "2025-11-04T15:00:00Z" + }, + "Hotels": { + "hotel_name": "Hotel California", + "hotel_address": "1000 Sunset Boulevard, Los Angeles, CA" + } + } + } +} +``` + +> warning "Publish timing for enrichment" + + ### Managing activations 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. From 1c7d444c8f3cbeda033d701e3a93a6ae89ba0a09 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 28 Sep 2025 20:03:40 -0500 Subject: [PATCH 03/10] add setup callout --- src/engage/journeys/v2/event-triggered-journeys-steps.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index 1f22a41e31..748c4ecc33 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -326,7 +326,8 @@ This example shows how data is structured and enriched with contextual details s 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. -> info "Before you start" +> info "Setup checklist" +> 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. #### Configure enrichment @@ -362,6 +363,7 @@ Here's an example of an enriched payload: ``` > warning "Publish timing for enrichment" +> 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. ### Managing activations From 91e0a7fca9385f4528cb6cd7055438fc4558fdc4 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 28 Sep 2025 20:17:00 -0500 Subject: [PATCH 04/10] add some links [netlify-build] --- src/engage/journeys/v2/event-triggered-journeys-steps.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index 748c4ecc33..d9ac9528c5 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -324,7 +324,9 @@ This example shows how data is structured and enriched with contextual details s ### Warehouse enrichment (Data Graph) -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. +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. + +For more information on join keys and event relationships, see [Linked Events overview](/docs/unify/data-graph/linked-events/). > info "Setup checklist" > 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. From 4eb161bab1bda58e88c3b3aa4265d566be390f18 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 28 Sep 2025 21:44:06 -0500 Subject: [PATCH 05/10] typo fix [netlify-build] --- src/engage/journeys/v2/event-triggered-journeys-steps.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index d9ac9528c5..9d6debf95e 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -324,7 +324,7 @@ This example shows how data is structured and enriched with contextual details s ### Warehouse enrichment (Data Graph) -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. +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. For more information on join keys and event relationships, see [Linked Events overview](/docs/unify/data-graph/linked-events/). @@ -336,10 +336,10 @@ For more information on join keys and event relationships, see [Linked Events ov Follow these steps to add attributes from the warehouse: 1. Select the Data Graph entity you want to pull attributes from. -2. Choose the join ID in journey context that matches the entity’s primary key. +2. Choose the join ID in the journey context that matches the entity’s primary key. 3. Pick the attributes to include; the preview updates as you add them. -4. Check the payload preview. Attributes appear under `properties.journey_context.`. -5. (Optional:) Map the enriched fields to your destination schema. +4. Use the **Preview event** panel to confirm names and nesting. Attributes appear under `properties.journey_context.`, and the preview reflects what Segment sends. +5. (Optional:) Map the enriched fields to your destination schema. Here's an example of an enriched payload: From 841e75e6646a8ff2876d67efd6215268927d7416 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 28 Sep 2025 22:20:21 -0500 Subject: [PATCH 06/10] update code tab [netlify-build] --- .../v2/event-triggered-journeys-steps.md | 23 +++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index 9d6debf95e..b82f708a0d 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -341,8 +341,25 @@ Follow these steps to add attributes from the warehouse: 4. Use the **Preview event** panel to confirm names and nesting. Attributes appear under `properties.journey_context.`, and the preview reflects what Segment sends. 5. (Optional:) Map the enriched fields to your destination schema. -Here's an example of an enriched payload: +Here's an example of a payload before and after enrichment: +{% codeexample %} +{% codeexampletab Before enrichment %} +```json +{ + "properties": { + "journey_context": { + "Reservation Booked": { + "reservation_id": 12345, + "hotel_id": 67890 + } + } + } +} +``` +{% endcodeexampletab %} + +{% codeexampletab After enrichment %} ```json { "properties": { @@ -363,11 +380,13 @@ Here's an example of an enriched payload: } } ``` +{% endcodeexampletab %} + +{% endcodeexample %} > warning "Publish timing for enrichment" > 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. - ### Managing activations 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. From 4c0ec2709bf8db8e0e5fdfc257294e0068ad677c Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 29 Sep 2025 21:20:33 -0500 Subject: [PATCH 07/10] change warning to troubleshooting paragraph [netlify-build] --- src/engage/journeys/v2/event-triggered-journeys-steps.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index b82f708a0d..9664f729af 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -384,8 +384,12 @@ Here's an example of a payload before and after enrichment: {% endcodeexample %} -> warning "Publish timing for enrichment" -> 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. +##### Publish behavior and failures + +Segment prepares enrichment when you publish. The journey stays in a **Publishing** state until enrichment is ready. If enrichment isn’t ready within 5 hours, the publish fails. + +If your publish fails, in most cases you just need to fix Data Graph or warehouse sync/join issues first, then create a new version and publish again. If a long warehouse job has since finished, re-publishing may succeed. + ### Managing activations From 90b3a6649936c096c76490a3971354ccbfbc3548 Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 29 Sep 2025 21:20:49 -0500 Subject: [PATCH 08/10] some more rephrasing [netlify-build[] --- src/engage/journeys/v2/event-triggered-journeys-steps.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index 9664f729af..f1807dbc55 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -386,10 +386,11 @@ Here's an example of a payload before and after enrichment: ##### Publish behavior and failures -Segment prepares enrichment when you publish. The journey stays in a **Publishing** state until enrichment is ready. If enrichment isn’t ready within 5 hours, the publish fails. +When you publish, Segment builds the enrichment data it needs. The journey stays in a **Publishing** state while that finishes. If enrichment isn’t ready within 5 hours, the publish fails. -If your publish fails, in most cases you just need to fix Data Graph or warehouse sync/join issues first, then create a new version and publish again. If a long warehouse job has since finished, re-publishing may succeed. +If your publish does fail, first check the Data Graph and your warehouse setup—sync status, join IDs, and entity configuration. Fix any issues, create a new version, and publish again. +If a long warehouse job has since finished, re-publishing may succeed without changes. ### Managing activations From 463eba43539303b1dfd0b1ccaaf24781f952ac2e Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 29 Sep 2025 21:21:09 -0500 Subject: [PATCH 09/10] typo fix [netlify-build] --- src/engage/journeys/v2/event-triggered-journeys-steps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index f1807dbc55..c1091a1938 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -390,7 +390,7 @@ When you publish, Segment builds the enrichment data it needs. The journey stays If your publish does fail, first check the Data Graph and your warehouse setup—sync status, join IDs, and entity configuration. Fix any issues, create a new version, and publish again. -If a long warehouse job has since finished, re-publishing may succeed without changes. +If a long warehouse job has since finished, re-publishing may succeed without changes. ### Managing activations From 6b2eec6255abe3a9404018d45fa0763d0b3eddf9 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Tue, 30 Sep 2025 11:29:36 -0500 Subject: [PATCH 10/10] Update src/engage/journeys/v2/event-triggered-journeys-steps.md Co-authored-by: Sharon Adewusi --- src/engage/journeys/v2/event-triggered-journeys-steps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/engage/journeys/v2/event-triggered-journeys-steps.md b/src/engage/journeys/v2/event-triggered-journeys-steps.md index c1091a1938..5b7bcaaf19 100644 --- a/src/engage/journeys/v2/event-triggered-journeys-steps.md +++ b/src/engage/journeys/v2/event-triggered-journeys-steps.md @@ -386,7 +386,7 @@ Here's an example of a payload before and after enrichment: ##### Publish behavior and failures -When you publish, Segment builds the enrichment data it needs. The journey stays in a **Publishing** state while that finishes. If enrichment isn’t ready within 5 hours, the publish fails. +When you publish a journey, Segment builds the enrichment data it needs. The journey stays in a **Publishing** state while that finishes. If enrichment isn’t ready within 5 hours, the publish fails. If your publish does fail, first check the Data Graph and your warehouse setup—sync status, join IDs, and entity configuration. Fix any issues, create a new version, and publish again.