From 86fefef309176b56e4f243bcbf3d78eb7da09ac5 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 31 Oct 2025 14:07:42 -0400 Subject: [PATCH 1/5] linked to snowflake delivery overview --- src/connections/delivery-overview.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index cc64ab5474..4546dd2169 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -50,12 +50,22 @@ The pipeline view for storage destination includes the following steps: - **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), [Destination Insert functions](/docs/connections/functions/insert-functions/), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences. - **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into warehouse rows. - **Failed to sync**: Syncs that either failed to sync or were partially successful. Selecting this step takes you to a table of all syncs with one or more failed collections. Select a sync from the table to view the discard reason, any collections that failed, the status, and the number of rows that synced for each collection. For information about common errors, see Ware -- **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step. +- **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step. The following image shows a storage destination with 23 partially successful syncs: ![A screenshot of the Delivery Overview tab for a Storage destination, with the Failed to sync step selected and a table of partially successful syncs.](images/delivery-overview-storage-destinations.png) +##### Linked Audiences to Snowflake destination + +You can send Linked Audiences downstream to the Snowflake destination with the following steps: +- **Events from audience***: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. +- **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). +- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), [Destination Insert functions](/docs/connections/functions/insert-functions/), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences. +- **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into Snowflake warehouse rows. +- **Failed to sync**: Syncs that either failed to sync or were partially successful. Selecting this step takes you to a table of all syncs with one or more failed collections. Select a sync from the table to view the discard reason, any collections that failed, the status, and the number of rows that synced for each collection. For information about common errors, see Ware +- **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step. + #### Destinations connected to Engage Destinations > info "Delivery Overview for Engage Destinations is in Public Beta" From d68392d2a9bff5163eebfb3e88c7ab6c75d43393 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 5 Nov 2025 09:52:02 -0500 Subject: [PATCH 2/5] Update src/connections/delivery-overview.md Co-authored-by: Sharon Adewusi --- src/connections/delivery-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index 4546dd2169..d9f31fda63 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -63,7 +63,7 @@ You can send Linked Audiences downstream to the Snowflake destination with the f - **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). - **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), [Destination Insert functions](/docs/connections/functions/insert-functions/), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences. - **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into Snowflake warehouse rows. -- **Failed to sync**: Syncs that either failed to sync or were partially successful. Selecting this step takes you to a table of all syncs with one or more failed collections. Select a sync from the table to view the discard reason, any collections that failed, the status, and the number of rows that synced for each collection. For information about common errors, see Ware +- **Failed to sync**: Syncs that either failed to sync or were partially successful. Selecting this step takes you to a table of all syncs with one or more failed collections. Select a sync from the table to view the discard reason, any collections that failed, the status, and the number of rows that synced for each collection. For information about common errors, see [Warehouse Errors](docs/connections/storage/warehouses/warehouse-errors). - **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step. #### Destinations connected to Engage Destinations From bf273d925d99e941ffa4b3c6d5312794866ae819 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 7 Nov 2025 09:37:16 -0500 Subject: [PATCH 3/5] update w eng feedback --- src/connections/delivery-overview.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index d9f31fda63..51a596c6d2 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -58,13 +58,14 @@ The following image shows a storage destination with 23 partially successful syn ##### Linked Audiences to Snowflake destination -You can send Linked Audiences downstream to the Snowflake destination with the following steps: +You can view information about events sent from Linked Audiences downstream to the Snowflake destination with the following pipeline view: + - **Events from audience***: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. - **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). - **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), [Destination Insert functions](/docs/connections/functions/insert-functions/), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences. - **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into Snowflake warehouse rows. -- **Failed to sync**: Syncs that either failed to sync or were partially successful. Selecting this step takes you to a table of all syncs with one or more failed collections. Select a sync from the table to view the discard reason, any collections that failed, the status, and the number of rows that synced for each collection. For information about common errors, see [Warehouse Errors](docs/connections/storage/warehouses/warehouse-errors). -- **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step. +- **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements. Click into this step to view a table of all collections with one or more failed events. Select a collection from the table to view the discard reason, any events that failed, and the status. For information about common errors, see [Warehouse Errors](docs/connections/storage/warehouses/warehouse-errors). +- **Successful delivery**: Events that were successfully delivered to Snowflake. #### Destinations connected to Engage Destinations From 67f6d3067996d84c8e9e5a9c0f874e6894b9d783 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 7 Nov 2025 09:38:30 -0500 Subject: [PATCH 4/5] [netlify-build] --- src/connections/delivery-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index 51a596c6d2..bd65c6dacb 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -162,4 +162,4 @@ The Delivery Overview pipeline steps Failed on Ingest, Filtered at Source, Filte This table provides a list of all possible discard reasons available at each pipeline step. {% include content/delivery-overview-discards.html %} - + \ No newline at end of file From c33c8fa1bb241d5a7106fe81e1b58babe8031d48 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 7 Nov 2025 14:56:22 -0500 Subject: [PATCH 5/5] fixes [netlify-build] --- src/connections/delivery-overview.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index bd65c6dacb..42eaf6470e 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -48,7 +48,7 @@ The pipeline view for storage destination includes the following steps: - **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules. - **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) Tracking Plans. - **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), [Destination Insert functions](/docs/connections/functions/insert-functions/), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences. -- **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into warehouse rows. +- **Events pending retry**: A read-only box that shows the number of events that are awaiting retry. - **Failed to sync**: Syncs that either failed to sync or were partially successful. Selecting this step takes you to a table of all syncs with one or more failed collections. Select a sync from the table to view the discard reason, any collections that failed, the status, and the number of rows that synced for each collection. For information about common errors, see Ware - **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step. @@ -60,11 +60,11 @@ The following image shows a storage destination with 23 partially successful syn You can view information about events sent from Linked Audiences downstream to the Snowflake destination with the following pipeline view: -- **Events from audience***: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. +- **Events from audience**: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. - **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). - **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), [Destination Insert functions](/docs/connections/functions/insert-functions/), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences. -- **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into Snowflake warehouse rows. -- **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements. Click into this step to view a table of all collections with one or more failed events. Select a collection from the table to view the discard reason, any events that failed, and the status. For information about common errors, see [Warehouse Errors](docs/connections/storage/warehouses/warehouse-errors). +- **Events pending retry**: A read-only box that shows the number of events that are awaiting retry. +- **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements. Select a discard reason from the table to view all events that failed, sorted by collection. For information about common errors, see [Warehouse Errors](/docs/connections/storage/warehouses/warehouse-errors). - **Successful delivery**: Events that were successfully delivered to Snowflake. #### Destinations connected to Engage Destinations