Find clear answers about sending, deliverability, and email campaigns.

Inviate agli indirizzi sandbox documentati come delivered@messagebird.dev, bounce@messagebird.dev o complaint@messagebird.dev. Questi simulano risultati e webhook attraverso la pipeline normale. Limitate il pubblico di prova agli indirizzi sandbox; gli indirizzi reali nello stesso invio ricevono email reali.

Il dominio di onboarding supporta un primo invio entro le restrizioni documentate, e gli indirizzi sandbox supportano i test. Verificate il vostro dominio di invio per l'invio regolare. Controllate i limiti attuali del vostro spazio di lavoro anziché fare affidamento su un'assegnazione fissa del piano indicata in questa pagina.

Usate la guida rapida per la prima email per un'integrazione API, la guida SMTP per un'applicazione SMTP esistente, Email marketing per le campagne, o la guida rapida agent-mailbox per le conversazioni. Ogni percorso rimanda alla configurazione e alla documentazione corrispondente.

You can start on the Free plan with its included sending allowance to test integration and delivery. Paid Email plans add a monthly deposit directly to your shared Bird balance, and each email you send is billed from that balance at your plan's published per-email rate without expiring message bundles. Visit the pricing page to compare current deposits, rates, and plan allowances.

If you downgrade your plan, any custom handles you have already claimed continue receiving mail without interruption, and you can claim additional handles once your usage is back within your plan's limit. Mailboxes created on your own verified domain count toward your total mailbox quota without using any of your custom-handle allowance.

Dedicated IPs are available as a monthly add-on on eligible paid Email plans. You can check the current monthly price per IP and the maximum number of dedicated IPs included in each plan tier on the Email pricing page before ordering from the dashboard.

Your sending throughput and monthly allowances depend on your Email plan, with full tier details listed on the Email pricing page and any custom enterprise limits applied automatically. You can check your active rate limits and remaining quota through the API or response headers, and use the returned wait time to pace retries when requests are throttled. API and SMTP traffic share your sending throughput, while batch requests and campaign broadcasts follow their own request limits.

A complete email can be up to 20 MB, including the HTML body, plain text, headers, and encoded attachments. Because attachment encoding adds overhead, keep raw attachment files under 15 MB so the assembled message stays within the limit, and keep in mind that some recipient mail servers enforce smaller size caps.

When content storage is enabled, you can inspect sent message bodies and attachments for up to 30 days. For Agent Mailboxes, parsed headers, extracted text, and attachments stay available for 30, 90, or 365 days depending on the retention tier selected on your plan, while raw MIME payloads are retained for 30 days.

Scope the agent's API key to the specific permissions its workflow requires, and configure mailbox receive rules so untrusted senders do not trigger agent runs. For sensitive outbound communication, have the agent save a draft first so a human or policy check can verify the recipients, sender address, and body before sending.

Sì, entrambe passano attraverso la stessa API di invio. L'unica differenza è il campo category, che determina come si applicano le soppressioni e le disiscrizioni. Scelga transactional per reset password e ricevute, e marketing per le campagne.

Invii un header Idempotency-Key con ogni invio logico. Se la prima richiesta è andata a buon fine ma non ha ricevuto la risposta, reinviandola con la stessa chiave otterrà il risultato originale con un header Idempotency-Replay, anziché inviare l'email due volte.

Imposti scheduled_at su un orario compreso tra 30 secondi e 30 giorni nel futuro. L'invio viene restituito come accettato immediatamente e resta programmato fino alla partenza, quindi può annullarlo in qualsiasi momento prima dell'invio.

Sì, come base64 nell'array attachments. Per mostrare un'immagine inline, le assegni un content_id e la referenzi dall'HTML con cid:. Mantenga i file grezzi a 15 MB o meno affinché il messaggio rientri nel limite di 20 MB una volta codificato, e tenga presente che i content type eseguibili e di script vengono rifiutati prima dell'invio.

Yes. If your application or third-party software already sends email over SMTP, you can switch to Bird without rewriting code by updating the SMTP host, port, and credentials. Verify your sending domain in the dashboard and authenticate with an API key that has email sending permissions.

Connect on port 465 for implicit TLS encryption, or use ports 587 and 2525 with STARTTLS, including port 2525 for cloud environments that block standard mail ports. Point your client to the regional SMTP host that matches your API key; unencrypted submission on port 25 is disabled.

Use SMTP when you want a drop-in relay for existing services, CRMs, or frameworks that already assemble MIME messages. Choose the HTTP API when you want to send with stored templates, schedule deliveries, or pass structured JSON fields from your application code. Both methods share your verified domains, IP pools, suppression lists, and analytics.

SMTP messages are billed at the same published per-email rates as HTTP API sends under your Email plan, with no extra protocol fee. Check the Email pricing page for current plan rates, or talk with our team if you are migrating a high-volume SMTP workload.

Contacts live in your workspace and can store an email address, a phone number, your own external user ID, and custom attributes. Audiences reference those shared contact records, so when a customer updates their email address or profile details, the change carries across the audiences they belong to.

Upload a CSV, TSV, or Excel file in the dashboard, map your columns to contact attributes, and assign the imported contacts straight to an audience. To keep lists synchronized from your application, you can create or update up to 1,000 contacts per request through the API or CLI.

Audiences use explicit membership that you manage by adding or removing contacts through file imports, the dashboard, or the API. When a scheduled broadcast starts sending, Bird resolves the audience's current members so recent additions and removals take effect automatically.

You can define text, number, boolean, and date-time attributes with optional fallback values for missing data. Those attributes plug directly into your email templates so you can personalize subject lines and body copy for each recipient.

Select a saved audience when setting up your broadcast. When sending starts, Bird resolves the current audience members, filters out suppressed or unsubscribed addresses, and personalizes the template with each contact's saved attributes.

Yes. You can send a broadcast immediately or schedule it up to a year in advance, and you can edit or reschedule the campaign before delivery begins. If you cancel a broadcast that is scheduled or in progress, Bird stops delivery to any remaining recipients.

Broadcasts send a campaign to a saved audience up to a year ahead. For individual transactional emails, the sending API lets you schedule a message from 30 seconds to 30 days in advance. When you schedule a transactional send, Bird locks in the template version, language, and personalization values at request time so later edits do not alter your queued message.

Yes. Create a test audience populated with Bird sandbox addresses to simulate deliveries, bounces, and spam complaints without sending mail to real inboxes. Sandbox sends trigger your webhooks and appear in your analytics so you can verify your webhook and analytics integration before launching a live campaign, and they count toward your sending allowance.

Marketing broadcasts and transactional emails share your verified domains, templates, and delivery infrastructure, so you do not have to sync templates or suppression lists across two separate providers. Marketers can compose and schedule broadcasts in the dashboard, and developers can automate audience updates and campaign setup through the API, CLI, or MCP tools.

When you send a marketing broadcast or tag an API send as marketing, Bird includes one-click list-unsubscribe headers and an unsubscribe link for Gmail and Yahoo compliance. When a recipient opts out, Bird records their preference and filters them out of future marketing sends while still allowing transactional receipts and account alerts through.

Each broadcast report tracks delivered messages, human opens with automated privacy proxy prefetches filtered out, link clicks, bounces, and spam complaints. To tie campaigns back to signups or purchases, include UTM or custom link parameters and measure conversions in your product or analytics tool.

Use broadcasts in the dashboard to send newsletters, product announcements, and scheduled promotions to your saved audiences. For event-driven lifecycle emails such as welcome series, onboarding nudges, or cart reminders, trigger templates directly from your application backend using the Email API.

No. You can write and preview HTML templates in the dashboard code editor, or manage template files from your repository using the API, CLI, and MCP tools. If your team builds templates with React Email, you can compile them to HTML with Bird personalization placeholders intact and sync the output to the same drafts and published versions visible in the dashboard.

Templates use Liquid placeholders to merge dynamic data into subject lines, preview text, and message bodies. When you send a broadcast, Bird populates contact placeholders automatically from each recipient's saved profile attributes and fallback values. When you send transactional emails through the API, you can pass custom parameters such as order numbers or line items and use Liquid conditionals and loops to format the message.

Yes. Edits are saved to a working draft while live traffic continues using your currently published version. When you publish a change, Bird creates a version snapshot, and you can roll back to any earlier snapshot with one click if you spot a mistake, without affecting messages that have already been accepted for delivery.

Yes. A single template can store localized subject lines, preview text, and HTML bodies for multiple languages alongside a default fallback language. You can choose whether sends requesting an untranslated locale fall back to your default language or return an error, and preview each locale with sample recipient data before publishing.

Generiamo i record per te: un record TXT DKIM per firmare la tua posta, un CNAME return-path che allinea SPF (nessun record SPF apex richiesto) e un record TXT DMARC. Un CNAME di tracking per link di apertura e clic brandizzati è opzionale. Aggiungi il dominio, incolla i record presso il tuo provider DNS e premi Verifica: la maggior parte delle verifiche si risolve in pochi minuti dalla propagazione DNS, anche se occasionalmente può richiedere più tempo.

DMARC indica ai server riceventi cosa fare con le email che non superano l'allineamento DKIM o SPF e dove inviare i report aggregati che mostrano chi sta inviando per conto del tuo dominio. Richiediamo un record DMARC prima che un dominio possa inviare e raccomandiamo di iniziare con p=none, che monitora senza influire sulla consegna. Una volta confermato che ogni fonte legittima è allineata, rafforza la policy a p=quarantine o p=reject. Se pubblichi già DMARC sul tuo dominio o su un dominio padre, lo utilizziamo così com'è. I principali provider di posta ora si aspettano che i mittenti ad alto volume pubblichino una policy, quindi averne una è sempre più importante per raggiungere la casella di posta su larga scala.

Sì, entrambe le cose, e raccomandiamo un sottodominio dedicato, poiché isola la reputazione email dalla posta aziendale. Puoi anche utilizzare domini separati per email transazionali e marketing, o uno per brand, ciascuno con la propria autenticazione e reputazione.

Considera un IP dedicato quando invii volumi costanti e hai bisogno di controllare la tua reputazione IP. Un mittente con volumi bassi o irregolari potrebbe essere meglio servito dal pool condiviso. Bird riscalda automaticamente un nuovo IP dedicato in circa 30 giorni, con l'eccedenza instradata attraverso l'infrastruttura condivisa durante la rampa. Valuta il tuo pattern di invio con uno specialista email prima di scegliere.

Sì. Raggruppa gli IP in pool e instrada ogni tipo di traffico verso il proprio pool. Questo separa gli IP che trasportano i tuoi flussi di campagna e transazionali. Autenticazione, reputazione del dominio e engagement dei destinatari restano importanti per entrambi.

Bird handles SPF, DKIM, and DMARC authentication, dedicated IP pools with automated warmup, bounce and complaint suppressions, unsubscribe preferences, and real-time delivery analytics. You control list acquisition, message content, and sending cadence, and you can pair those controls with Inbox Insights to monitor inbox placement across providers.

Start in the dashboard or analytics API by breaking down bounce reasons and spam complaints by sending domain and mailbox provider, such as Gmail or Yahoo. You can inspect individual delivery attempts in the email log to see exact server responses, and use Inbox Insights to run seed tests or check whether providers are routing your mail to spam.

No. Health statuses like Healthy, Watching, and Throttled give you an early warning when bounce or complaint rates rise, without automatically pausing your traffic or changing your rate limits. Your team stays in control of whether to pause a broadcast or clean an audience while investigating.

When an address hard bounces, Bird adds it to your suppression list and blocks future sends to protect your sender reputation. Spam complaints and unsubscribes automatically stop future marketing emails to that recipient while allowing critical transactional messages, such as password resets or receipts, to reach valid addresses.

Gli hard bounce creano soppressioni per tutta la posta; i reclami creano soppressioni per la posta non transazionale. Le soppressioni manuali bloccano tutte le categorie. I soft bounce e i differimenti non creano soppressioni permanenti dei destinatari.

Una cancellazione registra la preferenza del destinatario nella scheda Preferenze. È separata dalla lista di soppressione. Entrambe vengono verificate al momento della decisione di consegna, e l'eliminazione di un contatto non cancella il suo opt-out.

Puoi rimuovere una soppressione tramite la dashboard o API dopo averne indagato la causa. Rimuoverne una non rimuove altri record di blocco o preferenze di opt-out. L'indirizzo sandbox suppressed@messagebird.dev ti consente di testare un destinatario rifiutato senza modificare la tua lista.

Usa Email Lookup con una chiave API abilitata per il lookup. Invia un indirizzo e leggi il risultato, la confidenza di consegna, i flag di rischio e l'eventuale suggerimento per errori di battitura. La dashboard, gli SDK e CLI offrono modi per eseguire lo stesso lookup.

I risultati documentati sono valid, neutral, risky, undeliverable e typo. Tratta result come un vocabolario aperto e gestisci i valori futuri usando delivery confidence. Il booleano valid è la valutazione di validità del provider; leggilo insieme a result e confidence, perché non garantisce la consegna.

Proponi il suggerimento di correzione affinché la persona lo confermi; non sostituire mai l'indirizzo in modo silenzioso. Neutral significa che la casella non è stata confermata in nessuno dei due sensi. Combina risultato e confidenza con la tua policy di consenso e invio.

No. Un lookup aiuta a valutare la qualità dell'indirizzo in quel momento. Non stabilisce il consenso, non rimuove le preferenze di opt-out e non garantisce il posizionamento in inbox. Continua a rispettare i record di soppressione e preferenza.

Usa la API batch per valutare fino a 1.000 indirizzi in una singola richiesta, entro il limite di 128 KiB per richiesta. I risultati seguono l'ordine di invio, inclusi i duplicati. Ogni voce con risposta viene fatturata. Controlla i limiti di replay documentati prima di riprovare un batch; questa pagina non fornisce un controllo per il caricamento di liste.

You can track delivered messages, opens, clicks, bounces, spam complaints, and delivery latency. Filter and group performance by sending domain, recipient domain, mailbox provider, tag, template, or broadcast to spot trends quickly. You can also inspect delivery and bounce rates by sending IP to monitor infrastructure health.

Analytics update within minutes as delivery and engagement events arrive, and each report includes a freshness timestamp so you know how current the numbers are. Metrics are recorded when the event happens, meaning a link clicked on Tuesday appears in Tuesday's activity even if the email was sent earlier in the week. You can query hourly or daily rollups across the dashboard and reporting API.

Delivery metrics confirm that the recipient's mail server accepted your message. To see whether accepted emails land in the primary inbox or the spam folder across major providers, use Inbox Insights, and use Competitive Insights to benchmark competing brands. To measure revenue or signups, pass campaign tags or link parameters into your application's analytics.

No. You can generate a Bird forwarding address in seconds and forward emails from your existing inbox to start testing right away. When you are ready to receive mail directly on your own brand, you can configure a receiving subdomain.

Yes. Register and verify a dedicated subdomain in Bird, enable inbound receiving, and publish the provided MX records in your DNS. Using a dedicated subdomain lets Bird process application replies and support tickets while your primary domain continues routing employee mail to Google Workspace or Microsoft 365.

Bird sends a webhook notification to your server as soon as an incoming email arrives, and your app can fetch the parsed subject, plain text, HTML body, headers, and attachments through the API. You can verify webhook signatures to confirm each request came from Bird and rely on automatic retries if your endpoint is temporarily unavailable.

Inbound email turns incoming messages on your receiving domain or forwarding address into structured webhook events and parsed content for your backend. Agent Mailboxes give each AI agent or support workflow a dedicated inbox that tracks multi-turn conversation threads, filters unwanted senders, and sends replies in context.

Inbound email parses incoming messages and forwards them to your webhook endpoint for one-way processing. An agent mailbox gives your AI agent or support app a persistent inbox that groups messages into conversation threads, strips quoted reply history to keep prompts clean, enforces sender admission rules, and sends threaded replies.

Yes. You can create mailboxes on any verified domain or subdomain where you have enabled inbound receiving. For quick setup without DNS changes, you can also provision a generated or custom handle on Bird's managed inbox domain, which stays reserved to your workspace even if you delete the mailbox later.

Parsed message headers, clean extracted text, and attachments are stored for 30, 90, or 365 days based on the retention period you choose for your plan. Raw MIME files and unparsed original bodies are kept for 30 days so you can debug formatting or delivery issues.

Yes. Configure mailbox webhooks to trigger your agent automatically whenever an admitted message lands in the inbox, or connect to the live event stream for real-time updates during an active session. If a streaming connection drops, your agent can list recent thread messages through the API to catch up on anything that arrived while disconnected.

Inbox Insights is the current Bird dashboard experience for inbox placement and seed testing, replacing the older Inbox Tracker name. If your organization uses a standalone eDataSource or legacy Tracker account, you can continue signing in through that platform's existing portal and support team.

Your delivery rate shows how many emails were accepted by recipient mail servers, which includes messages that later get filtered into spam. Inbox Insights shows where those accepted messages actually land across major mailbox providers, breaking down primary inbox versus spam folder placement alongside your delivery metrics.

Verify your sending domain in a workspace with Inbox Insights enabled and turn on domain tracking. Once active, panel placement estimates populate for supported mailbox providers as your domain sends volume, and you can run seed tests using your plan's seed testing allowance.

No. Creating a seed test reserves a set of test addresses for you to include in your campaign audience or pre-send test list before the expiration date. Placement results populate in your dashboard as those seed mailboxes receive your email, and reserving a test uses one test from your allowance.

You can see inbox, spam, and missing counts for each measured mailbox provider, verify that SPF, DKIM, and DMARC passed on the received messages, and compare how engaged versus dormant test mailboxes filtered your campaign.

Inbox Insights is designed for interactive investigation in the Bird dashboard, where you can inspect placement trends and seed test results visually. For programmatic reporting on your sent volume, bounces, opens, and clicks, use the Email analytics API.

Yes. Competitive Insights is the Bird dashboard tool for tracking competing brands and benchmarking their email programs, replacing the older Competitive Tracker name. If your team uses a legacy standalone account, you can continue accessing it through its existing sign-in and support path.

Competitive Insights estimates volume and engagement from a representative panel of consumer mailboxes, tracking each watched brand's primary high-volume sending domain. Mail sent from secondary domains or very low-volume senders may not appear in the panel sample.

Yes. The campaign feed displays captured subject lines and rendered email screenshots when available from the panel. It focuses on observed broadcast campaigns to help you review messaging, cadence, and seasonal promotions across your industry.

Treat them as complementary signals. Competitor read rates come from observed mailbox activity in the measurement panel, whereas your own open rates come from tracking pixels in the emails you send. The dashboard labels panel estimates alongside your own delivery metrics so you can compare directional trends accurately.

Yes. Each brand profile lists the detected email service provider when the panel can identify it from message headers and sending infrastructure. If a sender's provider cannot be verified from observed mail, the field stays blank.

Open Competitive Insights in the Bird dashboard, search for competitors by brand name or sending domain, and add them to your watchlist up to your plan's brand allowance. You can also book a demo with our team to check panel coverage for your industry before you subscribe.

Both are self-managed mail transfer agents for organizations that run their own sending infrastructure. Momentum MTA is designed for carrier-grade, high-volume environments that need deep policy customization and routing control. PowerMTA gives enterprise senders high-throughput delivery and granular queue management on their own hardware or public cloud instances in AWS, Azure, or GCP.

Momentum MTA and PowerMTA fit enterprises and mailbox providers whose compliance or infrastructure policies require running dedicated mail servers on-premises or in their own cloud. Inbox Insights and Competitive Insights are cloud tools in the Bird dashboard for any sender who wants inbox placement testing and competitor benchmarking, and you can use both without self-hosting an MTA.

SparkPost fa parte di Bird. Bird Email fornisce i flussi di invio, campagna e consegna per i nuovi progetti. Un'integrazione SparkPost esistente è un'integrazione separata: esamina le sue chiamate API, i record di dominio e gli eventi con il tuo account team prima di pianificare una migrazione.

Bird Email ha i propri API e SDK. Consulta le guide su invio, template, dominio e webhook anziché presumere che una richiesta SparkPost possa essere inviata senza modifiche.

Momentum è la nostra piattaforma di infrastruttura email on-premises per invii ad alto volume, con workflow personalizzabili, routing e parametri di consegna impostabili tramite il suo Policy Manager. È progettata per scalare con il tuo volume di invio mantenendo prestazioni stabili e supporta Unicode completo (SMTPUTF8) per inviare a set di caratteri internazionali.

Adaptive Delivery è il traffic shaping automatico di Momentum. Osserva come ogni provider di posta risponde alla tua mail e si regola in tempo reale: rallentando, differendo o mettendo brevemente in pausa un flusso per proteggere la tua reputazione, per poi riprendere una volta risolto il problema. Raggiungi la inbox senza dover gestire manualmente i tassi di invio per ogni provider. L'Intelligence Router ti mostra tutto questo attraverso tutte le tue fonti dati, con avvisi in tempo reale ogni volta che viene effettuata una regolazione.

Sì a entrambe. Momentum funziona sui tuoi server, su qualsiasi cloud principale o in configurazione ibrida, così puoi adattarlo alla tua infrastruttura, ai costi e alle esigenze di conformità, e modificare quel mix nel tempo. Inoltre continua a evolversi: le release recenti lo mantengono aggiornato con i sistemi operativi moderni, TLS 1.3 e gli standard di sicurezza e SMTP più recenti, ed espongono gli eventi dei messaggi tramite API in tempo reale che puoi integrare nei tuoi sistemi di reportistica e automazione.

Sì. PowerMTA può inoltrare parte del traffico alla Bird Email API hosted continuando a consegnare il resto direttamente dai tuoi server — il modo più semplice per provare la piattaforma hosted o migrare gradualmente senza spostare tutto in una volta. PowerMTA stesso gira su infrastruttura di tua proprietà, quindi quegli IP restano sotto la tua gestione. Il traffico che inoltri alla piattaforma hosted può utilizzare i nostri IP oppure i tuoi IP dedicati, mentre tutto il resto rimane interamente sotto il tuo controllo.

I Virtual MTA permettono di eseguire diversi flussi di invio indipendenti all'interno di una singola istanza PowerMTA, ciascuno con i propri IP, reputazione e limiti. Usali per gestire separatamente posta transazionale, posta marketing o clienti diversi. Domini condivisi e policy dei provider destinatari possono comunque influire sulla consegna tra i flussi.

Yes. API requests require HTTPS, and SMTP submission requires TLS encryption on port 465 or a completed STARTTLS upgrade on ports 587 and 2525 before authentication is accepted, keeping your credentials encrypted in transit. Unencrypted submission on port 25 is disabled. To keep data in your chosen region, send through the regional endpoint that matches your API key; Bird's official SDKs and CLI detect the key's region prefix and route requests automatically.

You choose the exact read or write permissions for each API key across email sending, marketing campaigns, and domain management, so a key created for an application server to send receipts cannot modify your domains or access unrelated resources. Administrative actions such as managing team members, workspace settings, API keys, and IP pools require an authenticated user session. You can also attach an IP address allowlist to any key so requests from unfamiliar networks are rejected.

When you rotate an API key, Bird issues a replacement key immediately and keeps the previous key active for a configurable grace period (24 hours by default) so you can roll out the new credential across your services without dropping traffic. If a key is compromised, you can set the grace period to zero to revoke it right away, and you can assign a custom expiration date to the new key if your security policy requires periodic rotation.

Yes. Bird supports enterprise single sign-on over SAML 2.0 and OIDC with identity providers such as Okta, Microsoft Entra ID, and Google Workspace. Your account team can enable SSO for your organization, and team members who sign in with an email and password can enable multi-factor authentication on their own accounts.

Yes. The organization audit log records configuration and administrative changes in a read-only timeline showing the actor, workspace, timestamp, and outcome, and you can export entries in OCSF format to your SIEM. The audit log tracks account and infrastructure actions, while individual sent and received emails are recorded in the email log.

You can download compliance certifications and security documentation from the Bird Trust Center at trust.bird.com, and review our data processing agreement, privacy statement, and acceptable use policy at bird.com/legal. If your procurement or security team requires a custom vendor questionnaire, contact your account team.