Brevo says 'delivered' but the customer swears they never got it
Brevo's shared SMTP IPs get listed on Spamcop and Spamhaus in recurring waves, so receiving servers that use those blocklists soft-bounce or silently drop the mail. Because the rejection is asynchronous, the dashboard often still shows 'delivered' while the recipient's own server quietly refused it.
The fix
Do not trust the 'delivered' label alone. Open the transactional email History tab, filter for soft bounce or hard bounce, and click Show details to read the actual SMTP response, which comes from the recipient's server and names the blocklist and IP (for example "550-Rejected because 77.32.148.24 is in a black list at bl.spamcop.net"). A shared-IP listing is Brevo's incident to clear: Brevo automatically stops using an IP once a Spamhaus block is detected and works to delist it, so open a support ticket with the exact bounce text rather than changing your DNS or SPF. If a critical stream like order confirmations or password resets cannot tolerate riding other senders' blocklist hits, move it to a dedicated IP.
Brevo suspended our whole account after one bad send, and we can't get it back
Brevo auto-suspends the campaign and account when a random-subset assessment (usually within 1 to 3 hours of a send) crosses hard lines: hard bounce over 2%, unsubscribe over 1%, or spam complaints over 0.2%. The first suspension often arrives with no warning, and Brevo's policy is that a second suspension can mean permanent, irreversible deactivation.
The fix
Treat the first suspension as your only warning. It is reversible: go to the Deliverability center, follow the reactivation prompt, and clean your contact database exactly as instructed before resuming, because a second suspension can permanently deactivate the account with no reinstatement. Cleaning means removing hard bounces, role and generic addresses, and anyone you cannot prove opted in (blocklist them in Brevo). Structurally, keep hard bounce under 2% by validating every import externally, and keep unsubscribes under 1% and complaints under 0.2% by mailing only consented, recently engaged segments, since complaint rate is driven by consent and relevance, not list validation.
We imported a fresh list, hit send, and Brevo froze the campaign mid-send
Brevo watches sends to newly imported contacts especially closely: it evaluates the campaign on a random early sample, and if that sample crosses its limits (hard bounce over 2%, complaints over 0.2%, unsubscribes over 1%, or any spam-trap hit) it suspends the rest of the campaign and often the whole account. Senders who blast a purchased or long-dormant list immediately are the ones who get caught.
The fix
Never send a full blast to a freshly imported list. Verify the list through an external validation service first (Brevo integrates Emailable for this) to strip dead and trap addresses, then ramp: mail your most recently engaged contacts before touching cold or newly imported ones so the early sample stays clean. If the import is old or you cannot prove consent, run a re-permission campaign to a small slice first instead of mailing the whole file at once. If a campaign is frozen, you clean up and reactivate it from the Deliverability Center.
Our Brevo emails aren't in spam, they're buried in Gmail's Promotions tab
Independent testing of Brevo sends shows a large share landing in Gmail's Promotions tab rather than the primary inbox, which does not register as a spam failure but still tanks opens. It is driven by promotional-looking content, many tracked links and images, and the weaker authentication and shared-IP reputation typical of Brevo accounts.
The fix
Promotions placement is a content and categorization signal, not an authentication failure, so do not chase it with DNS changes; DKIM, SPF, and DMARC can all pass and mail still lands in Promotions. Reduce tracked links and heavy image blocks, lean toward a plain, one-to-one tone with a personal-looking sender name for mail that must reach Primary, and keep sending to engaged recipients so Gmail learns the mail is wanted. Separate genuinely transactional streams like receipts and password resets onto their own authenticated subdomain. Keep expectations realistic: Promotions is still the inbox, so weigh this against clearer wins like authentication and list hygiene first.
Brevo inbox placement gets soft on big sends while small sends land fine
Senders happy with Brevo's features report that inbox placement weakens specifically as send size grows, even with healthy overall metrics. The pattern of small sends landing while large ones crater points to the disengaged tail of the list dragging the whole send, compounded by Brevo's shared IP pool where you can inherit reputation from other senders on the same IPs.
The fix
Do not switch tools first, because stale lists and weak engagement follow you to any ESP. Segment to recently engaged contacts and stop mailing the never-openers, since large sends drop when they reach the dead tail of the list. Confirm SPF, DKIM, and DMARC actually align rather than just pass, and watch domain reputation in Google Postmaster Tools directly instead of trusting the sending dashboard. Shared IP pools are the one genuinely Brevo-specific factor, so once your volume justifies it, move to a dedicated IP so no neighbor can tank your placement.
