Email reporting: see what happened to every message

Email reporting in 2Mail is a real-time dashboard per sending domain that shows for every message whether it was delivered, deferred, bounced or rejected, with the receiving server's literal response. On top of that you see opens and clicks, bounce and complaint rates and searchable logs, and you pull the same data into your own systems through webhooks or the API.

A send button says nothing about arriving. This page shows what you get to see after a send, which numbers really count and how you evaluate a campaign in four steps. Anyone who wants to see the dashboard beforehand gets a free live demo with anonymised data.

Four statuses, one answer from the recipient

Every message that leaves through 2Mail gets a status. More important than the label is what sits behind it: the reaction of the receiving mail server, logged word for word.

Delivered

The receiving server accepted the message. That is where our responsibility ends and the mailbox decides: inbox, promotions or spam folder. 2Mail hands the message over within 10 seconds of receiving it.

Deferred

The recipient asks us to come back later, usually because of greylisting or throttling. The platform retries automatically. Lots of deferrals at one provider are a sign that your volume or reputation there still has to grow.

Bounced

The message definitively did not arrive: the address does not exist (hard bounce) or the mailbox was temporarily unreachable (soft bounce). Bounces are processed automatically and the address is flagged in your contacts.

Rejected

The receiving server deliberately refused the message, for instance because SPF or DKIM did not check out, your domain is on a blocklist or the content was judged to be spam. The reason is in the server response.

The difference between bounced and rejected determines what you do: after a bounce you clean the list, after a rejection you look at your authentication, your reputation or your content. That is why we show the server's response verbatim, not just a colour code.

What else the dashboard shows you

Beyond the status per message, the dashboard bundles per domain everything you need to judge a campaign or a transactional flow. All figures are updated in real time.

Open and click tracking per campaign and per contact, with device and location detection.
Bounce rate and complaint rate per domain, so you spot a problem before it hits your reputation.
Searchable logs: search by recipient, subject, period or status and read the server response.
Separate statistics per sending domain and per application, thanks to the own login per application.
Unsubscribes and complaints per campaign, next to the opens and clicks, in the same view.
Tracking and storage run on our own servers in Belgium; no behavioural data goes to third parties.

Which numbers matter, and which matter less

Not every figure in a dashboard is equally reliable. This is the order in which we look at them, from hard to soft.

1 Delivery rate: the share of messages the receiving server accepted. This is the only number you fully control yourself, through your list and your authentication.
2 Bounce rate: should stay low. If it rises, your list is outdated or you imported addresses without cleaning them.
3 Complaint rate: the share of recipients who clicked 'spam'. Even a small percentage weighs heavily with mailbox providers; this is the number to watch first.
4 Clicks: the strongest sign that someone actually read your message and found it interesting. A click requires a human action, which makes it more reliable than an open.
5 Opens: an indication, not a measurement. Several mailboxes preload images through a privacy proxy, which registers an open without anyone having looked at the message.

In short: arriving weighs more than opens. A falling open rate at equal clicks often says more about your recipients' mailboxes than about your campaign. So compare opens only over time within your own list, and do not draw conclusions from a single send.

Read about deliverability

Reporting in your own systems

The dashboard is one way to look at the numbers. If you want them in your CRM, your webshop or your own reporting tool, you pull the same data through webhooks or the REST API.

Signed webhooks

2Mail sends a message to your endpoint on every delivery, bounce and open. Every call is signed, so your application can verify it really comes from us. That way the status of an order confirmation sits right next to the order in your own system.

REST API with a key per application

Every application gets its own API key that you can revoke separately. You query the status of messages, build your own overviews or automate bounce follow-up without having to look at the dashboard.

Go to the email API Transactional email

Evaluating a campaign in four steps

An hour after the send you already know most of it. Walk through these four steps in this order and you will draw the right conclusion, not the easiest one.

1

Check delivery first

Open the domain's statistics and look at the split between delivered, deferred, bounced and rejected. If a lot is still stuck in deferred at one provider, hold off on judging: the retries are still running.

2

Read the server responses for bounces and rejections

Filter the logs on rejected and read what the receiving server says. An authentication error, a blocklist or a content filter each call for a different fix. For bounces, look for patterns: all at the same domain, or spread out?

3

Look at complaints before opens

Go to the complaint rate and the unsubscribes. If they are higher than in previous campaigns, something was off in the segment, the frequency or the expectation you set in the subject line. Only then do you look at opens and clicks.

4

Write down what you will do differently next time

Note one concrete adjustment: clean addresses, shrink a segment, rewrite a subject line. Compare the next send on the same numbers. One change at a time makes the effect measurable.

Request a live demo All about email marketing

Frequently asked questions about email reporting

The status (delivered, deferred, bounced or rejected), the timestamp and the receiving mail server's literal response. You also see per contact whether the message was opened and which links were clicked, with device and location detection.
A bounce means the address does not exist or the mailbox was unreachable; the problem is in your list. A rejection means the receiving server deliberately refused the message, for instance because of an authentication error, a blocklist or a content filter; the problem is with your domain or your content. The server response in the logs tells you which of the two it is.
Only partly. Several mailboxes preload images through a privacy proxy, which registers an open without anyone having looked at the message. Use opens to follow trends within your own list, but base decisions on delivery, complaints and clicks instead.
Through an invisible image for opens and through redirected links for clicks. That tracking runs on 2Mail's own servers in Belgium; no behavioural data goes to third parties.
Yes. Through signed webhooks your application receives a message on every delivery, bounce and open, and through the REST API you query the status of messages. Every application uses its own API key that you can revoke separately.
Yes. A free live demo of the dashboard with anonymised data is available, without registration. That way you see in advance what the statistics per domain and the logs per message look like.
Call us
Send an email