Skip to main content
Every email you send through Lettr generates a series of events as it moves through the delivery pipeline. The Events page in your dashboard gives you a real-time, chronological view of what happened to each message — from the moment it was injected all the way through delivery, opens, clicks, bounces, or complaints. Events are distinct from Analytics, which shows you aggregate metrics and trends over time. Events are the granular, per-email record. If Analytics tells you “your bounce rate went up yesterday,” Events lets you find exactly which messages bounced and why.

​
What You’ll See in the Events Dashboard

When you navigate to Events in the sidebar, you’ll land on a list of all recent email events for your team. Each row shows the timestamp, the event type (color-coded by category), the email subject, and the recipient and sender addresses. From this list, you can click View Details on any row to drill into the full event history for that specific message. Events are kept for about 10 days, and the dashboard opens on that whole window. You can narrow the date range with the date picker (it doesn’t offer days older than the retained window or days in the future) and narrow results down to a specific recipient by entering their email address in the search field. If a requested range reaches further back than that, the page tells you so (“Events are kept for about 10 days…”) and shows results from the oldest retained events onward. The per-page selector lets you display 10, 25, 50, or 100 events at a time, and navigation buttons let you page through results.

​
Available Filters

The Events page cannot filter by template, subject line, or email content. To find the emails sent from one template, search by the recipient you sent to and narrow the date range to when the send happened; the subject column then identifies the message.
Events also don’t show the merge tag values (substitution_data) an email was sent with. Lettr does not store those values — the API logs record only how many were sent (see Truncated Fields). If you need to know later which values a message was sent with, attach the important ones as metadata, which is kept and shown on the Message Details page, or log them in your own application.
Events are kept for about 10 days. If you need longer-term storage of event data, use webhooks to capture and store events in your own system as they occur.

​
Events vs. Webhooks

Events and webhooks are two ways to observe the same underlying data. The Events dashboard is for manual investigation — you open it when you want to check on a specific email or understand what happened to a batch of sends. Webhooks are for automation — Lettr pushes event data to your server in real time so your application can react without polling. For a full reference of event types and their webhook payloads, see Webhook Event Types. The event types you see in the Events dashboard correspond directly to the same set of events that webhooks deliver.
There’s a third way to explore events: ask an AI assistant. The remote Lettr MCP server has a browse_email_events tool, so a prompt like “show me all bounces from the last week” in Claude.ai or ChatGPT queries the same event data without opening the dashboard.

​
Searching for a Specific Email

If you need to track down what happened to a particular message, enter the recipient’s email address in the search field and hit Search. Lettr will return all events associated with emails sent to that address within your selected date range. From there, click View Details on the relevant row to see the full timeline of that message, including delivery status, any bounces or deferrals, and engagement like opens and clicks.

Try it in the app

Follow an interactive walkthrough of this guide inside Lettr.
You can also retrieve sent emails programmatically using the emails API:
This returns a list of emails sent to the specified recipient, filtered to injection events only. It does not include the full event history (deliveries, opens, clicks, bounces, etc.) that the Events dashboard shows. See Email History for full details on the API response structure and query parameters.

​
Next Steps

Event Types

Reference for every event type and what it means

Message Details

How to read the per-message event timeline

Webhook Event Types

Full payload reference for programmatic event handling

Analytics

Aggregate metrics and trends across all your sends