Start before submission.
Confirm domain authentication and recipient eligibility. Preserve suppressions and unsubscribe preferences when traffic moves between providers or applications.
Prepare authentication ↗EmailDeliverability
Care for the inbox.
Before you press send.
Build a sending program around authentication, recipient care and delivery evidence. Use the right signal to decide what needs attention next.
A closer look
A considered start. A healthier next send.
Authentication, sending reputation and recipient expectations work together. Receiver acceptance alone does not establish inbox placement.
Follow a message
Delivery signals
01
Authenticate the sender
DKIM · SPF · DMARC
02
Check the recipient
Preferences and suppressions
03
Read the delivery response
Accepted, deferred or bounced
A separate measurement
Did it reach the inbox?
Investigate placement with Inbox Insights and seed tests.
Workflow illustration. Recipient mail servers determine placement; a delivered event records acceptance.
LOCAL WALKTHROUGH
Follow the question to its evidence.
Choose an illustrative situation to see the next action. This walkthrough does not query your account, verify a domain or send a message.
NEXT ACTION
Authentication check failed
Inspect the generated DNS records and workspace verification result. Correct the specific missing or misaligned record before testing a production send.
Receiver deferred or bounced
Read the recipient event and receiver response, then compare the affected provider and sending stream. Avoid inferring a universal reputation cause from one failure.
Delivered, but inbox placement unclear
A delivery event means receiver acceptance. Use a scoped placement test with coverage and capture time to investigate inbox or spam observations.
Companies that trust Bird across their communications.
Read Bird customer storiesChoose the symptom. Read the evidence.
Investigate after acceptance.
Follow the message events to see a receiver response. Use a scoped placement test when the question concerns inbox or spam, and retain unknown or missing observations.
Follow the deliverability guide ↗Looking for inbox placement monitoring?
Delivery events tell you whether a recipient server accepted a message. Inbox placement is a separate question. Use Inbox Insights to investigate inbox versus spam placement for your verified domains and test a campaign with seed addresses.
Explore Inbox InsightsDeliverability is a feature, not a hope.
The Bird Email API combines domain authentication, managed warmup for dedicated IPs, recipient suppressions and sending metrics. Your team still controls consent, content and audience quality. Use the appropriate signal for the question: sending events for delivery and Inbox Insights for estimated placement.
Five things working for you on every send.
Domain setup, sending controls and delivery feedback work together.
Authenticated sending.
Verify your sending domain and publish its authentication records. DKIM signs messages, SPF identifies authorized sending infrastructure, and a DMARC policy tells receivers how to handle authentication failures.
Managed IP warmup.
Start on a shared pool, or take dedicated IPs that Bird warms automatically over roughly 30 days and organizes into pools you control.
Automatic suppression.
Hard bounces block delivery to an address; complaints block non-transactional mail. Unsubscribe preferences are stored separately and checked when processing a send.
Message-level diagnosis.
Inspect a recipient’s event timeline and receiving-server response in the email log. Use that response to identify the next configuration or sending change to investigate.
Per-provider visibility.
Bounce codes, complaint types, and mailbox-provider and client breakdowns, broken out per domain, ISP, and IP, in the dashboard and via the stats API.
You don't write deliverability. You watch it.
Configure your domain authentication, IP warmup and suppression workflow, then review the sending results. Pull bounce and complaint rates, mailbox-provider breakdowns and bounce codes from the stats API to investigate a changing trend.
reputation.ts
200
// Watch the rates that decide whether you reach the inbox.
const { data, error } = await bird.email.stats.summary({
from: "2026-06-01",
to: "2026-06-23",
}).safe();
if (error) throw error;
console.log(data.delivery.bounce_rate); // 0.004
console.log(data.delivery.complaint_rate); // 0.0006
console.log(data.delivery.delivered); // 248119
What healthy sending looks like.
The Metrics dashboard classifies delivery, bounce and complaint signals as Healthy, Watching or Throttled. Those labels describe risk; they do not automatically change your sending rate or pause mail. Investigate the affected domain, provider or audience and pause a campaign yourself when its source data needs attention.
Go deeper in the docs.
Set up authentication with the DKIM, SPF & DMARC guide, plan a ramp with the IP warmup guide, or read the full deliverability guide for the playbook end to end.
Compare deliverability approaches
Bird vs Validity EngageCompare measurement and remediation, then follow the monitoring transition guide.Bird vs GlockAppsCompare measurement and remediation, then follow the monitoring transition guide.Bird vs InboxAllyCompare measurement and remediation, then follow the monitoring transition guide.Bird vs WarmyCompare measurement and remediation, then follow the monitoring transition guide.
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Watch the guideWhat happens between send and the inboxUnderstand the conceptWhat are bounced emails?Follow the learning pathOperate messaging reliably
Try the practice and 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 deliverability
What can Bird help me control?
Bird provides domain authentication, dedicated IP pools with managed warmup, recipient suppressions, preferences and sending metrics. Your team controls consent, content and sending behavior. Inbox Insights measures placement separately.
How do I investigate a decline?
Use the stats API and dashboard to review bounce reasons, complaints, sending domains and mailbox-provider breakdowns. Inspect a specific recipient in the email log. Use Inbox Insights to investigate placement estimates and run campaign seed tests.
Do health classifications automatically pause sending?
No. Healthy, Watching and Throttled classify sending risk. They do not change your sending rate or pause traffic. Investigate the affected campaign or list and decide whether to pause it.
What happens after a bounce, complaint or unsubscribe?
Hard bounces create a suppression that blocks mail to the address. Complaints block non-transactional mail. Unsubscribes record a preference separately. Transactional delivery still depends on the address being valid and on any other blocking records.
Choose the control you need
Email validation
Check recipient addresses before sending and investigate address-quality problems.
Sending domains
Domain verification, DKIM signing, SPF alignment and DMARC policy setup.
Dedicated IPs
Managed dedicated IPs and pools, warmed automatically.
Suppressions
Recipient suppressions and opt-out preferences checked before delivery.
Analytics
Delivery by domain, provider and IP, with separate engagement breakdowns.
Email API overview
The full Email API: sending, deliverability, IPs, suppression, analytics, and broadcasts.
Talk to our email team
Make your next delivery issue easier to investigate.
Bring your authentication, sending reputation and delivery questions. Discuss a migration, a growing email program or the monitoring your team needs.