Skip to main content
Message Logs enables you to monitor and track all email events in real-time, including delivery status, bounces, complaints, opens, and clicks.
  1. Click the Enable Message Logs button on the Message Logs page
  2. Click AWS API button and copy the configuration set name from the code example
  3. Include the configuration set name in your AWS SES API calls
Example
await client.sendEmail({
  FromEmailAddress: "<from-email-address>",
  Destination: { ToAddresses: ["<recipient-email-address>"] },
  ConfigurationSetName: "<log-configuration-set-name>", // Copy this from AWS API button
  Content: {
    /* ... */
  },
});
Emails sent without the configuration set name will not be tracked.

​
Delivery Summary

The Message Logs page displays a summary of your email delivery and engagement metrics at a glance.
  • Delivered: Percentage of emails successfully delivered to recipients’ mail servers
  • Bounced: Percentage of emails that bounced (hard or soft bounces)
  • Open Rate: Percentage of delivered emails that were opened by recipients
  • Click Rate: Percentage of delivered emails where recipients clicked on links

​
Monitor Another Configuration Set

If you want to monitor another configuration set, you should configure your configuration set destination with an SNS topic created by Sendbase. The SNS topic name starts with sendbase-log-<id>.

​
Tracked Events

Event TypeDescription
SENDEmail was successfully sent from SES
DELIVERYEmail was successfully delivered to the recipient’s mail server
BOUNCEEmail bounced (hard or soft bounce)
COMPLAINTRecipient marked the email as spam
REJECTSES rejected the email (invalid recipient, configuration issues)
OPENRecipient opened the email
CLICKRecipient clicked a link in the email
RENDERING_FAILUREEmail template failed to render
DELIVERY_DELAYTemporary delivery delay occurred
When a Bounce or Complaint event is received, the contact is automatically unsubscribed if they exist in the project’s contact list.

​
Data Retention

Email logs are automatically deleted after 7 days to manage storage costs and comply with data retention best practices. An automated cleanup job runs every hour to remove expired logs. If you need longer retention:
  • Set up your own custom CloudWatch or S3-based logging solution
  • Contact support for retention options