Brevo email deliverability: 7 checks before you send

Short answer. Before a major Brevo send, authenticate the domain, verify consent and suppression, segment from recent customer-generated engagement, inspect bounce and complaint trends, keep volume predictable, choose shared or dedicated IP intentionally, and test unsubscribe plus rendering. Brevo can deliver the message to the receiving server, but no platform can guarantee inbox placement.

Deliverability is a system. DNS, list acquisition, customer expectation, sending volume, content, and recipient behavior all influence whether future messages are accepted and placed.

Brevo's current deliverability best practices emphasize legitimate contacts, consistent volume, gradual ramp-up, and visible unsubscribe.

Check 1: authenticate the sending domain

Use a domain the brand controls. In Brevo, complete the current domain-authentication flow and publish the requested DKIM and DMARC records. Review SPF alignment as part of the broader sending setup.

Validate with DNS lookup, not only a green badge in the application:

• DKIM selector resolves and signature passes.
• DMARC record exists at _dmarc.yourdomain.
• Visible From domain aligns under the intended DMARC mode.
• Return-Path and sending infrastructure are understood.
• Test message headers show SPF, DKIM, and DMARC results.

Start DMARC at a monitored policy appropriate to the domain's maturity, review aggregate reports, then move toward enforcement. Do not publish a strict policy before identifying every legitimate sender.

See the full SPF, DKIM, and DMARC guide.

Check 2: prove consent and preserve suppressions

A clean Brevo list is not a CSV with valid syntax. It is a group of people who asked for the relevant messages and still expect them.

Before importing, preserve separately:

• Active consented contacts.
• Unsubscribed contacts.
• Hard bounces.
• Spam complaints.
• Administrative or legal suppressions.
• Unknown or unproven records.

Do not subscribe an entire CRM or customer export. A purchase, business card, abandoned checkout, or historical account does not automatically create marketing permission.

For each acquisition source, store the opt-in date, source, form or wording, channel, and region where available. Quarantine sources with missing evidence.

Check 3: send to a defensible engaged audience

Build engagement from signals the customer generated:

• Recent click.
• Recent purchase.
• Recent form or preference update.
• Recent relevant site event where consent allows tracking.
• Support or account interaction that supports the message context.

Do not rely on opens alone. Brevo documents proxy_open for Apple Mail Privacy Protection, which can represent an automatic open. In France, Brevo's 2026 automation documentation also notes explicit separate tracking-consent requirements before individual open data is used for certain triggers. Confirm market-specific legal requirements with counsel.

For a large or newly reactivated database, send in tiers:

1. Recent customers and verified clickers.
2. Older but still relevant customers and clickers.
3. Carefully selected dormant profiles only through a defined re-permission or sunset plan.

Stop expansion if complaints, hard bounces, or provider errors worsen.

Check 4: review bounces, complaints, and domains

Brevo can classify delivered, soft bounce, hard bounce, unsubscribe, and other system events. Use event logs and campaign reporting to find the pattern, not only the account average.

Google asks bulk senders to keep user-reported spam below 0.1% and avoid reaching 0.3% or higher. Treat these as ceilings. Aim to remain materially below them through permission and relevance.

Suppress permanent failures and complaints. Do not repeatedly retry a hard bounce.

Check 5: keep volume predictable

Mailbox providers learn from sending patterns. Sudden volume after a long pause or a new domain can cause temporary deferrals or worse placement.

Plan campaigns on a volume calendar that includes:

• Campaign sends.
• Automation volume.
• Transactional sends.
• Seasonal peaks.
• New market or list imports.
• Domain or IP changes.

If reputation is new or inactive, begin with the most engaged profiles and expand gradually. Do not resend immediately to contacts affected by a provider deferral without understanding the error.

Brevo's Gmail troubleshooting documentation notes that rate limiting can appear as temporary 421 4.7.0 responses, but the full message must be read because the code can cover several causes.

Check 6: choose shared or dedicated IP intentionally

Shared IP

A shared pool can suit lower or irregular volume because the infrastructure has ongoing traffic. The sender still owns domain reputation, content, permission, and behavior.

Dedicated IP

A dedicated IP gives one organization direct responsibility for IP reputation. It is useful only when volume is sufficient and consistent enough to maintain it.

Brevo currently offers dedicated IPs under plan-specific and add-on conditions. Its dedicated IP setup guide requires authentication and warm-up.

Brevo's manual warm-up documentation currently recommends starting around 3,000 messages per day and increasing approximately 15% per day for that specific workflow, beginning with engaged contacts. Treat that as Brevo product guidance for eligible plans, not a universal schedule. Adjust to actual volume and follow the current in-account process.

A dedicated IP is not a repair for weak consent. It concentrates the consequences of poor sending.

Check 7: test unsubscribe, rendering, and final headers

Send the final message through Brevo to seed accounts at the main providers. Verify:

• From name and reply address.
• SPF, DKIM, and DMARC results.
• Subject and preview text.
• Mobile and desktop layout.
• Dark-mode readability.
• Image blocking and alt text.
• Link destination and tracking.
• Unsubscribe link and one-click behavior where applicable.
• Preference center.
• Physical address and required footer information.
• Language and market-specific conditions.

Brevo says it automatically adds an unsubscribe link when a campaign lacks one. Do not rely on a last-minute fallback. Design a visible unsubscribe path and test it on a real profile.

A pre-send gate

No high-volume campaign should launch without an owner watching the first provider-level results.

What to monitor after sending

Review the first results without overreacting to tiny samples. Track:

• Attempted, delivered, soft bounce, and hard bounce counts.
• Complaint and unsubscribe rate.
• Results by mailbox provider.
• Click and conversion behavior.
• Deferral and block messages.
• Volume compared with recent history.

Annotate DNS, IP, list-source, and frequency changes. A timeline helps distinguish a reputation issue from a one-off content or storefront problem.

If performance deteriorates

1. Pause expansion to older audiences.
2. Isolate affected mailbox providers and campaigns.
3. Read complete bounce and deferral messages.
4. Verify DNS and header alignment.
5. Identify acquisition sources behind bounces or complaints.
6. Reduce to recent consented customers and verified clickers.
7. Remove or suppress invalid and persistently inactive contacts.
8. Resume gradually only after the cause is addressed.

Do not rotate domains or IPs to escape reputation. That avoids diagnosis and can make future trust harder to establish.

Common Brevo deliverability mistakes

• Trusting a delivered status as proof of inbox placement.
• Importing all customers as subscribers.
• Using Apple privacy opens as human engagement.
• Sending a dormant list in one batch.
• Buying a dedicated IP without consistent volume.
• Skipping warm-up after a new or long-idle IP.
• Hiding unsubscribe to reduce list loss.
• Resending temporary failures before reading the response.

FAQ

Does Brevo guarantee email deliverability?

No provider can guarantee inbox placement. Brevo supplies sending infrastructure and controls, while sender authentication, permission, reputation, content, and recipient behavior remain decisive.

Do I need a dedicated IP?

Not necessarily. A dedicated IP requires consistent volume and disciplined ownership. Lower or irregular senders may be better served by a shared pool while building strong domain reputation.

How should I warm a Brevo dedicated IP?

Follow Brevo's current plan-specific workflow and begin with the most engaged consented contacts. Its manual guide currently suggests around 3,000 daily messages and 15% daily growth for eligible setups, but actual plans should match real volume.

Is Gmail Promotions a deliverability failure?

No. Promotions is an inbox category, not spam. Focus on wanted mail, authentication, reputation, and customer response rather than attempts to trick category placement.

Are open rates reliable in Brevo?

They are affected by Apple Mail Privacy Protection. Brevo exposes proxy-open behavior, so use verified clicks, purchases, and other customer actions for engagement decisions.

Protect reputation before chasing volume

Deliverability improves when permission, audience, authentication, cadence, and message all agree. Deliver helps teams audit Brevo setup and turn findings into an operating plan. Book a Brevo deliverability diagnostic.