Skip to content

Commit bf273d9

Browse files
committed
update w eng feedback
1 parent d68392d commit bf273d9

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

src/connections/delivery-overview.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,13 +58,14 @@ The following image shows a storage destination with 23 partially successful syn
5858

5959
##### Linked Audiences to Snowflake destination
6060

61-
You can send Linked Audiences downstream to the Snowflake destination with the following steps:
61+
You can view information about events sent from Linked Audiences downstream to the Snowflake destination with the following pipeline view:
62+
6263
- **Events from audience**<sup>*</sup>: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership.
6364
- **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/).
6465
- **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.
6566
- **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into Snowflake warehouse rows.
66-
- **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).
67-
- **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.
67+
- **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).
68+
- **Successful delivery**: Events that were successfully delivered to Snowflake.
6869

6970
#### Destinations connected to Engage Destinations
7071

0 commit comments

Comments
 (0)