Email

Crittah uses email in various business processes to communicate information with customers. Email are sent for automatically for invoice payments, job status changes (when configured) or they can be manually sent by requesting to send an email in various parts of the system. All emails sent by Crittah go through a sophisticated delivery mechanism to keep you updated on if the email was delivered, if the customer read the email or if there was a failure in delivering the email.

Regardless of where an email is sent from within Crittah you can view all email events from the Administration page to occasionally check if emails are being delivered to your customers. To view email events you can navigate to Admin → Administration and then select "Mail Events" in the Mail section.

If you click on any of the email events you can view the full delivery history and the actual email that was sent

A complete description of all event can be found below.

Processed

This event fires when SendGrid receives an individual message and prepares it to be delivered. 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.

Dropped

There are a number of reasons your email will not even be sent to a recipient for delivery. This event informs your system when an email has been dropped. 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.

Deferred

When an email cannot immediately be delivered, but it hasn’t been completely rejected, the deferred event fires. Sometimes called a soft bounce, SendGrid will continue to try for 72 hours to deliver a deferred message.

Bounce

If a server cannot or will not deliver a message, SendGrid fires a bounce event. Bounces often are caused by outdated or incorrectly entered email addresses. Many times you won’t know a bounced email address until it bounces. This event can help you ensure it doesn’t bounce again by removing it from your lists.

Delivered

When an email has been accepted at the receiving server, the delivered event fires. This event does not guarantee that the email was placed in the recipient’s inbox. In fact, a delivered email is only the beginning of an opaque process. The remaining four events begin to give us hints about whether anyone will ever see this delivered email.

Open

An opened email is the first step toward the action you want your recipient to take. This event fires every time the email is viewed with images turned on. Like all email service providers, SendGrid uses a transparent image beacon to track opened messages. This beacon is currently the only way a sender can tell if an email has been opened. (To learn how image opens are affected by Google’s new image caching, read our blog post on the topic here.)

Click

The pinnacle of email engagement is the click. Your call to action, whether it is to confirm a newly registered account or to view a recommended product, asks the recipient to click a link. SendGrid tracks that interaction and fires a click event.

Spam Report

Most internet service providers provide a feedback loop, sending specific spam complaints to the email service providers. When SendGrid receives a notice, we fire a spam event, so that you can react appropriately–or at the very least, never send another email to that address.

Unsubscribe

One of the most important events fires when a recipient unsubscribes from your mailings. Reacting immediately to an unsubscribe by removing the email from your lists can pay long term dividends in fewer spam reports and a higher engagement rate.

These nine events are the core of the Event Webhook. To dive even deeper into how to use the webhook, some case studies of successful integrations and a technical overview, download the Event Webhook Guide.