Email Notifications

1. Creating the email notification

  • built: The email notification has been created by Shipup.
  • canceled: The notification was created but not dispatched because of a specific Liquid condition.
  • error building: We encountered an error while building the notification because of two possible reasons:

1/ no email: The email field was empty 

2/ no template: There isn't any template for this notification. This can happen when a language has been added to Shipup but the associated email templates haven't been generated. More information below:

 
2. The email notification has been built and we are now trying to send it

  • dispatched: The email notification has been dispatched to SendGrid.
  • error dispatching: There was an error while dispatching the email notification (ex: provider unavailable)

3. The email notification has been dispatched and processed by SendGrid

  • delivered: The email notification has been delivered to the client.
  • SendGrid error: The email was processed by SendGrid but it returned an error such as:

1/ bounced: 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.
2/ blocked/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.
3/ dropped: 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 or we see the recipient has unsubscribed previously.
4/ spam_reported: When SendGrid receives a specific spam complaints they fire a spam event so that you can react appropriately. (not included yet)
5/ unsubscribe: One of the most important events fires when a recipient unsubscribes from your mailings. (not included yet)

4. The email notification has been delivered

  • open: The email notification has been opened by the client
  • clicked: The email notification has been opened and clicked by the client

SMS

1. Building the SMS

  • built: The SMS notification has been created by Shipup.
  • canceled: The SMS notification was created but not dispatched because of a specific Liquid condition.
  • error building: We encountered an error while creating the notification because of one main reason.
  1. invalid number: The phone number field was empty or invalid

2. The notification has been created and we are now trying to sent it

  • dispatched: The SMS has been dispatched to our SMS provider
  • error dispatching: There was an error while dispatching the SMS (ex: provider_unavailable)

Zendesk & Georgias

1. Building the ticket

  • built: The ticket notification has been built by Shipup.
  • canceled: The ticket notification was built but not dispatched because of a specific Liquid condition.
  • error building: We encountered an error while building the ticket notification because of one main reason.no_app_found: We tried to create a Zendesk or Gorgias ticket for a client who uninstalled the Zendesk or Gorgias app on Shipup


2. The ticket notification has been built and we are now trying to send it

  • dispatched: The ticket has been dispatched to Zendesk or Gorgias
  • error dispatching: There was an error while dispatching the ticket (ex: support unavailable)

🎁 Bonus:

  • 🇫🇷 Language Filters 🇬🇧: You have the ability to filter the notification by languages to give you the ability to view only the notifications created in a specific language.
  • 📋Statuses included in exports : The Notification statuses are integrated in the CSV exports which will allow you to operate deeper analysis on your notifications.
  • ✉️Filtered by Notification types 💬: You are able to filter the notifications to view only the emails, SMS or Zendesk/Gorgias tickets created.


Did this answer your question?