Supported source · Amazon SES
BigStats subscribes to your SES configuration-set events over Amazon SNS and turns sends, deliveries, delays and bounces into per-provider delivery health, bounce forensics and alerts — in the same dashboard as your self-hosted MTAs.
SES event → BigStats
SNS HTTPS subscription → https://bigstats.email/api/public/ingest/ses?key=ga_live_…
{"eventType":"Bounce","mail":{"destination":["user@gmail.com"]},
"bounce":{"bounceType":"Permanent","bounceSubType":"General",
"diagnosticCode":"550 5.1.1 user unknown"}}
→ signature verified · classified: hard · invalid_recipient · isp=gmailEvent coverage
Every send and successful delivery, counted once per recipient — so a campaign to 1,000 people reports 1,000 messages, not a pile of attempts.
SES's deferred-delivery signal, tracked as a deferral with recovery detection — when the retry lands, the message flips to delivered and the incident clears itself.
SES bounce type, subtype and the remote diagnostic response, classified into invalid recipient, mailbox full, blocklisted, throttled, policy or authentication failures.
Feedback-loop complaints as a first-class rate, per provider and per tenant, with thresholds and anomaly alerts.
Mail SES refused to send, kept separate from post-send failures so configuration problems are not confused with delivery problems.
Connect it
01
Each BigStats workspace issues its own ingest key and SES endpoint. Nothing in your sending configuration changes.
02
Add an SNS event destination to your SES configuration set and subscribe the BigStats endpoint. The subscription handshake confirms automatically.
03
Events are verified against Amazon's signing certificate, normalized and queryable immediately — no batch window.
The onboarding wizard walks through the SES setup step by step, and Settings → Amazon SES has the same instructions with your ingest URL and key. Add a tenant message tag to split reporting per client.
Delivered, bounced and deferred with recovery tracking, period-over-period deltas and a composite health score.
Gmail, Microsoft, Yahoo, Apple and corporate buckets with delivery, bounce and complaint rates side by side.
SES bounce types and diagnostic text, classified and ranked — the detail a postmaster team asks for.
FAQ
Native SES reporting tells you what SES did. BigStats is built for deliverability work: per-provider and per-MX breakdowns, deferral recovery tracking, bounce forensics grouped by the receiver's actual diagnostic text, sending-IP blocklist monitoring, and alerts that escalate until someone owns the incident. Our pricing page has a side-by-side comparison.
No. BigStats only receives event notifications through SNS. It never touches your configuration sets, sending quotas or message content, and an ingest failure on our side does not affect your sending.
Yes. The configuration set name becomes the Virtual MTA, so multiple configuration sets report as separate streams, and a tenant message tag splits reporting per client — the SES equivalent of per-customer subaccounts.
SES does not report which shared IP sent a given message, so shared-pool sending appears as "SES shared" rather than per-IP. Dedicated IP pools report by pool name with per-pool breakdowns, and blocklist monitoring covers dedicated IPs — Amazon manages the shared pool's reputation itself.
Every notification's signature is verified against Amazon's published signing certificate before it is accepted, on top of your per-workspace ingest key. Unauthenticated or forged payloads are rejected.