Skip to content

Commit d0be3db

Browse files
authored
Update event-delivery.md
1 parent 549cb91 commit d0be3db

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

src/connections/event-delivery.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,11 @@ To help you debug, Segment provides sample payloads from every step of the data'
9292

9393
- **Request to Destination** - the request Segment made to the Partner API. This payload will likely be different from what you sent it because Segment is mapping your event to the partner's spec to ensure the message is successfully delivered. 
9494

95-
- **Response from Destination** - the response Segment received from the Partner API. This will have the raw partner error. If you need to troubleshoot an issue with a Partner's Success team, this is usually something they'll want to see. 
95+
- **Response from Destination** - the response Segment received from the Partner API. This will have the raw partner error. If you need to troubleshoot an issue with a Partner's Success team, this is usually something they'll want to see.
96+
97+
#### Email Alerts
98+
99+
You can opt in to receive email alerts regarding failed events/syncs by going to your workspaace Settings > User Preferences > Activity Notifications > Destiantions. Then you can select the option to be alerted by Email and/or In-app.
96100

97101

98102
## 4. Trends
@@ -112,8 +116,5 @@ When debugging, it's helpful to see when issues start, stop, and trend over time
112116

113117
How P95 latency has trended over the time period you selected.
114118

115-
#### Email Alerts
116-
117-
You can opt in to receive email alerts regarding failed events/syncs by going to your workspaace Settings > User Preferences > Activity Notifications > Destiantions. Then you can select the option to be alerted by Email and/or In-app.
118119

119120

0 commit comments

Comments
 (0)