When your application sends a password reset or an order confirmation, “sent” isn’t enough. You need to know whether it was delivered, bounced or opened, especially when a customer in Saskatoon calls to say they never got their receipt. Mailpro’s API statistics give you that answer per message and in aggregate.
What is tracked
- Accepted: the API received your request and queued the message.
- Delivered: the recipient’s server accepted it.
- Bounced: hard bounces (invalid address) and soft bounces (temporary issue such as a full mailbox).
- Opened and clicked: engagement, where tracking is enabled.
- Unsubscribed or complained: relevant if any API stream carries commercial content.
Our FAQ on delivery status for transactional email describes each status in detail.
Three ways to read the data
In the dashboard
The Mailpro interface shows totals and trends over time, plus global statistics across all sending channels. Useful for managers and support teams.
Through the API
Query message status by ID from your own code. The API documentation lists the endpoints.
By webhook
Receive events in real time at your endpoint. For example, mark an address as invalid in your database the moment a hard bounce arrives. The webhook documentation and our FAQ on webhook types show how.
Using statistics in a Canadian context
Support in two languages
If you send English and French versions of transactional templates, compare their delivery and click rates. A lower click rate on the French password-reset email may reveal a translation or button-label issue.
Regional patterns
Geographic tracking shows where messages are opened. For a national retailer, that can confirm, for example, that shipping notifications to remote communities are being read.
Proof for your records
Delivery logs help document that you sent important notices, which is useful for customer disputes and for demonstrating good practice. Remember that logs contain personal information: under PIPEDA, keep them only as long as needed. Mailpro stores statistics in Switzerland, outside US jurisdiction.
Which metric matters for which message
| Message type | Key metric | Why |
|---|---|---|
| Password reset | Delivery time and delivery rate | Users wait for it; delays create support calls |
| Order confirmation | Delivery rate and bounces | A bounce often means a mistyped address at checkout |
| Shipping notice | Clicks on the tracking link | Shows whether customers use the information |
| Invoice or statement | Opens and delivery proof | Useful in payment follow-ups |
When a customer says “I never got it”
A short routine helps support teams answer quickly, in either language:
- Search the message by recipient address and date.
- If it shows as delivered, ask the customer to check spam or promotions folders and to add your sender address to their contacts.
- If it bounced, check the address for typos (a common one is a missing letter in the domain) and correct it in your application.
- If it is still queued or soft-bounced, the recipient’s server may be delaying mail; the message will usually be retried automatically.
- If the address is on a suppression list because of an earlier hard bounce, confirm the address with the customer before removing it.
Keeping delivery healthy
- Authenticate your domain with SPF, DKIM and DMARC.
- Remove hard-bounced addresses immediately.
- Keep transactional and marketing traffic separate so promotional complaints don’t affect receipts.
In Mailpro’s own customer survey, email deliverability is rated 9.6/10. To choose between integration methods, see API vs SMTP, or go back to the email API overview for Canada.