Skip to main content

​
Overview

Logs provide real-time monitoring of email activity and webhook events to help debug email delivery issues and track campaign performance.

​
Log Types

​
Messages Tab

  • Email Events: Track delivery, opens, clicks, bounces, and complaints
  • Real-Time Updates: Events appear immediately as they occur
  • Email Provider Data: Direct feedback from your configured email providers
  • Error: When a send was refused, the provider’s own reply — the SMTP code and the text that came with it, such as 452: 4.3.1 Daily sending quota exceeded. Hover to read the whole of it, or hide the column from the column picker.
Messages logs screenshot

​
Email Provider Webhooks Tab

  • Raw Payloads: Stores the complete, unmodified webhook data from email providers
  • Real-Time Processing: Webhooks processed immediately upon receipt
  • Provider Integration: Data from Mailgun, Amazon SES, Postmark, etc.

​
Event Updates

Email events are updated in real-time as email provider webhooks are received:
  • Delivered: Email successfully delivered to recipient
  • Opened: Recipient opened the email
  • Clicked: Recipient clicked a link in the email
  • Bounced: Email delivery failed
  • Complained: Recipient marked email as spam
Webhooks logs screenshot

​
Filtering Options

Filter logs by multiple criteria:
  • Status: Filter by delivery status (delivered, bounced, etc.)
  • Delivery: Show only the messages that failed to send, or only those that did not
  • Email: Search by specific recipient email address
  • Template: Filter by email template used
  • Broadcast: Filter by specific broadcast campaign

​
Permissions

The two tabs answer to two different permissions, both read-only in practice:
  • Messages needs Message History read. This is also where broadcast delivery statistics live — delivered, open, click, bounce and per-link counts — so a member who may create and send a broadcast still cannot see how it performed without it. The log carries recipient addresses and the data each message was rendered with, so treat it as contact data.
  • Email Provider Webhooks needs Webhook Events read. These are the providers’ own payloads, including recipient addresses and provider diagnostics.
The write verb of both permissions gates nothing today: these rows are written by the sending pipeline and by the provider callback routes, never by anything you can call. See Admins & API Keys.

​
Debugging Email Issues

Logs are essential for troubleshooting email provider problems:
  • Delivery Failures: Identify bounced emails and reasons, and read why a send was refused in the Error column
  • Provider Issues: Spot patterns in webhook failures
  • Performance Monitoring: Track open and click rates
  • Real-Time Debugging: Immediate feedback on email sending issues