Skip to content

SendingAnalytics and delivery reports

Analytics and delivery reports

Analytics shows how much mail you send and receive, what happened to it, and which conversations still need a reply. A report can cover the whole organization or a few mailboxes. The URL keeps your filters, so a teammate with access can open the same view.

Last updated

The four views

ViewWhat it shows
OverviewMessage volume, delivery KPIs, current reply workload, and quota context.
DeliveryRecipient outcomes, event investigation, reputation, and domain health.
ActivityCurrent reply workload and historical response and mailbox activity.
SuppressionsOrganization-wide addresses blocked from sending.

Choose the report scope

Pick a preset period or custom dates, then a time zone and a message source. The time zone sets where each day starts and ends. You can pick several mailboxes at once, either by including only the ones you want or by excluding some from everything you can access.

  • Search mailboxes by address, name, or domain.
  • Reuse a mailbox group, or save the current selection as a new group.
  • With organization-wide access, inactive and suspended mailboxes keep their history and show as historical activity. With restricted access, you see the non-suspended mailboxes you can access. A temporary readiness issue does not remove their history.
  • Copy the URL to share the period, source, time zone, mailbox selection, and view.
  • Changing a filter starts a fresh report and sends delivery results back to page one.

Report cutoffs and current state

Each report shows an As of time. Paging through delivery results, coming back from a message, and downloading a CSV all keep that cutoff. The underlying records can still change later, so a report is not a frozen archive. Choose Refresh to now to move the cutoff to now. Changing a filter also starts a fresh report.

Period metrics use the dates at the top of the report. Some cards describe the organization right now instead: current reply workload (for mailboxes that are ready for mail), current sending state, and quota usage. Their labels say they are current.

Historical response metrics pair each incoming message with the next eligible outgoing message in the same Shipmail conversation and mailbox. They do not prove that a person wrote the reply.

Current reply workload uses the live needs-reply state. A conversation counts when its newest inbound message is later than its newest tracked outbound message. Conversations already handled as due follow-ups don't count. The inbox action can also include other work, such as due follow-ups, so its count can be higher than the analytics card.

Recipient outcomes and the event timeline

Latest outcomes lists the recipients of outbound messages created in the selected period. Each recipient shows the latest outcome Shipmail saw before the report cutoff. Pending means the message is queued or accepted and the provider has not reported anything since.

Event timeline lists every delivery event, so one recipient can appear several times. It covers at most the last 30 days of the selected period. Search by recipient, subject, or message ID, and filter by delivery status.

Delivery rate counts only known provider outcomes. It leaves out pending sends and addresses suppressed before sending. It does not tell you whether mail landed in the inbox or in spam. The deliverability guide covers how to look into a change.

Read the deliverability guide.

Delivery by provider

The Delivery view splits recipient outcomes by mail provider: Gmail, Outlook and Hotmail, Yahoo and AOL, iCloud, and other domains. Each row shows recipients, delivery rate, bounces, deferrals, and complaints. A drop at one provider shows up here even when the overall rate looks normal.

Shipmail reads the provider from the recipient's domain. A business address hosted by Google Workspace or Microsoft 365 counts as other domains.

Why a delivery failed

Open a bounced or deferred event to see the cause in plain language and what to do next. Shipmail recognizes these causes:

  • a full mailbox
  • an unknown or disabled address
  • a domain that does not receive email
  • a message that is too large
  • a failed SPF, DKIM, or DMARC check
  • a blocklisted sending server
  • a provider rate limit
  • a spam rejection

If the server response matches none of these, the explanation says so and shows the raw response.

Suppressions and CSV exports

The Suppressions view searches the whole organization list, not only the page you are on. Filter by bounced, complained, or manually blocked addresses. Remove an address to allow sends to it again.

The report menu exports volume or delivery data with the filters and snapshot you have open. One CSV export holds up to 5,000 rows, so narrow the report if it has more. The file escapes values that a spreadsheet would otherwise run as formulas.

Open Analytics in the dashboard to build a report. Your filters stay in the address bar as query parameters, such as range, tz, andsource.

Blocklist alerts

Every 6 hours, Shipmail looks up each verified domain on the Spamhaus Domain Blocklist. If a domain is listed, the organization owner gets an email explaining what the listing means and how to ask for removal. A second email follows when Spamhaus removes the domain. If a lookup gets no answer, nothing changes and no email goes out.

Share a domain health report

On a domain's Overview tab, Share report creates a link that anyone can open without a Shipmail account. The report shows whether the MX, SPF, DKIM and DMARC records pass, whether the Spamhaus Domain Blocklist lists the domain, and the last 30 days of delivery from the domain's mailboxes, split by recipient provider. It shows nothing else from your account.

Organization administrators create and turn off links. A link works for 30 days. A domain has one live link at a time, so creating a new one turns off the old one. Turn off link stops a link at once. Shipmail stores only a hash of the link, so it can't show you an existing link again. To read the same data from code, call GET /v1/domains/{id}/health or the MCP tool shipmail_get_domain_health.