Brevo Deliverability: What to Check and Fix

Do not index

Launch week exposes weak Brevo deliverability faster than any dashboard review. A campaign shows a healthy delivery rate, Gmail subscribers report it in spam, and the same afternoon a customer cannot find a password reset. Those events may share one cause, or they may involve separate sending streams that need different fixes.

Table of Contents

How to Diagnose a Brevo Spam Report What to Check First First Read on a Brevo Spam Report Authenticate the Domain and Separate Streams Verify Each Sending Domain Check Before Mailbox Providers Do Lists, Engagement, and the Weekly Review Build Segments Around Recent Behavior Review Weekly by Campaign and Stream Shared IP Versus a Dedicated IP Compare the Operational Trade-Off Warm the IP and Protect the Cadence Common Mistakes That Damage Brevo Sending When to Involve Brevo Support or an Expert Frequently Asked Questions

How to Diagnose a Brevo Spam Report

Brevo deliverability is whether each sending stream reaches the inbox at each mailbox provider, not whether Brevo accepted the campaign for sending. Brevo counts a message as delivered when the recipient server accepts it, and accepted mail can still land in spam.

That distinction drives the whole diagnosis. Brevo's guide to email deliverability defines delivery as successful receipt by the recipient's mail server, while delivered messages may still be in the inbox or spam folder. A strong aggregate delivery rate therefore cannot rule out a Gmail, Outlook, or Yahoo placement problem.

What to Check First

1. Name the affected stream. Separate campaigns, automations, and transactional email such as receipts and password resets. A campaign-only failure usually points toward audience, consent, content, or frequency, while simultaneous failure across streams raises authentication, account, or IP concerns.

2. Read the message headers. Open a recent delivered message, inspect Authentication-Results for SPF, DKIM, and DMARC, and compare the visible From domain with the Return-Path. A failure, missing result, or misalignment should stop the next send until that exact sending domain is corrected.

3. Identify exactly who received the mail. Look for a recent import, a segment untouched for months, role-based addresses, or contacts without a recorded opt-in. Don't assume a familiar list is safe if its acquisition source, consent date, or last engagement date cannot be explained.

4. Split results by mailbox provider. Compare Gmail, Microsoft, Yahoo, and important business domains separately. A Gmail-only drop and an all-provider drop don't share a fix, and an account average can hide a severe problem concentrated at one provider.

5. Export failed-delivery reasons. Treat 4xx responses as temporary deferrals and 5xx responses as rejections, then group them by provider and recipient domain in Brevo's log views. Brevo's automation statistics guidance supports separating temporary deferrals from permanent rejections before deciding whether to reduce or pause the affected stream. For Gmail, the same diagnostic approach includes checking whether domain reputation has moved among High, Medium, Low, or Bad.

6. Match the incident to a change. Compare starting date, sending volume, complaints, imports, From address, and stream settings. Pause only the affected stream while the cause is corrected, because resending to the full list after a complaint spike creates more reports, more filtering, and more support work.

First Read on a Brevo Spam Report

Check	What you see	Likely cause	First action
Stream	Campaigns fail, transactional is fine	Audience, consent, or frequency	Pause campaigns, keep transactional sending
Stream	Campaigns and transactional fail together	Authentication, shared IP, or account review	Freeze volume changes, verify domain authentication, contact Brevo support
Authentication	SPF, DKIM, or DMARC fails or is not aligned	Unauthorized or misaligned From domain	Authenticate that domain before the next send
Audience	Drop starts after an import or on an old segment	Stale, purchased, or unconsented contacts	Suppress and clean that segment before sending
Mailbox provider	Only Gmail, Yahoo, or Microsoft drops	Provider filtering or complaints	Read that provider's bounces and complaints

Volume also belongs in the timeline. A sharp increase can produce temporary rate limiting, especially when it reaches older or less engaged contacts. Reintroduce traffic gradually after list quality and engagement have been verified, rather than restoring the full send because one small test looked normal.

A controlled placement check, complaint trend, rejection export, and engagement split by cohort provide better evidence than a dashboard average. Teams rebuilding trust after an incident also need patience with a structured email warmup process, because mailbox providers judge the pattern over repeated sends, not a single declaration that the problem is fixed.

Authenticate the Domain and Separate Streams

A Brevo account can show a healthy delivered rate while one stream lands in spam at a single provider. Authentication is the first thing to verify, because it tells Gmail, Yahoo, and Microsoft that Brevo may send for the domain recipients see. When SPF, DKIM, or DMARC fails, those providers get a clear reason to reject or filter the message, and the dashboard may still count the send as delivered.

Brevo's dedicated IP setup guidance confirms that authentication authorizes sending addresses to send on behalf of the organization, and that when SPF fails, Gmail, Yahoo, and Microsoft may reject or filter the email.

Verify Each Sending Domain

Authenticate every domain or subdomain that appears in a live From address, then confirm DMARC alignment with the visible From domain. A domain verified for campaigns leaves automations and transactional mail unproven if they send under a different identity, so check each sender one at a time.

Check the exact stream: Review campaign, automation, and transactional senders separately rather than relying on one account-level status.

Check the IP association: On a dedicated IP, the sender must configure SPF, and associating that IP with a subdomain can authenticate the associated subdomain automatically.

Check live mail: Confirm authentication results in received headers after setup. The settings screen shows configuration; the headers show what providers saw.

Use example.com purely as an example. Campaigns send from news.example.com while receipts and password resets send from transact.example.com, each subdomain authenticated in Brevo. If a promotion earns complaints at Gmail, the damage stays on the campaign subdomain and the receipts keep landing. That separation also supports the controls described in the guide to improve transactional email deliverability.

The same discipline appears in compliance-first email marketing for lawyers, where sender identity, consent records, and message purpose stay clearly separated. Governance like that lets any team answer which system sent a message and why.

Check Before Mailbox Providers Do

Gmail and Yahoo bulk-sender rules, in force since February 2024, require SPF and DKIM, DMARC, and one-click unsubscribe for qualifying senders. Put the unsubscribe header on the verification list now; whether recipients need it is a list and complaint question, but the mechanism must exist before volume triggers a rejection.

Authentication gaps remain a routine finding across custom sending domains. SPF records go missing, sit malformed, or break after a later DNS change, and nobody notices until a provider starts filtering. A pass in the settings panel means little if the record on the sending subdomain no longer resolves.

A careful email authentication review identifies whether the live sending domains pass and align. To inspect the DMARC record itself, our sister tool mailX runs a free DMARC check; for current domain-authentication screens and menu paths, follow the Brevo help center.

Misalignment ignored has a commercial cost. Receipts disappear, account access stalls, campaign revenue falls, and support teams manually resend messages that should have arrived automatically.

Lists, Engagement, and the Weekly Review

Deliverability work starts before creative review. Import only addresses with a known source and defensible consent, and prefer double opt-in for new marketing contacts when the acquisition channel makes intent uncertain. A recognized signup creates expectations that a purchased, scraped, rented, or inherited file cannot match.

No automatic safeguard makes a stale or poorly permissioned import safe. Remove invalid addresses before import, suppress repeated soft bounces, review role-based addresses, and skip any segment whose source nobody can explain. A documented email list clean-up should happen before a suspicious file reaches Brevo, because reacting after mailbox providers respond is already damage control.

Build Segments Around Recent Behavior

For recovery, the typical pattern is controlled rather than dramatic. Authenticate the domain, separate transactional mail from campaigns, restrict campaigns to recent openers and clickers for a few weeks, clean the list, and then raise volume gradually. Placement usually builds over several weeks rather than after a single successful send.

Engaged segment: Start with recipients who opened or clicked within the previous 30 days for a warm-up or restart.

Expansion segment: Add older engaged cohorts in stages while bounces and complaints remain stable.

Sunset segment: Suppress contacts who still haven't engaged after a defined sequence of campaigns and a final confirmation attempt.

Source segment: Keep new imports, partner leads, event contacts, and older CRM records separate until each source proves itself.

Thoughtful email list building makes those segments possible because source, consent, and signup date are captured from the beginning. Teams refining subject lines or campaign variants can also learn from AI-driven testing for email campaigns from Stamina, provided testing stays inside an engaged audience and doesn't become an excuse to mail dormant contacts.

Review Weekly by Campaign and Stream

Brevo's delivered rate can stay green while one mailbox provider files your campaigns into spam, so the unit of review is stream plus provider, never the account-level dashboard. Read hard bounces, soft bounces, complaints, unsubscribes, opens and clicks by provider, plus transactional delivery and deferral logs. Act before the next send when one provider drops, bounces spike after an import, or complaints start trending upward on Gmail.

Metric	Watch level	What it usually means	Action before the next send
Hard bounce	Above 2 percent	Invalid or nonexistent addresses	Pause, suppress, review the import source
Soft bounce	Spike versus the recent baseline	Throttling, full mailbox, or temporary block	Separate 4xx from 5xx and slow that stream
Spam complaint	Above 0.2 percent Brevo risk, or rising on Gmail	Consent, expectation, or frequency	Pause the segment and check the audience
Unsubscribe	Above 1 percent	Targeting or cadence	Narrow the segment and reduce frequency
Provider split	One mailbox provider drops	Filtering at that provider	Do not mail that cohort again until reviewed
Transactional log	Deferrals rise with no list change	Infrastructure or account side	Compare with campaigns, then consider Brevo support

Those watch levels have account consequences. Brevo's suspension guidance states that a hard-bounce rate above 2%, an unsubscribe rate above 1%, or a spam-complaint rate above 0.2% can trigger suspension. Prioritize the metric closest to its limit and pause the risky send while the list or targeting problem is corrected.

Gmail and Yahoo bulk-sender requirements expect senders to keep spam rate under 0.3% and ideally under 0.1%, and Microsoft applies comparable rules to high-volume Outlook.com senders. Making exit difficult doesn't preserve an audience. It converts quiet disengagement into complaints that can stop the whole program.

Shared IP Versus a Dedicated IP

Let sending pattern drive the IP strategy. A dedicated IP earns its keep only when a team sends often enough to keep a stable reputation alive, and private infrastructure below that threshold becomes a liability rather than an asset. For intermittent or seasonal volume, a shared IP is usually the right home, because the pool absorbs the quiet stretches that would starve a dedicated address of the consistent evidence mailbox providers look for.

Brevo sets a minimum sending pattern for dedicated IPs, and falling below it is the failure mode that catches most smaller teams: the IP goes quiet, providers lose the steady behavior they use to build trust, and the next campaign starts from a weaker position than expected.

Compare the Operational Trade-Off

Decision	Shared IP	Dedicated IP
Fits when	Occasional volume, below the dedicated pattern	At least three campaigns weekly to 3,000 or more contacts, or over 100,000 monthly emails
Reputation	Pooled with other senders	Yours alone, including your mistakes
New IP start	No private warm-up you control	About 3,000 emails on day one, to recent engagers
Daily increase	Avoid sudden jumps on any IP	About 15 percent the next day if results stay stable
After 30 days idle	No dedicated warm-up to restart	Warm-up restarts at about 3,000 a day, then 15 percent
Both streams fail	Brevo support first, especially with a restriction	Check authentication first, then Brevo support if the IP is clean

The dedicated IP thresholds and warm-up figures in this table come from Brevo's dedicated IP management guidance.

A shared IP creates neighbor risk. Other senders' bounces, complaints, or abuse can affect the pool, which is why simultaneous campaign and transactional deterioration deserves Brevo support involvement. A dedicated IP removes that neighbor variable but concentrates every consequence of poor lists, erratic cadence, and sudden spikes on one sender.

Warm the IP and Protect the Cadence

Open a new dedicated IP at the starting volume in the table above, aimed at contacts who opened or clicked recently rather than the full file. Raise the next day's send by the same modest step only while bounces and complaints stay calm. The address count matters less than early proof that real recipients want the mail.

An idle stretch restarts the ramp from the beginning. Seasonal brands should build that restart into the campaign calendar, because jumping straight back to last season's peak invites deferrals and spam placement.

Scheduling is part of the mechanics. Suspending and requeuing a campaign can restart warm-up and reset the sending quota, so mid-ramp changes need an owner who understands the consequence. After any disruption, rebuild gradually and read results by mailbox provider and by stream before each increase, because a healthy delivered rate can still hide a single provider filing the mail in spam.

Point operational questions to Brevo's current dedicated IP and warm-up help articles rather than stored screenshots or old internal notes. A dedicated IP is the right call when the team sends often enough, cleanly enough, and predictably enough to maintain the reputation attached to its own address.

Common Mistakes That Damage Brevo Sending

The mistakes that survive authentication, list hygiene, and provider-level diagnosis are operational. They are ownership gaps that let a sound setup drift.

Sending campaigns and transactional mail from the same From domain lets one weak promotion teach filters to distrust receipts and password resets. Stream separation contains that damage and makes the next incident faster to isolate.

Buying a dedicated IP for an occasional newsletter creates a cold asset with none of the control it was bought for. Leave it idle long enough and the team owns another warm-up before it can send normally, which is a poor trade for a sender who mails a few times a year.

Doubling launch volume without starting from recent engagers makes legitimate growth look like a spike. Deferrals follow, and frustrated teams often resend to the same file, which deepens the problem. Growth should move through the most engaged segment first, then widen.

Restarting a suspended campaign without checking warm-up status can reset the ramp the team thought it had preserved. A paused campaign keeps consuming reputation, so scheduling decisions need the same care as audience decisions.

None of these appear as a broken configuration, and that is why they persist. Each one is a decision made without an owner. Assign the controls by name: who approves a volume increase, who confirms warm-up status before a suspended campaign requeues, and who signs off before a new stream shares an existing domain. A control with a name attached holds. A checklist item without one drifts.

When to Involve Brevo Support or an Expert

Open a Brevo ticket when transactional and campaign mail degrade together without a list or volume change, or when Brevo shows a sending restriction or account review. The ticket moves faster with evidence attached: failed-delivery reasons broken down by provider, the affected stream and time window, sample headers with Authentication-Results, and volume and complaint trends from the moment the incident started.

Support can clear platform-side flags and confirm whether a shared IP or an account-level block is involved. It cannot rebuild list quality or domain reputation, because those sit on the sender's side. A different pattern points there instead. If transactional mail stays healthy while campaigns fail, audience quality and frequency are the likely causes, and the team can usually correct them without a ticket.

Outside help becomes sensible when incidents repeat, a migration approaches, a provider block won't clear, or nobody owns the weekly review. MailAdept embeds a dedicated deliverability expert in the team to audit the setup, protect sender reputation, and improve inbox placement, without guaranteeing placement.

Frequently Asked Questions

Does a high Brevo delivery rate mean inbox placement? No. Check the signal the account average hides first: complaints and rejection reasons split by mailbox provider. If Gmail shows rising complaints or deferrals while Outlook holds steady, the problem is placement at that provider, and the delivered count will not show it. Engagement cohorts and controlled placement checks confirm which stream and provider need attention.

How long does placement take to recover? Authentication faults can often be identified and fixed quickly, while reputation recovery usually takes several weeks depending on severity and sending history. The working pattern is authentication, stream separation, engaged-only campaigns, list cleaning, then a gradual volume ramp. One clean send does not reset provider trust or prove the underlying problem is gone.

Should campaigns and transactional mail share one domain? No. Separate authenticated subdomains keep promotional complaints from training filters against receipts, password resets, and other expected product messages. Each stream then carries distinct volume, audience, authentication, and engagement signals, which makes the next incident faster to diagnose.

When is a restriction a Brevo support issue? Treat it as a support issue when both streams fail together, Brevo displays a review or sending restriction, or performance drops without a matching audience or volume change. That pattern is especially important on a shared IP or a newer account.

Strong Brevo sending comes down to authenticated streams, permissioned and engaged audiences, steady volume, and review split by stream and mailbox provider. Teams that want that review run for them can work with deliverability experts for marketing teams; the free deliverability audit is the starting point and produces the first order of fixes.