BrevoOpen-tracking pixel, click tracking and unsubscribe

Brevo intègre un pixel de suivi dans vos emails afin de mesurer les ouvertures

Caveat By default, with individualised links for clicks, "enregistrant des données d'engagement par contact dans les deux cas" (recording engagement data per contact in both cases). The page sets out a purpose-over-channel doctrine: a promotional email sent through transactional SMTP/API remains subject to consent — a notable reversal of the classic transactional exception.

À propos des pixels de suivi des emails et de la recommandation de la CNIL dans Brevo · Help centre · last reviewed on 08/20/2026 · confidence medium

Ces rapports suivent qui a ouvert les emails et cliqué dessus

Caveat Named tracking of opens and clicks; links individualised per contact (CNIL page). Dates are rare and shown in the body: since 06/02/2025 the open rate includes Apple MPP, and since 08/07/2025 bot activity — both can be excluded from reports. Global switch = anonymous tracking.

Analyser et exporter le rapport de votre campagne email · Help centre · last reviewed on 08/20/2026 · confidence medium

Lorsque cette option est définie sur Non, ces contacts ne sont pas suivis. » (texte du sous-réglage « Suivre les contacts dont le consentement est inconnu », verbatim)

Caveat The same mechanism as consentement-sans-pixel: removing tracking per contact (opens and clicks) goes through recorded consent, and the message is still sent. Disabled by default at account level. Independent of the sending infrastructure (unlike Braze, which is limited to SparkPost/SendGrid).

Per-contact consent to pixel tracking · Interface · last reviewed on 08/23/2026 · confidence high

Les ouvertures et les clics collectés en dehors du consentement explicite, par exemple dans le cadre de l’exemption de délivrabilité, ne sont pas associés à un profil de contact.

Caveat Removing tracking per contact goes through recorded consent (box observed set to "oui" (yes) in the tool on 23 August). The page says that some opens are still collected without explicit consent, for deliverability purposes, without being linked to the profile: an image therefore still loads for a contact who has not consented, and it is the link to the profile that is removed, not the pixel. It never states that the pixel leaves the message; for the API, it says only that "Brevo ne suit pas les ouvertures ou les clics pour cet email" (Brevo does not track opens or clicks for this email). To be settled on an email received by a contact who has refused consent.

À propos des pixels de suivi des emails et de la recommandation de la CNIL dans Brevo · Help centre · page dated 09/14/2026 · last reviewed on 10/17/2026 · confidence high

Suivez les ouvertures et les clics pour chaque contact uniquement lorsque le consentement a été enregistré pour ce contact. Lorsque cette option est désactivée, tous les contacts sont suivis. » (texte de l'interface, verbatim)

Caveat Disabled by default — the option was set to "Non" (No) when the screen was opened, and the interface text itself states the consequence: all contacts are tracked. The engine takes consent into account only once the option is enabled. On activation, a second setting appears: "Suivre les contacts dont le consentement est inconnu" (track contacts whose consent is unknown; Oui = unknowns are tracked / Non = they are not) — presence observed, default not established (the captured state may result from our own handling). The remaining question stands and can only be settled on a received send: for an untracked contact, is the pixel removed from the message or set aside on the server side?

Per-contact consent to pixel tracking · Interface · last reviewed on 08/23/2026 · confidence high

la recommandation de la CNIL vous autorise à le conserver même si un contact n'a pas accepté le suivi par pixel. … Cet attribut se met à jour automatiquement à chaque nouvelle ouverture

Caveat The box was observed set to "oui" (yes) in the tool on 23 August. The page states that the last-open date keeps being updated, for deliverability purposes, for a contact who has refused tracking: an image therefore still loads for that contact. To be settled on an email received by a contact who has refused consent.

À propos des pixels de suivi des emails et de la recommandation de la CNIL dans Brevo · Help centre · page dated 08/31/2026 · last reviewed on 09/11/2026 · confidence high

Ajouter une case à cocher de consentement au suivi par pixel à vos formulaires … Seuls les contacts avec Oui sont suivis pour les ouvertures et les clics

Caveat Collected through a checkbox in sign-up and profile-update forms, withdrawn through a link in the footer. The choice is applied to every send, on all channels, transactional included.

À propos des pixels de suivi des emails et de la recommandation de la CNIL dans Brevo · Help centre · page dated 08/31/2026 · last reviewed on 09/11/2026 · confidence high

l'adresse email et l'adresse IP de vos destinataires seront masquées et remplacées par la mention Contact anonyme ou Données anonymes. Vous aurez toujours les dates d'envoi et de remise, ainsi que la date d'ouverture et le décompte

Caveat The anonymous mode exists, disabled by default, and must be enabled separately for campaigns and for transactional emails. It does not remove the image. Each open is still recorded and dated, on one line per masked recipient, and "chargements par proxy" (proxy loads) are still logged; only the email address and the IP are anonymised. The page never states that the pixel remains: that is what a dated open per recipient implies. The vendor nonetheless presents the option as a way of disabling tracking (article "Analyser et exporter le rapport de votre campagne email"). This is a reclassification against the definition (no longer loading an individualised image), not a change of page: the rewrite of 7 October does not affect the substance. The "yes" of 20 August rested on the existence of the mode.

Puis-je anonymiser le suivi des ouvertures et des clics pour mes emails ? · Help centre · page dated 10/07/2026 · last reviewed on 10/17/2026 · confidence high

Yes, Brevo automatically includes a list-unsubscribe header in your email campaigns and transactional emails.

Caveat Campaigns and transactional emails. On the Enterprise plan, a transactional email triggered by the recipient can carry List-Help instead.

FAQs - About list-unsubscribe and list-help headers in emails · Help centre · page dated 04/03/2026 · last reviewed on 09/11/2026 · confidence high

No action is needed on your side for the following requirements, which Brevo already handles automatically: … One-click unsubscribe support for the list-unsubscribe header (RFC 8058)

Caveat Presented among the Gmail, Yahoo and Microsoft requirements, with no date of introduction.

Comply with Gmail, Yahoo, and Microsoft's requirements for email senders · Help centre · page dated 07/10/2026 · last reviewed on 09/11/2026 · confidence high

The option to include a list-help header instead of a list-unsubscribe header is only available with an Enterprise plan, and under specific conditions.

Caveat Only on the Enterprise plan, for transactional emails triggered by the recipient (activation, order confirmation, reset). Elsewhere, List-Unsubscribe is also added to transactional emails. The vendor's CNIL page points out that a transactional email with a commercial purpose remains subject to consent for individual tracking.

FAQs - About list-unsubscribe and list-help headers in emails · Help centre · page dated 04/03/2026 · last reviewed on 09/11/2026 · confidence high

add the required DNS records (Brevo code, DKIM, DMARC), and verify the configuration

Caveat A notable automatic flow: Brevo connects to the client's registrar (login supplied) and adds the records itself; manual setup is possible. Selector not documented (ecosystem: mail._domainkey — to be observed).

Authenticate your domain with Brevo (Brevo code, DKIM, DMARC) · Help centre · last reviewed on 08/20/2026 · confidence medium

Since February 1, 2024, domain authentication is mandatory as part of Gmail

Caveat DMARC is set by the authentication flow (dated: mandatory since February 2024, with Microsoft following in May 2025). The opposite safeguard to Adobe's: if a DMARC record already exists, the automatic flow offers to replace it — declining requires manual setup. Brevo's default policy not read.

FAQs - About domain authentication (Brevo code, DKIM, DMARC) · Help centre · last reviewed on 08/20/2026 · confidence medium

verify it by entering the 6-digit code sent to the sender's email

Caveat Without an authenticated domain, sending is still possible with an address verified by a 6-digit code — a custom domain is not mandatory; an authenticated domain removes the need for this. The SMTP login xxx@smtp-brevo.com is a technical identifier, never a From — esp_signatures data.

Troubleshooting - Issues with Brevo SMTP · Help centre · last reviewed on 08/20/2026 · confidence medium

Date de consentement au suivi par pixel La date à laquelle le contact a accepté ou refusé le suivi par pixel. … Source du consentement au suivi par pixel La source via laquelle le contact a donné sa réponse

Caveat The date and source of the latest choice, not the history of its changes; the page does not say whether they can be exported.

À propos des pixels de suivi des emails et de la recommandation de la CNIL dans Brevo · Help centre · page dated 08/31/2026 · last reviewed on 09/11/2026 · confidence high

Configurez votre comportement par défaut en définissant Suivre les contacts dont le consentement est inconnu sur … Seuls les contacts avec Oui sont suivis pour les ouvertures et les clics

Caveat Two levels: the account enables per-contact consent and sets what happens to contacts whose consent is unknown; the contact, through its attribute, decides for itself. The setting applies to all channels, transactional included; the page does not mention a per-campaign setting.

À propos des pixels de suivi des emails et de la recommandation de la CNIL dans Brevo · Help centre · page dated 08/31/2026 · last reviewed on 09/11/2026 · confidence high