Skip to content

Commit f2f56b7

Browse files
authored
Add to delivery overview alerts section
1 parent 5322da3 commit f2f56b7

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

src/connections/delivery-overview.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,10 @@ With Source Debugger or Event Delivery, you can only verify that events are succ
8787
With Delivery Overview, you can verify that your source receives your events, that any filters and tracking plans work as expected, and that events successfully make it to your destination. Any errors or unexpected behavior can be identified using the pipeline view, leading to quicker resolution.
8888

8989
## How can I configure alerts?
90-
During the Delivery Overview beta, you can use the Event Delivery alerting features (Delivery Alerts) by selecting the **Alerts** tab in the destination header.
90+
During the Delivery Overview beta, you can use the Event Delivery alerting features (Delivery Alerts) by selecting the **Alerts** tab in the destination header.
91+
92+
Once enabled, if the successful delivery rate of all events is less than x% in the last 24 hours you will be notified via in-app notification and/or workspace email. Please note, this is dependent on your [notication settings](https://segment.com/docs/segment-app/#segment-settings). So if the thresshold is set to 99% then you will be notified anytime less than 100% of events fail.
93+
9194

9295
## Why is the Delivery Overview page only available for cloud-mode destinations?
9396
Similar to Segment's [Event Delivery](/docs/connections/event-delivery/) feature, the Delivery Overview page is only available for server-side integrations (also known as cloud-mode destinations). You won't be able to use the Delivery Overview page for client side integrations (also known as device-mode destinations) because device-mode data is sent directly to the destination tool's API. In order to report on deliverability, data must be sent to destinations using a server-side connection.

0 commit comments

Comments
 (0)