Question 1

Which MTAs can send data to BigStats?

Accepted Answer

GreenArrow Email Engine and KumoMTA are both supported today. GreenArrow connects through its Event Notification System and KumoMTA through an HTTP log hook posting JSON log records; each has its own ingest endpoint but everything lands in the same reports, exports, alerts and API. Any other system that can POST JSON events can also be pointed at an ingest key.

Question 2

What does KumoMTA reporting cover?

Accepted Answer

BigStats maps KumoMTA's Reception, Delivery, Bounce, TransientFailure, Expiration, AdminBounce, OOB, Feedback and Rejection records onto its own event model, keeping the SMTP reply code, enhanced status code, response text, peer MTA, egress pool and source IP. KumoMTA does not generate open or click events itself, so those streams stay empty unless another system supplies them.

Question 3

How is bounce data classified?

Accepted Answer

Every bounce is parsed for its SMTP reply code, enhanced DSN status and diagnostic text, then classified as hard, soft or block and bucketed into categories such as invalid recipient, mailbox full, blocklisted, throttled, policy/content, authentication/DMARC, greylisted, relay denied or network. The original response text is always retained for review.

Question 4

Can I see performance per receiving domain and ISP?

Accepted Answer

Yes. Every recipient domain is tracked individually and rolled into Gmail, Microsoft, Yahoo, Apple and corporate groups, with delivery, deferral, bounce, open, click and complaint rates side by side so you can spot a single-mailbox-provider problem before it becomes a reputation problem.

Question 5

Do you track sending IP and VMTA level reputation?

Accepted Answer

Sending IP, VMTA/binding and remote MTA are captured on every event, so you can compare bounce and deferral pressure across your IP pool and isolate a warming IP or a single binding that's dragging inbox placement down.

Question 6

How quickly does data appear?

Accepted Answer

Events are ingested as your MTA emits them and are queryable immediately — there is no batch window. Rollups are maintained continuously so reports stay fast at high volume.

Question 7

What can I export, and how?

Accepted Answer

Choose exactly the elements you need — opens, clicks, unsubscribes, complaints and detailed bounce fields including SMTP code, DSN, diagnostic text and sending IP — then download as CSV or pull the same data through a read-only, token-authenticated JSON API.

Question 8

How is our data isolated?

Accepted Answer

Each workspace has its own ingest keys and API tokens, and all data access is enforced at the database with row-level security. Members only ever see the workspaces they belong to.

Question 9

How does BigStats handle GDPR and data privacy?

Accepted Answer

BigStats processes the event data your MTA sends us on your instructions, as a processor acting for you as controller. Our Data Processing Agreement sets out the processing terms, security commitments and sub-processor handling, and our Privacy Policy describes what we collect and why. Both are published on this site and BigStats.email is happy to discuss customer-specific requirements at hello@bigstats.email.

Question 10

What personal data ends up in BigStats, and how long is it kept?

Accepted Answer

Event notifications include recipient addresses and delivery metadata such as receiving domain, SMTP and DSN responses, sending IP and timestamps. Raw events are pruned automatically on a retention window you set per workspace — 7, 14, 30, 45, 60 or 90 days, defaulting to 45 — while the aggregated statistics used for reporting contain no recipient addresses and are unaffected. Access is restricted to members of your workspace and enforced at the database with row-level security.

Question 11

Can you delete or export data for a specific recipient?

Accepted Answer

Yes. Recipient-level data can be searched and exported so you can respond to access requests, and workspace owners and admins can erase every stored event for a single address themselves from the dashboard's data privacy settings. Whole-workspace deletion and anything else can be requested at hello@bigstats.email; the handling process and timelines are described in our DPA.

Question 12

Can I see which senders are sharing the same sending IPs?

Accepted Answer

Yes. The Shared Pools report surfaces every sending IP used by more than one sender, and every sender rotating or round-robining across several IPs, with the volume mix and rotation pattern for each. From there you can open a pool detail view showing per-sender delivery, bounce, hard-bounce, deferral and complaint rates, bounce categories and top SMTP codes for that single IP or sender.

Question 13

Can I compare senders, or this period against the last one?

Accepted Answer

Pool detail has a compare-to-previous-period toggle that adds delta chips to every KPI and key column, and row checkboxes that build a side-by-side sender or IP comparison with the best value in each metric highlighted. Each KPI tile is also clickable and drives an hourly or daily trend line with a dashed previous-period overlay.

Question 14

Can I see where a single IP or sender is struggling?

Accepted Answer

Yes. From pool detail you can drill through to a destination view for that one IP or sender, grouped by recipient domain or ISP group, with its own 24h/7d/30d/90d and custom date-range controls and a problems-only filter that isolates the streams with elevated bounce, deferral or complaint pressure.

Question 15

We run several MTAs on different IP ranges. Can they report together?

Accepted Answer

Yes. Clusters group your sending /24 blocks into named sets — one per MTA, region or platform — and a cluster selector filters every report, export, alert and API call to that group, so you can look at one MTA in isolation or the whole estate at once.

Question 16

Can I ask questions about the data instead of building a report?

Accepted Answer

Yes. BigStats includes a built-in AI delivery analyst that answers questions about your workspace's own delivery data, and every chart, tile and table has an "ask about this" control that hands the exact figures to the analyst so the answer is grounded in the numbers on screen.

Question 17

Can I reuse a report configuration?

Accepted Answer

Any combination of filters, groupings, export columns and date window can be saved as a named view with a tag you define. Views are shared with your workspace, sortable by tag or name, and reopening one restores the report exactly as it was saved.

Question 18

Can I connect BigStats to Claude or ChatGPT?

Accepted Answer

Yes. BigStats ships an MCP server with tools for workspace listing, delivery overview, domain breakdown, bounce analysis, event search, shared-pool discovery, per-pool detail and pool destination drill-through. Connect any MCP-capable assistant, approve the workspace scopes, and manage or revoke connected clients and API tokens — with last-used timestamps — from the dashboard.

Question 19

How do you handle very high sending volume?

Accepted Answer

Ingestion accepts batched event posts and writes are rolled up with statement-level aggregation into hourly, domain, IP and bounce summary tables, so reports read pre-aggregated data rather than raw events. The architecture is built for senders pushing hundreds of millions to billions of messages per day.

Question 20

Will I be alerted when something goes wrong?

Accepted Answer

Yes. BigStats watches bounce rate, deferral rate, complaint rate, unsubscribe rate and delivery rate against thresholds you set per workspace, plus per-sending-domain anomalies measured against a rolling 7-day baseline and a watchdog for a silent event feed. Alerts appear in the in-app feed in real time and go out by email, with per-alert cooldowns so an incident can't flood inboxes.

Question 21

Can alerts go to Slack or our own systems?

Accepted Answer

Yes. Every fired alert can fan out to a Slack incoming webhook as a formatted message with a deep link to the alert, and to your own HTTPS endpoint as a JSON payload signed with an HMAC-SHA256 signature header so you can verify it. Both channels have per-alert-type toggles, so bounce spikes can page Slack while unsubscribe alerts stay email-only, and each can be test-fired from the settings panel.

Question 22

What happens if nobody looks at an alert?

Accepted Answer

Unresolved alerts escalate. You set a reminder interval and a maximum number of reminders, and you can override both per alert type so a complaint spike chases harder than a deferral blip. Escalations stop automatically the moment someone acknowledges or resolves the alert in the feed, or when BigStats detects the underlying metric has recovered — the alert is auto-resolved and the reason is recorded.

Question 23

Is there a daily summary instead of individual emails?

Accepted Answer

Yes. A configurable daily digest summarises every still-open alert for a workspace with severity counts and deep links straight into the alert feed. You choose whether it runs, the hour it sends in UTC, the minimum severity to include and who receives it — and it can run alongside or instead of individual alert emails.

Question 24

Does adding BigStats change how mail is sent?

Accepted Answer

No. BigStats only reads. It consumes the event notifications your MTA already produces and never touches queues, routing or message content.

Every message your MTA touches, measured to the DSN.

Your World with BigStats

Sending is solved. Knowing what happened next isn't.

Your MTA tells you it sent. It can't tell you it landed.

Reputation damage compounds while you're not looking.

One bad mailbox provider hides inside an average.

Answers in minutes, not a spreadsheet afternoon.

Delivery health

Domain & ISP breakdown

Bounce forensics

Configurable exports

AI delivery analyst

Saved & tagged views

Shared pools & clusters

Proactive alerting

MCP + JSON API

Bring the sending stack you already run.

GreenArrow Email Engine

KumoMTA

Questions deliverability teams ask first.