Email Marketing & Newsletter

Brevo

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Sendinblue SAS · www.brevo.com

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The CRM Manager v1.0 · The Deliverability Engineer v1.0 · The Data Protection Officer v1.0 · The Shop Owner v1.0 · The Integrator v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 30 Sep 2026

Compare with Mailchimp → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Integrator

Weighted verdict

Has to wire this into a stack that already exists. Wants a documented API with rate limits, webhooks that retry, a sandbox and a deprecation policy. Treats a partner-form integration page as a missing API, and reads "Zapier supported" as an outsourced one.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Integrator

Campaigns & automation

How this is scored

Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.

0 — One-off broadcasts from a fixed template; no segmentation and no automation of any kind.

3 — A drag-and-drop editor and simple list segmentation, but automation is a single welcome mail and there is no testing.

5 — Reusable templates, attribute and behaviour segmentation, multi-step automations on common triggers, and subject-line A/B testing.

8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, and testing that reports significance rather than raw counts.

10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.

Report an error

The Integrator

Templates, segmentation that includes web tracking, ready-made and custom automation workflows with welcome, birthday and abandoned-cart triggers, subject-line A/B testing and AI send-time selection are all documented. We found no public information on journey branching on behaviour and data, dynamic content per segment, or tests that report statistical significance, so I stop below the full journey-builder mark. 8 9 17 1

Report an error

Deliverability infrastructure

How this is scored

Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.

0 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.

3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.

5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.

8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.

10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.

Report an error

The Integrator

SPF, DKIM and DMARC with a custom sending domain are documented down to API endpoints for validation and authentication, shared IPs ship on all plans with dedicated IPs from Professional, and a Deliverability Center surfaces a score with six months of history while unengaged subscribers can be auto-excluded. We found no public information on dedicated-IP warm-up, seed or inbox-placement testing, automatic hard-bounce suppression, or blocklist handling done on the customer's behalf, and the 99% inbox figure appears only as marketing copy. 17 10 11 9

Report an error

Consent, proof & tracking limits

How this is scored

How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.

0 — Single opt-in with no consent record; tracking is always on and cannot be disabled.

3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.

5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.

8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, tracking off-by-default available, and retention rules for inactive subscribers.

10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.

Report an error

The Integrator

Double opt-in is the documented default, consent groups with a self-serve preference centre give topic-level granularity, and erasure handling is written down to removal across accounts when a contact writes to Brevo directly. We found no public information on what a stored consent record contains, on unsubscribe mechanics, or on switching open and click tracking off — tracking is listed as an included feature. 9 13 12 4

Report an error

List ownership, import & exit

How this is scored

Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.

0 — Export is addresses only; engagement history, segments and automations cannot leave.

3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.

5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.

8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.

10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.

Report an error

The Integrator

Import and export are documented endpoints — CSV or JSON in with a completion callback, export with selectable attributes, metadata and email and SMS subscription status — and the GDPR pages commit to exporting data for transfer to a competitor. We found no public information on exporting engagement history, campaigns or templates, the export endpoint lists a too-many-requests error, and exit is tight: termination deletes content immediately and irrevocably unless requested within 24 hours, with the last monthly subscription amount named as a possible recovery fee. 14 15 12 3

Report an error

Integrations & API

How this is scored

The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.

0 — No API and no named integrations; the list is maintained by CSV upload.

3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.

5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks for the core subscriber events.

8 — Maintained bidirectional integrations with named systems including at least one major shop platform, event webhooks with retries, documented rate limits, and a sandbox.

10 — The tool is a component rather than a destination: transactional and marketing sending on one API, events flowing both directions, versioned API with a deprecation policy, and integrations the vendor maintains rather than lists.

Report an error

The Integrator

This is one I can build against: a documented REST API with key authentication, official SDKs in seven languages, published rate limits per plan (1,000 requests per second on all plans, 2,000 on Professional and Enterprise, 6,000 Enterprise-only), real-time webhooks for delivered, opened, clicked, bounced and spam plus inbound parsing, idempotency keys, an API playground for live endpoint testing, transactional and marketing sending on one API, and a Shopify integration syncing purchase and abandoned-cart data. We found no public information on webhook retry behaviour or a deprecation policy, and the marketplace's Developed-by filter alongside a technology-partner contact form suggests not every listing is vendor-maintained — that caps it at the connection-surface mark for me. 17 16 9 2 14

Report an error

European sovereignty

How this is scored

Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.

0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.

3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.

Report an error

The Integrator

Hosting is EU with named providers — OVH in France and Germany, Google Cloud in Belgium — under an EU entity, with downloadable ISO 27001:2022 certification, a TÜV Rheinland audit of the technical measures, an Article 28 GDPR data processing agreement inside the terms, and transfers to the USA and India named with adequacy decisions or standard clauses as the basis. The captured pages name different entities for contracting and control — Sendinblue SAS in Paris in the terms, Brevo GmbH in Berlin as controller — the full subprocessor list is referenced to the data processing agreement rather than shown, and AI input and output including customer contents are transmitted to third-party AI providers, so I hold this just under the fully evidenced mark. 1 4 3 7 6

Report an error

Pricing transparency

How this is scored

Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A headline price per contact tier exists, but send limits, overage rates or the tier where automation begins are not stated.

5 — Contact-tier prices public with the billing period stated and send limits given, but at least one commonly needed capability sits in an unpriced tier or add-on.

8 — Every tier priced publicly with contact and volume limits, overage rates, feature boundaries and VAT treatment stated; only genuinely custom volume lacks a number.

10 — Complete price computability: a calculator producing the annual invoice for a given list size and send frequency, including overage, additional domains and dedicated IPs.

Report an error

The Integrator

Volume tiers are public with the billing period and VAT treatment stated — Starter from 5,000 emails per month at €7, Standard at €15, Professional from 150,000 at €499, Enterprise custom — alongside priced add-ons such as removing the logo at 8,10 € per month. We found no public information on overage rates, dedicated-IP or SMS pricing, and the credit model's price depends on the number of emails without a visible rate table; the captured pages also give different figures for the free plan's contact and send limits, so the real invoice is not fully computable from public pages. 17 2 3 9

Report an error

European sovereignty — proven facts

2 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Incorporated in DE ⚠ unverified	3/3 pts	6 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	EU only ⚠ unverified	3/3 pts	1 Report an error
Subprocessors	Not determined ⚠ unverified	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Legal entity. The terms of use name the French parent Sendinblue SAS (Paris, France) as the contracting party for the service, of which Brevo GmbH is a subsidiary.
Weak sourcing — Data residency. The statement sits in homepage marketing copy rather than the excerpted contractual terms, and one of the named hosts, Google Cloud, is a US-headquartered company (Belgian region).
Weak sourcing — Subprocessors. Not confirmed on the vendor’s own pages as captured.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

53 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
10 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
5 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
4 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us

Do you know more about Brevo? Tell us Report an error on this page

Sources (17)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor homepage www.brevo.com Checked 15 Sep 2026 Details →
2 Pricing www.brevo.com Checked 15 Sep 2026 Details →
3 Terms www.brevo.com Checked 15 Sep 2026 Details →
4 Privacy policy www.brevo.com Checked 15 Sep 2026 Details →
5 Privacy policy www.brevo.com Checked 30 Sep 2026 Details →
6 Imprint www.brevo.com Checked 30 Sep 2026 Details →
7 Security / trust page — found from the homepage www.brevo.com Checked 30 Sep 2026 Details →
8 Campaigns & automation — found from sitemap www.brevo.com Checked 30 Sep 2026 Details →
9 Campaigns & automation — found from sitemap www.brevo.com Checked 30 Sep 2026 Details →
10 Deliverability infrastructure — found from sitemap developers.brevo.com Checked 30 Sep 2026 Details →
11 Deliverability infrastructure — found from sitemap www.brevo.com Checked 30 Sep 2026 Details →
12 Consent, proof & tracking limits — found from sitemap www.brevo.com Checked 30 Sep 2026 Details →
13 Consent, proof & tracking limits — found from sitemap www.brevo.com Checked 30 Sep 2026 Details →
14 List ownership, import & exit — found from sitemap developers.brevo.com Checked 30 Sep 2026 Details →
15 List ownership, import & exit — found from sitemap developers.brevo.com Checked 30 Sep 2026 Details →
16 Integrations & API — found from sitemap www.brevo.com Checked 30 Sep 2026 Details →
17 Integrations & API — found from sitemap www.brevo.com Checked 30 Sep 2026 Details →