Marketing Automation
Brevo (Automation)
EU-Made Report an errorPanel 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
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 panel's verdict
Judged from a the evidence whose automation product page yielded no confirmed facts, Brevo's automation offering (vendor Sendinblue SAS, Paris) sits at the floor on its core criteria: journeys & orchestration at 0–1, lead scoring, routing & lifecycle and CRM integration & data model at 0 across the score table. Channels & personalisation is the relative strength at 2–3: email is priced in public send tiers (Starter from 5,000 emails/month, Professional from 150,000 with 10 users), and WhatsApp messaging and Facebook advertising are named as optional platform features — though nothing shows they share one contact profile or suppression list. Consent, tracking & profiling evidences only the vendor's own GDPR hygiene, and sovereignty credits a named German controller and declared DPF/SCC transfers to the USA and India against unstated hosting and a subprocessor list kept only in the DPA. Pricing stays label-only, with Enterprise 'Auf Anfrage'. flagged splits found none above threshold.
Speaks for it
- Email sending is priced in public tiers — Starter from 5,000 emails/month, Professional from 150,000 emails/month with 10 users included.
- WhatsApp messaging and Facebook advertising are named as optional platform features beyond email.
- A German controller entity, Brevo GmbH of Berlin, is named, with transfers to the USA and India carrying a stated DPF/SCC basis.
- The privacy policy documents GDPR role allocation, a DPO mailbox and Art. 20 portability.
Held against it
- Journeys & orchestration scored 0–1 with no evidenced trigger, branch, wait or journey-state fact anywhere in the evidence.
- Lead scoring, routing & lifecycle scored 0 across the table — no scoring model, decay, lifecycle stage or routing is documented.
- CRM integration & data model scored 0, with no CRM sync, field mapping, deduplication or identity resolution evidenced.
- No consent tooling for customers' contacts is evidenced — no double opt-in, stored consent record with source, or per-contact tracking switch.
- Hosting location is unstated beyond 'Tier-3 and PCI-DSS certified datacenters,' data residency is unknown, the subprocessor list lives only in the DPA, and the AI chatbot runs on OpenAI.
Best for
- You need tier-priced email volume (Starter from 5,000 emails/month) and can meet orchestration and CRM needs elsewhere.
- You want email plus optional WhatsApp and Facebook channels and accept them being managed separately.
- You want a European vendor with a named German contracting entity and declared transfer bases for USA and India flows.
Avoid if
- You need evidenced journey branching, waits or collision handling — the evidence documents none of them.
- Your implementation depends on CRM sync, field mapping or identity resolution — CRM integration & data model scored 0.
- You must show double opt-in, stored consent records or profiling suppression for named EU contacts.
- You require confirmed EU data residency or a publicly published subprocessor list — the evidence marks residency unknown and lists subprocessors only in the DPA.
The scores
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, and — the part that decides whether it survives contact with reality — what happens when journeys collide.
0 — Autoresponders on a single trigger; no branching, no waits, no conditions.
3 — Linear sequences with simple conditions, one entry trigger per journey, and no visibility into where a contact currently sits.
5 — A visual builder with branching on attributes and behaviour, waits and goals, entry and exit conditions, and per-contact journey state visible.
8 — Event-driven entry from external systems, frequency capping and suppression across journeys, priority when a contact qualifies for several, versioning of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and a journey a colleague can read months later without a diagram.
The Demand Gen Lead
I can't even confirm autoresponders, let alone per-contact journey state or suppression across journeys. 1
The Sales Ops Manager
The automation product page yielded not one confirmed fact about triggers, branching, waits or what happens when journeys collide. No workflow capability is evidenced, so it scores the floor. 1
The Data Protection Officer
The automation product page in the registry produced no confirmed facts — no trigger types, branching, waits, journey state, suppression or frequency capping appear anywhere in the evidence. I sit at the bottom anchor, granting a single point only because this row is sold as a marketing-automation product at all. 1 2
The Lifecycle Marketer
Nothing in the evidence evidences so much as a trigger and a wait: the automation product page produced no confirmed facts at all and the pricing fragments talk only send volumes and users. I can't credit branching, journey state, frequency capping or collision handling that has no paper trail — total silence lands at the bottom anchor. 1 2
The Solution Architect
The product page capture confirmed not one fact about triggers, branching, waits, journey state or collision handling — for a product sold as automation, that silence is the finding. The only automation-adjacent evidence anywhere is send-volume tiers, which describes sending, not orchestration. rubric level 0: nothing evidenced to build on. 1 2
The Skeptic
The product page was captured and yielded nothing — no trigger, branch, wait, entry-condition or journey-state fact made it to the evidence, so as far as this record goes the automation product has no evidenced automation at all. I score to the floor the anchors describe for absence, not to the vendor's category label. 1
Lead scoring, routing & lifecycle
Show reasoningHide reasoning
How this is scored
Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
0 — No scoring or lifecycle model; every contact is treated alike.
3 — A single additive score with fixed rules, no decay, no lifecycle stages and no routing.
5 — Configurable scoring on attributes and behaviour with decay, lifecycle stages, and routing to owners or teams with notification.
8 — Multiple scoring models per product or region, negative scoring, account-level scoring alongside contact-level, SLA on follow-up, and score history visible per contact.
10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.
The Demand Gen Lead
Nothing on scoring, decay, lifecycle stages, routing, or handover to sales anywhere in the evidence — not even a fixed additive score. If my reps can't trust a number or trace why a lead landed on their desk, this criterion is at the floor, and the evidence gives me no floor to stand on. 1
The Sales Ops Manager
Nothing in the evidence evidences scoring, decay, lifecycle stages, routing or handover to sales; the product page is silent on every capability this criterion needs. I score absence as absence. 1
The Data Protection Officer
Nothing in the evidence evidences scoring, decay, lifecycle stages or routing — not even a single additive score. For my purposes the sharper absence is that no automated decision logic is documented anywhere I could begin to assess under Art. 22; the silence is the finding. 1 3
The Lifecycle Marketer
No scoring model, no decay, no lifecycle stage, no routing — not a single fact anywhere in the evidence touches qualification or handover to sales. The anchors are explicit that absence here means absence of the capability, so 0. 1 2
The Solution Architect
No scoring, decay, lifecycle stage or routing capability appears anywhere in the captured evidence, not even on the product page itself. If the scoring model is invisible, neither I nor the customer's DPO can explain to a lead what the system decided about them. 1
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can actually send and personalise: email, SMS, push, on-site content, ads audiences — judged on what shares one profile and one suppression list.
0 — Email only.
3 — Email plus one further channel, managed separately with its own list and no shared suppression.
5 — Email, SMS or push and web forms driven from one contact profile, with dynamic content blocks and shared unsubscribe handling.
8 — The above plus on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.
10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.
The Demand Gen Lead
Email is real — send tiers of 5,000 and 150,000/month are priced — but WhatsApp and Facebook ads appear only as optional integrations named in a privacy policy, with no evidence they hang off one contact profile or share a suppression list. No SMS, push, or on-site personalisation evidenced at all, and nothing behavioural. 2 3
The Sales Ops Manager
Email is real — tiers are priced by send volume — and WhatsApp messaging plus Facebook advertising appear as optional platform apps. But nothing shows they hang off one contact profile, one suppression list or shared unsubscribe, and SMS, push and web content are unevidenced, which is anchor-3 territory. 2 3
The Data Protection Officer
Email is evidenced by the send-volume tiers, and WhatsApp messaging and Facebook advertising are named as optional platform features. What is missing is any evidence these share one contact profile or one suppression list, so this sits at the 'separately managed channels' anchor. 2 3
The Lifecycle Marketer
Email tiers are public and the privacy policy names WhatsApp messaging and Facebook advertising as platform apps, so it's more than email-only — but nothing shows one profile, one consent state or a shared suppression list across those channels, which caps it at the 'separately managed channels' anchor. No SMS, push or on-site personalisation is evidenced at all. 2 3
The Solution Architect
Email is evidenced through priced send tiers, and the policy names WhatsApp messaging and Facebook advertising as optional platform features — email plus further channels with no evidence they share one profile or one suppression list. No SMS, push, on-site personalisation or dynamic content in evidence anywhere. 2 3
The Skeptic
Email is real (send limits quoted per month) and WhatsApp plus Facebook ads appear — but only as optional apps named in a privacy policy, not as product capability. Nothing on SMS, push, on-site content, a shared profile, shared suppression or dynamic content puts this below the email-plus-one-managed-separately anchor. 2 3
Consent, tracking & profiling
Show reasoningHide reasoning
How this is scored
The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
0 — Tracking always on and undocumented, single opt-in, no consent record, no retention rule, no way to exclude a person from profiling.
3 — Double opt-in available with a timestamp, cookie tracking that cannot be disabled per contact, and retention described as the customer's problem.
5 — Double opt-in as documented default with a stored consent record including source, per-channel consent states, tracking switchable per contact, and stated retention for inactive records.
8 — Consent reproducible as evidence with the wording versioned, profiling suppressible per person, retention executed per data category, documented handling of access and erasure requests including derived scores, and a cookieless or first-party tracking mode.
10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
The policy proves GDPR hygiene on Brevo's own behalf — processor/controller roles, a DPO, Art. 20 portability, 5-year account retention, chatbot chats deleted at session end — but says nothing about the product's consent tooling for my contacts. No double opt-in default, no consent record with source, no per-contact tracking switch, no documented handling of erasure including derived scores. 3
The Sales Ops Manager
For a platform whose job is profiling named people, the evidence evidences only legal hygiene: GDPR roles, a DPO, portability, five-year retention on account data and session-end deletion of chatbot conversations. No evidence of consent records, per-channel consent states, per-contact tracking switches or profiling suppression — so below the anchor-3 bar that requires double opt-in with timestamp. 3
The Data Protection Officer
The privacy policy allocates controller/processor roles and grants portability for Brevo's own website visitors, but I find no double opt-in, no stored consent record with source, no per-contact tracking switch, no retention rule for inactive contacts, and no erasure process covering derived scores. A product whose job is profiling named people has evidenced essentially none of what accountability requires; the one point credits the GDPR role clarity and stated 5-year account-data retention. 3 1
The Lifecycle Marketer
There is a real privacy policy — GDPR roles, a DPO mailbox, Art. 20 portability, a 5-year retention rule for account data and chatbot chats dropped at session end — but that's the vendor's own housekeeping, not the marketer's toolkit: no double opt-in, no stored consent record with source, no per-contact tracking switch, no way shown to suppress profiling or contest an automated decision. That sits between the 0 and 3 anchors, closer to the floor. 3
The Solution Architect
The privacy policy documents GDPR roles, Art. 20 portability and a five-year retention for account data, but that is Brevo as controller of its own website — the platform's handling of customers' named contacts is entirely unevidenced. No double opt-in record with source, no per-contact tracking switch, no retention for contact records, nothing on profiling suppression or contestable automated decisions. 3
The Skeptic
Every consent-adjacent fact is the vendor governing its own website — GDPR roles, a DPO address, portability, five-year account retention — while the platform side is silent on double opt-in, stored consent records with source, per-channel states, per-contact tracking switches and retention for the customer's contact base. rubric level 3 at least demands double opt-in with a timestamp; that much isn't evidenced, so this sits below it with only partial retention documentation to lift it off zero. 3
CRM integration & data model
Show reasoningHide reasoning
How this is scored
The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
0 — CSV import and export; no CRM integration and no identity resolution.
3 — One-way sync into a named CRM on a schedule, with duplicates resolved by hand and no conflict rules.
5 — Bidirectional sync with at least one major CRM, field mapping, deduplication rules, and a sync error log somebody can act on.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry, and a documented API with rate limits.
10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.
The Demand Gen Lead
No CRM integration, no sync, no field mapping, no identity resolution — the evidence is silent on the entire join that decides whether an implementation survives. The only data facts I have are PCI payment processing and chatbot deletion, which have nothing to do with keeping two systems in agreement about who a person is. 1
The Sales Ops Manager
The join that decides my implementation is completely undocumented: no CRM named, no sync direction, no field mapping, no dedup rules, no conflict handling and no sync error log anywhere in the captured pages. 1
The Data Protection Officer
The only integrations named anywhere are WhatsApp, Facebook advertising, Google Fonts and reCAPTCHA. No CRM sync, field mapping, deduplication rules, conflict handling or identity resolution is evidenced, so this scores at the bottom anchor. 3
The Lifecycle Marketer
Not one fact about CRM sync, field mapping, deduplication rules, conflict handling or a documented API — the evidence is entirely silent on the join that decides the implementation. Silence is a 0 by the anchors; I won't assume the capability exists. 1 2
The Solution Architect
Not one fact on CRM sync, field mapping, conflict resolution, custom objects, identity resolution, or a documented API with rate limits — the join that decides the whole implementation is undocumented, and there is no stated path from anonymous visitor to known contact. rubric level 0, and having lived these failures, I treat an undocumented data model as no data model. 1
The Skeptic
No CRM sync, field mapping, deduplication, conflict rule, API or rate limit appears anywhere — not even CSV import is evidenced. A product page that produces no data-model facts is the whole answer here. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed, behavioural data leaving the EU with no stated basis.
3 — EU data residency for storage while tracking, sending or support access remain non-EU, or the contracting entity sits outside the EU.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — tracking scripts, AI scoring, analytics — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.
The Demand Gen Lead
Hosting location is unstated beyond 'Tier-3 and PCI-DSS datacenters', data residency is unknown, and the chain leaks: transfers to the USA and India on DPF/SCCs, and an AI chatbot running on OpenAI with Chatbase and Karumi in the wings. The full subprocessor list sits inside the DPA rather than on public pages, and the pipeline couldn't confirm the contracting entity despite EU entities being named — for behavioural profiles of named EU people that is not a chain I'd sign. 3
The Sales Ops Manager
Hosting location is unstated beyond 'Tier-3 and PCI-DSS certified datacenters,' and the pipeline could not confirm jurisdiction, ownership, residency or subprocessor exposure — while personal data flows to the USA and India. Transfers do carry a stated DPF/SCC basis and subprocessors are enumerated in the DPA with the AI vendors named, which lifts it above the floor but nowhere near confirmed EU processing end to end. 3
The Data Protection Officer
A German Brevo GmbH is named as controller and transfers to the USA and India are declared with DPF or SCC as the stated basis, which is more than the bottom anchor allows — but hosting location is unstated beyond 'Tier-3 datacenters', the subprocessor list lives only inside the DPA rather than published, Brevo operates in the USA, and OpenAI sits in the chatbot chain. The pipeline confirmed no jurisdiction or residency at all, and with behavioural profiles of EU residents at stake I do not give benefit of the doubt. 3
The Lifecycle Marketer
The controller named is European (Brevo GmbH, Berlin) and transfers to the USA and India are at least named with DPF/SCC bases rather than undocumented, which lifts it off the floor. But hosting location is unstated beyond 'Tier-3 and PCI-DSS datacenters', the subprocessor list lives only inside the DPA rather than published, and the AI chain runs through OpenAI and Chatbase — for behavioural profiles of named EU residents I weigh that heavily, so rubric level 3. 3
The Solution Architect
The vendor is European per provenance and there is a German controller entity with stated transfer bases (DPF/SCCs) for USA and India, but hosting location, the contracting entity and the subprocessor list are all unconfirmed on the vendor's own captured pages — the pipeline scored the attributes 0/10. Unstated hosting is anchor-0 language; the two points buy only the stated legal basis and the EU vendor identity. 3
The Skeptic
Residency, ownership and the contracting entity are all marked unknown; the policy names Tier-3 datacenters without a location, transfers behavioural data to the USA and India under DPF/SCCs, and keeps the operative subprocessor list inside the DPA rather than published. Named US subprocessors like OpenAI on the chatbot and a stated transfer basis are the only things keeping this off the floor for a buyer who weighs named-profile profiling heavily. 3
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
0 — No public prices at all; every tier is a sales conversation, and onboarding fees are never mentioned.
3 — A contact-tier headline exists, but the tier where journeys, scoring or CRM sync begin is unstated, as is any mandatory implementation fee.
5 — Contact-tier prices public with billing period and send limits stated, but at least one commonly needed capability sits in an unpriced enterprise tier.
8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.
The Demand Gen Lead
Tier structure and email ceilings are public — Starter from 5,000, Professional from 150,000 emails/month, 10 users — but no actual price figures, contact tiers, feature boundaries, overage rates, or onboarding fees are captured, and Enterprise is 'Auf Anfrage'. I cannot compute an annual invoice from this, and I can't tell which tier automation begins in, which is the only tier I care about. 2
The Sales Ops Manager
The pricing page publishes tier labels with send limits (from 5,000 to 150,000 emails/month, 10 users in Professional) but no actual prices, contact tiers, overage rates, onboarding costs or VAT treatment in the confirmed facts, and Enterprise is 'auf Anfrage.' I cannot compute an annual invoice from this, so it sits between the nothing-public and headline-only anchors. 2
The Data Protection Officer
Tier names and email volumes are public — Starter from 5,000, Professional from 150,000 emails/month with 10 users — but no price figure, billing period, contact tier, overage rate or onboarding cost is captured, and Enterprise is 'Auf Anfrage'. The tier where automation features actually begin is nowhere stated, which for this row is the number the buyer needs most. 2
The Lifecycle Marketer
Tier structure and send limits are public — Starter 'Ab 5.000 E-Mails/Monat', Professional at 150,000 emails and 10 users — but no actual prices, no contact tiers, no statement of which tier unlocks journeys or CRM sync, and Enterprise is 'Auf Anfrage'. I cannot compute an annual invoice from this, so it sits between the 0 and 3 anchors. 2
The Solution Architect
Tier structure with monthly send limits is public — Starter from 5,000 and Professional from 150,000 emails/month with 10 users — but there are no currency figures, no contact-based pricing, no overage or onboarding terms, and Enterprise is 'Auf Anfrage'. The tier where automation actually begins is unstated, so no buyer can compute a real annual invoice from this sheet. 2
The Skeptic
What was captured is a tier skeleton without prices: 'Ab 5.000 E-Mails/Monat', 'Ab 150.000 E-Mails/Monat', and Enterprise at 'Auf Anfrage' — no euro figure, no contact tier, no billing period, no overage. The two things I always look for — which tier journeys actually start in and the mandatory onboarding fee — are both absent, so no buyer can compute an annual invoice from this sheet. 2
European sovereignty — proven facts
2 of 4 dimensions provenBuilt 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 6 Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 3 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 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. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Data residency. The EU location is asserted only on marketing/security pages (supported by "den Server-Standort EU" in S3) without naming the hosting provider, and the privacy-policy excerpt does not state a storage location.
- Weak sourcing — Subprocessors. WhatsApp and Facebook advertising are optional platform functions whose role Brevo leaves open (controller or processor), the hosting provider of the EU servers is never named, and Google Fonts, reCAPTCHA, Cloudflare Turnstile, Karumi and Chatbase are website tools only.
- 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.
- 26 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
- 12 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
- 9 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
- 7 legal 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 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
- 3 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product page www.brevo.com Checked 16 Sep 2026 Details →
- 2 Pricing www.brevo.com Checked 16 Sep 2026 Details →
- 3 Privacy policy www.brevo.com Checked 16 Sep 2026 Details →
- 4 Privacy policy www.brevo.com Checked 30 Sep 2026 Details →
- 5 Imprint www.brevo.com Checked 30 Sep 2026 Details →
- 6 Security / trust page — found from the homepage www.brevo.com Checked 30 Sep 2026 Details →
- 7 Journeys & orchestration — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →
- 8 Journeys & orchestration — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →
- 9 Channels & personalisation — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →
- 10 Channels & personalisation — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →
- 11 Consent, tracking & profiling — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →
- 12 Consent, tracking & profiling — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →
- 13 CRM integration & data model — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →
- 14 CRM integration & data model — found from sitemap www.brevo.com Checked 1 Oct 2026 Details →