Bounces often are caused by outdated or incorrectly entered email addresses. If a server cannot or will not deliver a message, SendGrid fires a bounce event. After 72 hours, the deferral turns into a block. Sometimes called a soft bounce, SendGrid will continue to try for 72 hours to deliver a deferred message. When an email cannot immediately be delivered, but it hasn’t been completely rejected, the deferred event fires. Further, it provides a reason for the drop, such as if we’ve found spam content (if spam checker app is enabled) or we see the recipient has unsubscribed previously.
This event informs your system when an email has been dropped. There are a number of reasons your email will not even be sent to a recipient for delivery. Think of this as the top of the funnel-unless it is dropped (see below), each message you push to SendGrid will create a processed event. This event fires when SendGrid receives an individual message and prepares it to be delivered. Below is a quick breakdown of each of the nine events: 1. Your project may not require listening for all nine, but each is useful in its own way. And there are some events you may want to react to immediately. Others you may want to save to query later. Some are informational and can be used to create instant dashboards. All SendGrid customers can enable the Event Webhook to receive notifications for the nine types of email events described below. To help, SendGrid has robust analytics and tracking capabilities, one of which is our Event Webhook.Īs emails are sent and recipients interact with them, events are triggered within SendGrid. Having insight into how your emails are processed and engaged with is key to having a healthy and successful email program.
0 kommentar(er)
