| Sendinblue | |
|---|---|
| Their stated threshold | The same guidance applies as for Brevo: hard bounce rates under 2%, with account review for repeat offenders. |
| What happens if you cross it | Identical to Brevo, since it is the same company and the same compliance team. New accounts are reviewed before volume is released. |
| Where the bounce data lives | The same interface as Brevo: campaign statistics for the per-campaign split, and Contacts then Blocklisted for the account-wide set. |
| How bounces are classified | A hard bounce blocklists the address account-wide, exactly as it does under the Brevo name, because it is the same platform. |
Bringing the rate down
Each step is an action inside Sendinblue, in the order worth taking them.
Check whether your integration uses the old API name
Older integrations and plugins still reference Sendinblue. They work, and the mismatch causes real confusion when someone searches the documentation for the wrong name.
Read the blocklist for the reasons
Contacts, Blocklisted shows whether each address was blocked for a bounce, a complaint or an unsubscribe. Those need different responses.
Trace blocked addresses to the list that brought them in
Grouping by original list usually identifies the import responsible in a minute.
Turn on double opt-in in the form settings
The setting is where it always was, under the form configuration, and it removes the fake-address problem at source.
Use the current documentation
Search under Brevo rather than Sendinblue. The older pages are still around and they are frequently out of date on exactly the compliance details that matter.
The mistake people make here
A bounce report mixes two causes that need opposite responses: addresses that do not exist, and receivers refusing mail they could have delivered. The first is fixed by checking the list. The second is a sending problem and no amount of cleaning will move it.
Questions people ask
Is Sendinblue the same as Brevo?
Yes. Sendinblue rebranded to Brevo and it is the same platform, the same API and the same compliance team. Existing accounts and integrations carried over unchanged.
Do bounce rules differ between the two names?
No. Account-wide blocklisting on hard bounce applies identically, because there is only one product.
Will an old Sendinblue integration still work?
Yes. The API endpoints continued to function through the rename, which is why so many plugins still carry the old name.