Brevo
How to configure Brevo at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Receive marketing offers, Receive personalised marketing offers
Overview
This guide explains how to implement different privacy configurations for Brevo (formerly Sendinblue; includes the former Newsletter2Go) on a website and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Brevo sign-up forms and the Brevo tracker on the customer's website. Brevo is a French company. Email pixel tracking is handled through Brevo's per-contact pixel tracking consent (Settings > Contacts > Per-contact pixel tracking consent) and is outside the cookie banner.
What the service does in this scope. The Brevo tracker connects Brevo apps (Automations, Segments, Conversations) to the website. Before installing it, you choose first-party or third-party cookies. By default, a cookie is placed on the visitor's computer, and the visitor can be associated with an existing contact after identifying themselves (e.g. via an email click or form). With first-party cookies, Brevo appends _sc (marketing) or _se (transactional) parameters to links.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Sign-up forms only; no tracker. |
| Configuration B — Higher risk | Brevo tracker with first-party cookies; after consent. |
| Configuration C — Higher risk | Brevo tracker with third-party cookies; after consent. |
No configuration without prior consent for the tracker. For A, verify in the browser whether the form sets cookies before deciding whether it can load without consent.
Step 1 — Configure Brevo
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Receive marketing offers | Receive marketing offers; Receive personalised marketing offers | Receive marketing offers; Receive personalised marketing offers |
| 2 | Brevo tracker | Install via plugin, GTM or manually | Not installed | After consent | After consent |
| 3 | Cookie settings | Tracker setup, Step 1 | — | First-party cookies | Third-party cookies |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Per Brevo's DPA; add the United States if the DPA lists US cloud sub-processors.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk |
|---|---|---|---|
| Processing purposes | Receive marketing offers | Receive marketing offers, Receive personalised marketing offers | Receive marketing offers, Receive personalised marketing offers |
| Tracking method | No tracking | First party tracking (cross-session) | Third party tracking (crosssession, cross-website) |
| Identifier | Direct identifier (on submission) | Device identifiers, Direct identifier | Device identifiers, Direct identifier |
| Data categories | User-provided data, direct identifier | Browsing and interaction data, Device identifiers, User-provided data, direct identifier, Users' profiles | As B |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | Profile based | Profile based |
| Maximum storage duration | Per contact retention | Per cookie inspection | Per cookie inspection |
| Processing location | Per DPA | Per DPA | Per DPA |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on