From dbcc0d38ebe9655b01c47012edc1d4977f7e00ac Mon Sep 17 00:00:00 2001 From: joeynmq <37472597+joeynmq@users.noreply.github.com> Date: Wed, 15 May 2024 09:54:09 +0800 Subject: [PATCH 1/2] Update delivery-overview.md --- src/connections/delivery-overview.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index cdd0927d2e..052ea23453 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -20,6 +20,8 @@ Delivery Overview has three core features: You can refine these tables using the time picker and the metric toggle, located under the destination header. With the time picker, you can specify a time period (last 10 minutes, 1 hour, 24 hours, 7 days, 2 weeks, or a custom date range over the last two weeks) for which you'd like to see data. With the metric toggle, you can switch between seeing metrics represented as percentages (for example, *85% of events* or *a 133% increase in events*) or as counts (*13 events* or *an increase of 145 events*.) Delivery Overview shows percentages by default. ### Pipeline view +> info "Delivery Overview has a **5-minute** lookback period to provide more accurate metrics for the entire pipeline. + The pipeline view provides insights into each step your data is processed by enroute to the destination, with an emphasis on the steps where data can be discarded due to errors or your filter preferences. Each step provides details into counts, change rates, and event details (like the associated Event Type or Event Names), and the discard steps (Failed on ingest, Filtered at source, Filtered at destination, & Failed delivery) provide you with the reasons events were dropped before reaching the destination. Discard steps also include how to control or alter that outcome, when possible. The pipeline view also shows a label between the Filtered at destination and Failed delivery steps indicating how many events are currently pending retry. The pipeline view shows the following steps: @@ -113,4 +115,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 649e1088233d01916356475c3fd748fec25e12bf Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Wed, 13 Nov 2024 22:15:52 -0600 Subject: [PATCH 2/2] minor rewording --- src/connections/delivery-overview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index 052ea23453..a0472ca9d9 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -20,7 +20,6 @@ Delivery Overview has three core features: You can refine these tables using the time picker and the metric toggle, located under the destination header. With the time picker, you can specify a time period (last 10 minutes, 1 hour, 24 hours, 7 days, 2 weeks, or a custom date range over the last two weeks) for which you'd like to see data. With the metric toggle, you can switch between seeing metrics represented as percentages (for example, *85% of events* or *a 133% increase in events*) or as counts (*13 events* or *an increase of 145 events*.) Delivery Overview shows percentages by default. ### Pipeline view -> info "Delivery Overview has a **5-minute** lookback period to provide more accurate metrics for the entire pipeline. The pipeline view provides insights into each step your data is processed by enroute to the destination, with an emphasis on the steps where data can be discarded due to errors or your filter preferences. Each step provides details into counts, change rates, and event details (like the associated Event Type or Event Names), and the discard steps (Failed on ingest, Filtered at source, Filtered at destination, & Failed delivery) provide you with the reasons events were dropped before reaching the destination. Discard steps also include how to control or alter that outcome, when possible. The pipeline view also shows a label between the Filtered at destination and Failed delivery steps indicating how many events are currently pending retry. @@ -33,6 +32,8 @@ The pipeline view shows the following steps: - **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements - **Successful delivery**: Events that were successfully delivered to the destination +Delivery Overview applies a 5-minute lookback period to provide stable, accurate metrics across all pipeline steps. This interval accounts for processing delays and ensures the data Segment displays reflects a reliable snapshot of recent events. + Actions destinations also include a mapping dropdown, which allows you to select a [mapping](/docs/connections/destinations/actions/#customize-mappings) to filter the events in the Filtered at destination, Failed delivery and Successful delivery pipeline steps. The following image shows an Actions destination filtered to include only Track Page View events in the last three pipeline steps: ![A screenshot of the Delivery Overview tab for an Actions destination, with the Track Page View mapping selected.](images/delivery-overview-actions-destination.jpeg)