A guide to the Courier data logs and how to navigate the information they provide about messages, automation, recipients and lists.
Courier Message Logs
Using the Message Logs
The Courier Message Logs provide a timeline and insights into the status of your notifications, recipients, lists and automations. Each step in the Send status has a visual representation.Your Notification Data at a Glance
The message logs convey a great deal of information in the summary view:- The
Statusof each message send request - The
NotificationandRecipientof associate with eachSendstatus - The
Providerchannels for the notification
Send Status Key and Definitions
| Status | APNS/FCM | Courier Inbox | SMS | Chat | |
|---|---|---|---|---|---|
| Queued | Courier has received a properly formatted and valid Send API request and is attempting to Send the Notification. | Courier has received a properly formatted and valid Send API request and is attempting to Send the Notification. | Courier has received a properly formatted and valid Send API request and is attempting to Send the Notification. | Courier has received a properly formatted and valid Send API request and is attempting to Send the Notification. | Courier has received a properly formatted and valid Send API request and is attempting to Send the Notification. |
| Sent | Courier sent the request to the downstream provider. A 200 response will be given by Courier but could return undeliverable if the provider rejects it. | Courier sent the request to the downstream provider. A 200 response will be given by Courier but could return undeliverable if the provider rejects it. | Courier sent the request to the downstream provider. A 200 response will be given by Courier but could return undeliverable if the provider rejects it. | Courier sent the request to the downstream provider. A 200 response will be given by Courier but could return undeliverable if the provider rejects it. | Courier sent the request to the downstream provider. A 200 response will be given by Courier but could return undeliverable if the provider rejects it. |
| Delivered | Channel providers allow Courier to confirm that the message was accepted (in the case of Email, this means it hit their inbox). Webhooks are available for status delivery updates. | Delivery Rate = 100% - Error Rate \ If an event is not classified as an error, it is considered delivered. | Delivery Rate = 100% - Error Rate \ If an event is not classified as an error, it is considered delivered. | Courier has received a delivered response from the downstream provider. Not all SMS providers return a delivered status | The Chat provider has confirmed delivery. |
| Opened | If open tracking is enabled, the request was delivered and opened by the recipient. | Not reported or supported by the service | Tracked via push events from the client SDK | n/a | n/a |
| Clicked | If link tracking is enabled for your workspace, Courier will change the status to clicked when a recipient clicks on links sent in the notification. | Tracked via notification click events from the SDK | Tracked via click events pushed from the SDK | n/a | If link tracking is enabled for your workspace, Courier will change the status to clicked when a recipient clicks on links sent in the notification. |
Inbox and Channel Sync
Notification event states are synchronized between the inbox and other channels within a notification template. For example, if a notification was sent with an in-appinbox and email channels, opening the email will mark the in-app inbox notification as read.
This flow only works one way. Reading an inbox message will not mark an email as
opened.Other Message Statuses
- Canceled: The message delivery was canceled.
- Undeliverable: The channel provider did not accept the send request from Courier.
- Unmapped: the Notification ID does not exist or the Event ID included in the send command is not mapped to a Notification.
- Has Errors: indicates that the timeline in the Send detail view includes an error response.
- Throttled: Notifications are being throttled either because there are send limits in effect, or your workspace has reached its free quota.
- Simulated: Notifications are being sent with a mock key and are simulating the message lifecycle without sending to the downstream provider.
Histogram
The logs histogram gives Courier users insights and breaks down delivery metrics for specific days and groups events in color-coordinated graphs.
Logs Histogram
Drag Select View
Notification Log Detail View
To view the details of a Notification Send, click the Notification in the list view to open the Log details.
Detailed View
Send Detail View
When you click a Notification to open the Log Detail view you will see a Summary and Timeline.- Summary - See details like the Message and Recipient IDs, as well as Date and time stamps for Send stages (Enqueued, Sent, First Delivery, Status, etc.).
- Timeline - Detailed timeline of every step in the timeline. The timeline can be scrolled and events in the timeline can be clicked to open additional details.
Timeline Event View
If you want to see the details of any event in the timeline, click it to open. As an example, you can click into theError Encountered tab in the timeline to review the error message.
Error Tab
Filtering your Message Logs
The message log includes a filter to search and narrow your notification logs by sendStatus, Errors, or to inspect the results of specific Providers, Notifications, or Recipient.
Date, Recipient and Notification Filters
- The Log date filter allows you to filter to see notifications send on specific dates. The date range available depends on your account’s log retention policy (see Log Retention below).
- Filter by Email or Recipient ID
- Filter by a specific Notification or search them all.
Notification Status Filter
You can filter your Notification Logs by selecting one or more Status types: Queued, Sent, Delivered, Opened, Clicked, Undeliverable or Unmapped.INFOUnmapped means that an Event was posted to our Send API with an
eventId that does not map to a notification or an invalid notification ID.Error Status Filter
You can also identify notifications with any status that also have errors.Provider Filter
You can review the logs of any combination of your integrated providers by selecting them in theProvider filter.
Log Retention
Courier retains message logs for different periods depending on your account type:- Free and Pro accounts: Logs are retained for 30 days
- Contracted accounts: Logs are retained for 1 year
Enterprise Customers: If you need longer log retention periods, contact Courier Support to discuss extended retention options.
Automation Logs
The Automation logs provide detailed insights into the status of an automation run as well as step details.Automation Run List
Automation Logs
Automation Run Summary