Export events
Download every delivery event for the messages in your Activity search, one row or line per event, to analyse in a spreadsheet or load into your own systems.
An event is one thing that happened to one recipient of a message: delivered, deferred, bounced, expired, complained or rejected. These are the same events your webhooks receive, with the same fields (see the Event reference). Use the export when you want them as a file instead of waiting for them to arrive at an endpoint.
Export events
- Open Activity and set the filters you want: status, sending domain, date range, message ID, recipient or metadata. Select Search.
- Select Export, then Events (CSV or JSON Lines).
- Check Messages included. It lists the filters of your current search, so the export matches the messages in the list. To change them, close the window, change the filters and search again.
- Choose a Format and select Export.
The file downloads straight from SendMero as it is prepared. A large export can take a few minutes before the file appears; keep the page open until it does.
The file name is events- followed by today's date (UTC), for example events-2026-10-14.csv.
What is in the file
- Which messages: the messages your search lists, up to the 100,000 most recent. If your search has more, narrow it (a shorter date range or a single domain) and export again.
- Which events: every delivered, deferred, bounced, expired, complained and rejected event of those messages, including events for recipients that don't match a status filter. For example, a search for Bounced exports all events of the messages that bounced.
- Order: the newest message first. Within a message, the oldest event first.
- Times: UTC.
CSV
One row per event, with these columns:
| Column | Meaning |
|---|---|
| Event ID | Unique ID of the event (evt_…). Use it to ignore duplicates. |
| Type | delivered, deferred, bounced, expired, complained or rejected. |
| Occurred at (UTC) | When it happened. |
| Recorded at (UTC) | When SendMero recorded it. |
| Message ID | The ID returned when you sent the email (msg_…). |
| Recipient, Sending domain, Attempt | Who it is about, your sending domain, and the delivery attempt. |
| SMTP code, Enhanced code, SMTP response, Remote IP | What the recipient's mail server replied, when it did. |
| Bounce type, Bounce classification | For bounces: hard, soft, block or admin, and a more specific reason when known. |
| Reason | A short machine-readable reason for events that have one but no bounce, such as rejected. |
| Metadata | The metadata you sent with the email, as JSON. |
JSON Lines
One event per line, in exactly the format of a webhook event, with data.metadata included. Each line is a complete JSON document, so you can read the file a line at a time. It is the best format for loading events into a database or data warehouse.
Who can export
The Events option is available to people whose role has the Export analytics and raw events permission. Owners, Admins, Developers and Analysts have it by default. Owners and Admins can change this for custom roles under Settings → Users & Permissions. Everyone who can see Activity can still use Export CSV to download the messages themselves.
Each export is recorded in the audit log with the format, the filters used and how many events it contained.
If the export is refused
- No events to export: nothing matches the current filters, or the messages are so new that they don't have delivery events yet. Try again in a few minutes, or widen the filters.
- The download link expired: the link SendMero creates works for two minutes. Select Export again.
- Too many exports running: a workspace can run two exports at once. Wait for one to finish.
To download the messages themselves, one row each, choose Messages (CSV) in the same menu. To receive events as they happen instead of downloading them, set up a webhook.