Sending analytics
What happened after Send.
The Sent tab under Settings → Analytics counts the mail you sent and what became of it for each recipient. Read it for the whole workspace or for the addresses you pick.
In short
What is email sending analytics?
Sending analytics counts the mail that left you and what happened to it next: how many messages went out, to how many people, and how many were delivered, bounced or reported as spam. Delivered means the receiving server accepted the message.
How it works
Followed to each recipient
What became of a message is counted per recipient: delivered, bounced, reported as spam, failed outright or still pending. Uncertain covers a send to many people that failed partway.
By address and by route
Sent from ranks the addresses mail went out as, busiest first. Sent through splits the same mail by how it was sent: the composer, the API, a scheduled send, the MCP server or the assistant.
The workspace or the addresses you pick
The Sent tab sits beside Received, over the same windows. Pick addresses to narrow it, and each member sees the addresses they can reach.
What you get
In the product today
Test sends kept apart
They are counted on their own and left out of every figure.
Blocked addresses
A count of the addresses the workspace has blocked.
The same numbers in code
GET /analytics/sending on the REST API, analytics.sending in the SDK and getSendingAnalytics on the MCP server.
Good practice
Getting the most out of it
- 01
Check one address at a time
Pick a single sending address to see what became of its mail alone.
- 02
Confirm a new route
Once you start sending through the API or the MCP server, Sent through shows that mail beside the composer's.
- 03
Check when it started
Switch to a longer window to see whether a rise in bounces is new or has been there all along.
Questions
Asked often
Keep going
Works well with
Start
Your domain,
your mail.
Point a domain at OpenEmail and read it in a mailbox built around it. The free plan covers one domain.