Use delivery evidence.
A delivered event records acceptance by the receiving server. Compare provider, domain and sending stream before investigating one message.
Read the measurement guide ↗EmailAnalytics
Email analytics.
Follow the evidence.
Move from a delivery question to the provider, stream, and message behind it. Give your team a clearer place to investigate and improve.
From the whole picture to one useful detail.
See which messages were delivered, where sending needs attention and how performance changes over time. Filter the example report to follow a campaign down to its delivery events.
3Distinct Bird-accepted messages
1/3 · 33%Receiver-delivered / accepted
1Bounced messages
Delivered by event time.
Seven chart buckets. Select a bar to inspect its underlying events; select it again to return to the filtered cohort.
UNDERLYING FICTIONAL EVENTS
Gmail / transactional / 72026-09-17 em_t1 accepted → delivered → delivered → opened 2026-09-16 em_t2 accepted → bounced 2026-09-12 em_t3 accepted
No matching event appears in this fictional selection. An empty cohort has no delivery-rate denominator.
Metrics count distinct messages. Duplicate delivery events are ignored; the late event for em_t3 belongs to 12 September. Receiver acceptance does not establish inbox placement or a human read.
Measure the right outcome ↗Companies that trust Bird across their communications.
Read Bird customer storiesMeasure what the signal establishes.
Keep placement separate.
An open or click is a recorded event, influenced by privacy features and automated clients. Use placement tests for mailbox observations and your application for completed outcomes.
Understand tracking and metrics ↗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.
Delivery + engagement KPIs.
Sent, delivered, opens, clicks, bounces, and complaints in a single summary you can pull on demand.
Choose a documented breakdown.
Per domain, per ISP, per IP, per sending domain, per recipient domain, per tag or category, per broadcast.
Bounce + complaint analysis.
Bounce codes and complaint types broken out, so you fix the cause rather than chase the symptom.
Mailbox-provider + client breakdowns.
See how Gmail, Yahoo, Outlook, and Apple Mail treat your mail, and which clients actually open it.
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.
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.
Watch the guideWhy your sending domain is throttledFollow the learning pathOperate messaging reliably
Get an implementation brief161%
Increase in email open rates reported in Zillow’s customer story.
Built with Bird
When the right home appears, the email needs to arrive.
Zillow brought time-sensitive property alerts to Bird, with the capacity to handle sending surges and the analytics to understand engagement. Its team reported a 161% increase in open rates in the first month.
Planning a migration or a higher-volume send?
Contact salesQuestions 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.
Turn reporting into a next step
Inbox Insights
Investigate estimated placement when delivery events do not explain inbox performance.
Competitive Insights
Compare other brands’ campaign patterns with your own program.
Deliverability
Authentication, IP warmup, suppression, and per-provider visibility.
Email API overview
The full Email API: sending, deliverability, IPs, suppression, analytics, and broadcasts.
Talk to our email team
Make sense of your email delivery.
Talk through delivery reporting, webhook events and the signals your team needs. You can also start with a test send and explore analytics in your workspace.
Create your account and send a test email to start building your own reporting history.