Merge pull request #6544 from segmentio/joeynmq-patch-5

Clarify 5-min lookback window for Delivery Overview

Author: pwseg

src/connections/delivery-overview.md

@@ -21,8 +21,12 @@ 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
+
 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 includes a label between the Filtered at destination and Failed delivery steps indicating how many events are currently pending retry. 
 
+> info "Lookback window"
+> 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.
+
 #### Classic destinations
 The pipeline view for classic destinations includes the following steps:
 - **Successfully received**: Events that Segment ingested from your source.
@@ -43,8 +47,6 @@ The pipeline view for Actions destination includes 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.
 
-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)
 
 #### Storage destinations
@@ -141,4 +143,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 %}
-<!--- not in the product yet{% include content/retl-discards.md %}--->
+<!--- not in the product yet{% include content/retl-discards.md %}--->