A marketing analytics dashboard built around opens, clicks and conversions tells you almost nothing about whether mail is reaching the inbox. Deliverability has its own metrics, pulled from different sources, and they predict problems days or weeks before engagement numbers move.
The metrics that actually belong on a deliverability dashboard
| Metric | Source | What it predicts |
|---|---|---|
| Spam-rate band | Google Postmaster Tools (domain-verified) | Google's bulk-sender enforcement risk (threshold: 0.30%) |
| DMARC pass rate | Aggregate (rua) reports | Whether SPF/DKIM alignment is actually working in practice |
| Hard bounce rate | ESP/SMTP logs | List decay, bad data entering the funnel |
| Soft bounce rate (trend) | ESP/SMTP logs | Throttling or rate-limiting by a receiving provider |
| Complaint rate | Feedback loops, or implied from unsubscribe-vs-complaint ratio | Earliest warning before spam-rate crosses a threshold |
| Inbox vs spam placement | Seed-inbox test | The one direct measure of where mail actually lands |
Why this list looks different from a marketing dashboard
Marketing dashboards are built to answer "did this campaign work," which is a conversion question. Deliverability metrics answer "can this domain reliably reach anyone at all," which is an infrastructure question underneath every campaign. A campaign can have excellent subject-line testing and a perfectly segmented list and still underperform because the domain's spam rate crossed 0.30% the week before - a fact no amount of campaign-level analysis will surface.
Building a lightweight version of this with what you already have
- Verify the sending domain in Google Postmaster Tools. This alone gives spam-rate, authentication status, and delivery-error data for Gmail-bound mail, and since 2026 includes a Deliverability analysis view covering a broader read on sending health.
- Set up a DMARC aggregate-report address and either read the raw XML periodically or use a free aggregator to summarize it - this is the only direct signal on whether authentication is actually passing in the field, not just configured correctly.
- Pull bounce and complaint data from your ESP's API or export on a weekly cadence rather than per-campaign, so trend lines are visible across campaigns rather than reset each time.
- Run a seed-inbox placement check periodically, not just when a problem is suspected - placement is the only metric on this list that directly answers "did it land in the inbox," everything else is a proxy.
Where this data disagrees with your ESP's own dashboard
An ESP's built-in reporting typically shows delivery rate (not hard-bounced) and open rate, both of which can look healthy while placement quietly shifts to spam - a 98% delivery rate only means the receiving server accepted the message, and an open rate inflated by Apple Mail Privacy Protection or Gmail's image-proxy prefetching doesn't confirm a human read it in the inbox. The metrics above exist specifically because the ESP-native numbers can't answer the placement question on their own.
A worked comparison: two accounts with identical delivery rate
| Account A | Account B | |
|---|---|---|
| ESP-reported delivery rate | 98.2% | 98.4% |
| Open rate | 31% | 29% |
| Postmaster spam-rate band | 0.00%-0.10% | 0.30%-0.50% |
| DMARC pass rate | 99.1% | 71.6% |
| Seed-inbox placement (Gmail) | Inbox | Spam |
Account A and B look nearly identical on the two metrics most dashboards show by default. The difference only appears on the four rows a standard ESP dashboard doesn't surface at all. Account B's DMARC pass rate of 71.6% means roughly three in ten messages are failing alignment somewhere - most likely a secondary sending tool missing from SPF - and Google's own spam-rate band has already crossed the 0.30% enforcement threshold as a result. Nothing in "delivery rate" or "open rate" would have caught this until complaints or a full Gmail block followed.
Where to actually pull each number from
- Spam-rate band and Deliverability analysis: Google Postmaster Tools, domain-verified via a DNS TXT record - this takes a few minutes to set up and has no cost.
- DMARC pass rate: parse the
ruaaggregate XML reports, either by hand for a small volume or with a free DMARC report parser once volume makes manual XML reading impractical. - Bounce and complaint data: your ESP or SMTP relay's own API or CSV export - most platforms expose this even if it's not on the default dashboard view.
- Inbox vs. spam placement: a seed-inbox panel, run on a schedule rather than only when a campaign already looks like it underperformed.
What not to do
- Don't build a dashboard around open rate as the primary deliverability signal - it's an engagement proxy at best, and an increasingly unreliable one given privacy-proxy prefetching.
- Don't check Postmaster Tools or DMARC reports only when a campaign underperforms - by then the spam-rate band has often already been elevated for days.
- Don't conflate delivery rate with deliverability in reporting to stakeholders - the two numbers measure different things, and presenting one as the other hides real risk.
MailPilot tracks per-mailbox reputation daily, checks SPF/DKIM/DMARC against what's actually published, and runs real seed-inbox placement tests per provider - the underlying signals this kind of dashboard needs, collected automatically rather than pulled by hand from five different places.
Ready to reach the inbox every time?
Automated email warmup across real peer mailboxes. Live inbox placement monitoring. Free 7-day trial - no credit card required.
Start free trial