Skip to content

Commit 42ae275

Browse files
forstisabellapwseg
andauthored
Apply suggestions from code review
Co-authored-by: pwseg <[email protected]>
1 parent 564b1ce commit 42ae275

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/connections/delivery-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The pipeline view shows the following steps:
2525
- **Successfully received**: Events that Segment ingested from your source
2626
- **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules
2727
- **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) tracking plans
28-
- **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), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). Actions destinations 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.
28+
- **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), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). Actions destinations 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.
2929
- **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements
3030
- **Successful delivery**: Events that were successfully delivered to the destination
3131

@@ -35,7 +35,7 @@ The breakdown table provides you with greater detail about the selected events.
3535
To open the breakdown table, select either the first step in the pipeline view (successfully received,) the last step in the pipeline view (successful delivery,) or select a discard step and then click on a discard reason.
3636

3737
The breakdown table displays the following details:
38-
- **Event type**: The Segment spec event type (track call vs. identify call, for example)
38+
- **Event type**: The Segment spec event type (Track call vs. Identify call, for example)
3939
- **Event name**: The event name, provided by you or the source (*currently not available for inspection at all steps, but full availability is in development*)
4040
- **App version**: The app/release version, provided by you or the source (*currently not available for inspection at all steps, but full availability is in development*)
4141
- **Event count**: How many of each event either successfully made it through this pipeline step (in the case of the first or last steps in the pipeline view) or were filtered out (if you access it from a discard table)
@@ -50,7 +50,7 @@ To open the discard table, click on one of the discard steps. If you click on a
5050

5151
The discard table displays the following details:
5252
- **Discard reason**: Any relevant error code, message, or description associated with the event's failure. When possible, Delivery Overview will link to any troubleshooting information you can use to get your events up and running again. Clicking on a discard reason brings you to the [breakdown table](#breakdown-table,) where you can see more detail about discarded events.
53-
- **Details & Samples**: View up to ten samples over the selected time range. Examine the error message and reason for the error or discard and inspect the payloads involved with the attempted transaction (*currently not available for inspection at all steps, but full availability is in development*)
53+
- **Details & Samples**: View up to ten samples over the selected time range. Examine the error message and reason for the error or discard and inspect the payloads involved with the attempted transaction (*not available for inspection at all steps*)
5454
- **Event count**: How many of each event were discarded in this pipeline step
5555
- **% Change**: Insight into how the event counts differ from the last comparable time range as a percentage<sup>1</sup>
5656

0 commit comments

Comments
 (0)