Email analytics

Know your email performance.

See delivery, bounces and complaints by domain, provider, IP or tag. Explore engagement in its own reports, then investigate individual messages. The dashboard and stats API connect your sending activity to the next question worth asking.

Create your account and send a test email to start building your own reporting history.

Set up in:
Cursor

Email performance

Example report

Delivered messages
11,820
Last 7 days
Day 1Day 7
Provider breakdown
Find delivery changes
Message timeline
Investigate a recipient

Illustrative data. Delivery means server acceptance; engagement is measured separately from inbox placement.

The numbers in the API match the numbers in your dashboard.

Email analytics are part of the Bird Email API, not a separate add-on, so the same data the dashboard charts is available to query and export. Use delivery and engagement as diagnostic signals, then measure purchases or completed setup in your application.

Five ways to see your email.

From a single KPI to a per-ISP breakdown.

  1. 01

    Delivery + engagement KPIs.

    Sent, delivered, opens, clicks, bounces, and complaints in a single summary you can pull on demand.

  2. 02

    Choose a documented breakdown.

    Per domain, per ISP, per IP, per sending domain, per recipient domain, per tag or category, per broadcast.

  3. 03

    Bounce + complaint analysis.

    Bounce codes and complaint types broken out, so you fix the cause rather than chase the symptom.

  4. 04

    Mailbox-provider + client breakdowns.

    See how Gmail, Yahoo, Outlook, and Apple Mail treat your mail, and which clients actually open it.

  5. 05

    Daily + hourly granularity.

    Query a day or a single hour. Backfill reports, or stream the numbers into your own dashboards.

Give your reports a first delivery to follow.

Send a test message and inspect the delivery events it produces.

Start tracking delivery

Every chart is a query you can run yourself.

Read the summary, daily or hourly time series and the documented breakdowns. A sending-IP report covers delivery signals rather than engagement attributed to that IP. Responses include data_as_of so your own reporting can show its freshness.

stats.ts
200
// A single summary…
const { data } = await bird.email.stats.summary({
  from: "2026-06-01",
  to:   "2026-06-23",
  tag:  "campaign:spring-2026",
}).safe();
// → { delivery: { delivered, bounce_rate, … }, engagement: { open_rate, … } }

// …or the same metrics, broken down by mailbox provider.
const byProvider = await bird.email.stats.byMailboxProvider({
  from: "2026-06-01",
  to:   "2026-06-23",
});
// → gmail, yahoo, microsoft, apple … each with its own rates

Understand what an open measures.

Apple Mail Privacy Protection and Gmail's image proxy pre-fetch images on the recipient's behalf, registering opens no human triggered. Bird flags recognized prefetched opens and excludes them from the reported open rate. A remaining open still does not prove a person read the message. Clicks carry no such flag, and security systems follow links to check them, so treat a click as a recorded request too and judge a decision on what people complete in your own application.

Then see where it actually landed.

Delivered means the receiving server said yes. Whether the message reached the inbox or the spam folder is a separate question, and your own event stream cannot answer it. Two more views in the dashboard can, because they read from a panel of real mailboxes rather than from your sends.

Inbox Insights measures inbox and spam placement per mailbox provider for your verified sending domains, then lets you register seed tests: a batch of real addresses you include in a send, measured at the mailboxes themselves. Read the Inbox Insights guide.

Competitive Insights points the same panel at the brands you name: their send volume, cadence, inbox placement, read rates, and the campaigns themselves, in a watchlist beside your own measured figures. Read the Competitive Insights guide.

Go deeper in the docs.

See what's tracked in the tracking & metrics guide, and wire near-real-time data into your stack with email events and webhooks.

Put it into practice.

Continue with the documentation, guides and examples for this topic. Resources are in English.

Get an implementation brief

Questions about analytics

Which metrics can I review?
Review delivery, recorded opens and clicks, bounces, complaints and latency. Breakdowns cover sending domains, recipient domains, mailbox providers, tags, templates and broadcasts. Sending-IP breakdowns show delivery signals; engagement is not attributed to the IP that carried the message.
How fresh are the metrics?
Stats aggregate the event stream with a short delay and return data_as_of. They use event time, so a click today can belong to a message sent earlier. Daily and hourly endpoints support the windows documented in the stats guide.
Do these reports show inbox placement or revenue?
Delivery means acceptance by a receiving server. Use Inbox Insights for placement estimates and Competitive Insights for panel-observed competitor activity. For revenue or activation, connect campaign context to completed actions in your own application.

Understand what happened after the send.

Review delivery, bounces and engagement in your workspace. Use the provider and domain breakdowns to decide what to investigate next.

Create your account and send a test email to start building your own reporting history.

Start with one channel.
Add the others when you're ready.

A test API key is yours immediately. Production unlocks when you add a payment method and verify a sender.

Using Claude Code, Cursor, or Codex? Copy a setup prompt and your agent installs the Bird CLI and skills for you. Pick yours:

Cursor