Every message the platform sends (or attempts to send) is recorded in the E-mail Log. Use it to verify delivery, debug bounces, audit communication, and answer the inevitable "did you send the email?" question.
What's recorded
Per log entry:
- Recipient address.
- Sender (which E-mail Account was used).
- Subject.
- Body (the full HTML and plain-text versions).
- Template that produced the message.
- Send timestamp.
- Success / failure status.
- Error message if the send failed (e.g. SMTP rejection reason).
- Bounce status if the recipient's server reported a bounce.
- Open and click tracking (if you've enabled it via tracking-pixel injection).
Where to find it
Architect Panel → E-mail Log. The list page is filterable by recipient, subject, status, date range, template used, and sending account. Each entry can be clicked into for the full body view.
What you can do with the log
1. Verify delivery
"Did the customer actually receive the password reset?" Check the log; if status is Sent and there's no subsequent bounce, the email was delivered to their mail provider. (Whether it ended up in inbox or spam is a separate question — see deliverability monitoring.)
2. Debug bounces
Filter to Failed status. Common bounce reasons:
- User unknown — recipient address doesn't exist on their mail provider.
- Mailbox full — recipient's storage is full.
- Spam rejection — recipient's anti-spam filter rejected the message.
- Rate limit — your SMTP provider throttled your account.
Each has a different remediation: "user unknown" means clean up your contact list; "spam rejection" means investigate your SPF/DKIM/sender reputation.
3. Audit communication
"What emails have we sent to this customer in the last 6 months?" Filter the log by recipient. Useful for support tickets, compliance reviews, customer complaints.
4. Retry failed sends
Failed entries typically have a Retry action. Useful when a failure was transient (SMTP timeout, temporary provider outage). For permanent failures (invalid address), don't retry — fix the underlying problem.
Retention
By default, log entries are kept indefinitely. For high-volume installs (thousands of emails per day), this grows the database significantly over time. Set up a Task to purge entries older than your retention policy — typically 90 days for transactional, 1+ years for marketing.
Three real-world log uses
Example 1: Bounce investigation
Daily scheduled Task scans for new Failed entries with "user unknown" reason, removes the affected email from active marketing lists, alerts the data team to investigate the source.
Example 2: Customer support timeline
Support agent investigating a customer complaint pulls the customer's email log filtered to their address. Provides a clear timeline of what the platform sent to them and when, helping debunk "I never got the email" claims.
Example 3: Deliverability monitoring
Weekly Task aggregates the log and reports overall delivery success rate. A drop in success rate triggers an alert to investigate before the problem affects more users.