About email tracking pixels and the CNIL recommendation in Brevo

The following help article is for educational purposes only and should not be construed as legal advice. Brevo declines all responsibility for the content of this help article. The information it contains is of a general nature only and cannot be applied to the specific situation of any individual or legal entity. It is not necessarily complete, exhaustive, accurate, or up-to-date. We strongly recommend that you consult your DPO, lawyer or attorney for any interpretation or application of the laws related to pixel tracking.

On April 14, 2026, the CNIL (France's data protection authority) published a binding recommendation on email tracking pixels. Except for a few exempted purposes, email tracking pixels require prior, explicit, and separate consent from your recipients. This recommendation only applies to marketing content sent to contacts based in France.

Read the CNIL recommendation

❗️ Important
Since April 14th, 2026, both the unsubscribe link and the revoke pixel tracking consent link are mandatory in the footer of your emails to your future French contacts.

What this recommendation means for your email tracking

By default, Brevo embeds a tracking pixel in your emails to measure opens and record per-contact engagement data. Under the CNIL recommendation, collecting and storing that individual-level data requires explicit consent from each recipient, collected separately from consent to receive your emails.

This applies to all emails sent to contacts based in France, regardless of the sending channel you use (Email Campaigns, Automations, or Transactional email via SMTP or API).

❗️ Important
This recommandation applies based on the purpose of the email, not the sending channel. Sending a promotional email through the SMTP API or a transactional template does not make it transactional. If the content is commercial, individual tracking requires consent.

What is subject to the consent requirement?

The following table lists a few tracking use cases that require explicit consent:

Use case

Status under the CNIL recommendation

Send-time optimization at individual contact level ❌ Requires explicit consent
Targeting non-openers from a previous campaign (commercial purpose) ❌ Requires explicit consent
Engagement scoring feeding segmentation or personalization ❌ Requires explicit consent
Win-back and reactivation campaigns targeting non-openers ❌ Requires explicit consent, commercial purpose removes the deliverability exemption
Behaviorally triggered promotional emails (abandoned cart, price drop, browse abandonment) ❌ Requires explicit consent, event-triggered does not mean transactional

➡️ To learn more about what is subject to the consent requirement, check the full CNIL recommendation.

Set up per-contact tracking consent in Brevo

Per-contact tracking consent lets you continue collecting individual engagement data, such as opens, but only for contacts who have explicitly given permission.

✅ Allows you to... ❌ Does not allow you to...
  • Track opens for contacts who consented
  • Use engagement data to personalize and segment
  • Trigger automations based on engagement behavior
  • Let contacts manage their tracking preferences via update profile forms
  • Track contacts who have declined consent
  • Track contacts in Unknown status unless you explicitly choose to do so during setup
  • Assume silence means consent, you must actively collect consent

Once you activate per-contact tracking consent, Brevo automatically creates three default contact attributes to manage each contact's tracking consent:

Attribute Description
Pixel Tracking Consent

Whether the contact agreed to be tracked: Yes, No, or empty.

Only contacts with Yes are tracked for opens, so you keep engagement data while respecting consent.

Pixel Tracking Consent Date The date the contact accepted or refused pixel tracking.
Pixel Tracking Consent Source The source through which the contact gave their answer, for example a sign-up form.
💡 Good to know
Brevo also keeps a Last Email Open Date attribute for each contact. This attribute is not a consent attribute. When collected under an exempted purpose (ex: deliverability), the CNIL recommendation allows you to keep it even if a contact did not agree to pixel tracking.

Step 1: Activate per-contact tracking consent

  1. Go to Settings > Campaigns > Default settings > Tracking & reports.
  2. Under the Tracking section, select Yes under Per-contact pixel tracking consent to activate per-contact consent management for all your email channels.
    settings_tracking-pixels_en-us.png
  3. Configure your default behavior by setting Track contacts whose consent is unknown to either:
    • Yes, contacts continue to be tracked while you progressively collect consent.
    • No, contacts are not tracked until they explicitly consent.
  4. Click Save. All existing contacts are automatically set to unknown status.

Step 2: Add a pixel tracking consent checkbox to your forms

Add a pixel tracking consent checkbox to every form where you collect information from your French contacts, including your sign-up forms and your profile update form. This lets your contacts choose whether they agree to be tracked, whether they are joining your list for the first time or updating their preferences.

Your contacts' answer is saved to the _PIXEL_TRACKING_CONSENT attribute on their contact profile, so you can filter and segment your contacts based on their tracking consent.

  1. Open the form you want to edit, either your sign-up form, or profile update form.
  2. From the Build tab, drag and drop a Checkbox field into your form.
  3. In the Object type dropdown, select Contact.
  4. In the Attribute list dropdown, select the _PIXEL_TRACKING_CONSENT attribute.
    form_pixel-tracking_en-us.png
  5. Next to the checkbox, enter a consent statement to ask for your subscribers' consent for pixel tracking. For example, "I agree to be tracked through email tracking pixels for personalized communications".
  6. In the left panel, add a label name and a help text so your subscribers clearly understand that you will use tracking pixels to send them personalized communications.
  7. Continue editing your form, then publish it.

➡️ To learn more about forms, check our dedicated articles Create or edit a sign-up form, or Create or edit a profile update form.

Step 3: Manage contacts added before you activated tracking consent

If you have French contacts who subscribed between April 14 and July 14, 2026, they may have been tracked before you had a way to collect their pixel tracking consent. Use one or both of the following options to bring these contacts up to date.

Add a pixel tracking consent checkbox to your profile update form

Ensure you added a pixel tracking consent checkbox to your profile update form so these contacts can share or change their consent at any time.  

➡️ To learn more about how to add a pixel tracking consent checkbox to your update profile forms, check our dedicated article Create or edit a profile update form.

(Optional) Manually remove your contacts' consent until they actively opt in

You can also decide to treat these contacts as if they had not given consent, until they tell you otherwise through your profile update form:

  1. From the CRM > Contacts page, create a segment of contacts who meet all of the following conditions:
    • Contact attributes > _PIXEL_TRACKING_CONSENT > Not filled
    • Contact attributes > Creation date > Fixed period > 14/04/2026 - 14/07/2026
    • (Optional) The contact attribute that allows you to filter only French contacts
      contacts_segment-pixel-tracking-unknown_en-us.gif
  2. (Optional) Click Save as segment if you want to keep track of those contacts.
  3. Click the checkbox on the left of the CONTACT column and click Select all contacts.
  4. Click More actions > Edit.
  5. In the Update the following attribute dropdown, select the PIXEL TRACKING CONSENT attribute.
  6. In the PIXEL TRACKING CONSENT dropdown, choose No.
  7. Click Update to confirm.

These contacts are considered as not tracked until they change their answer through your profile update form.

Step 4: Add an easy revoke consent link to your email footers

Give contacts ongoing control over their tracking consent by including a revoke consent link in your email footers. This lets recipients change their tracking pixel consent at any time, without friction. Once they click this link, your contact's pixel tracking consent attribute is automatically set to No.

❗️ Important
Since April 14th, 2026, both the unsubscribe link and the revoke pixel tracking consent link are mandatory in the footer of your emails to your future French contacts.

Depending on your email editor, the procedure differs. Open the tab that matches your email editor:

Drag & Drop Editor HTML and Simple editors
  1. Drag and drop a Button content block into the email canvas.
  2. Click the button to open its settings in the left panel.
  3. In the Link settings section, choose from the Type of link dropdown the Revoke pixel tracking consent link.
    dde_button-revoke-pixel-tracking_en-us.png
  4. Replace Call to action with clear text that makes it obvious your recipients can decline the use of tracking pixels, such as "I prefer not to be tracked."
email_revoke-pixel-tracking-footer_en-us.png

Specific considerations for B2B communications

The CNIL recommendation makes clear that the consent requirement for tracking pixels is independent of the consent regime for sending the email.

A B2B prospecting email sent under professional exemptions is legally sendable without consent. However, inserting a tracking pixel into that email still requires separate, explicit tracking consent from the recipient.

For B2B cold outreach and prospecting sequences, use per-contact tracking consent to collect explicit tracking consent before deploying individual pixels. Deliverability exemptions apply in B2B under the same conditions as in B2C.

❗️ Important
The CNIL allows you to bundle consent for marketing communications with the consent to pixel tracking in some cases, under strict conditions. Seek advice from your DPO or lawyer if you intend to apply bundled consent.

❓ FAQs

Expand the accordions below to find answers to common questions about the CNIL recommendation on tracking pixels.

Does a tracking pixel in an email require consent?

Yes. The CNIL considers that loading a tracking pixel counts as an operation performed on the recipient's device. Prior consent is therefore required, unless the use falls under one of the defined exemptions, such as deliverability measurement.

Is measuring my newsletter's open rate banned without consent?

It is not banned, but it is regulated. If you measure opens to optimize campaigns, personalize content, or adjust sending frequency, consent is required. An exemption exists only for deliverability measurement, meaning identifying inactive contacts to clean your list, and only for transactional emails or emails sent with consent, with minimal data retention.

Do I need to collect new consent from my existing contact list?

The CNIL does not require you to retroactively collect consent for contacts you already had before this recommendation. However, you must clearly inform them about the use of tracking pixels and give them an easy way to opt out of future tracking, for example using the revoke consent link in your email footer.

➡️ If some of these contacts subscribed between April 14 and July 14, 2026, check Step 2: Manage contacts added before you activated tracking consent for additional steps.

Does agreeing to receive a newsletter also count as consent to tracking?

No. The CNIL draws a clear distinction between the two. Consent to receive an email is separate from consent to pixel-based tracking. Unless the pixel's purpose falls under an exemption, separate and specific consent for tracking is required.

Are transactional emails covered by the CNIL recommendation?

Yes, the recommendation applies to any tracking pixel regardless of the sending channel. However, transactional emails (order confirmations, shipping notifications, password resets, security alerts) benefit from the deliverability exemption, which only covers global, aggregate tracking, such as knowing whether an email was opened to measure deliverability or clean your list.

Individual-level tracking of transactional emails, for example linking opens to a specific contact for personalization or engagement scoring, is not covered by the exemption and requires the same explicit consent as any other email.

We are working on giving you more granular control over tracking consent for transactional emails specifically. We will share more details when this is available.

⏭️ What's next

🤔 Have a question?

If you have a question, feel free to contact our support team by creating a ticket from your account. If you don't have an account yet, you can contact us here.

If you’re looking for help with a project using Brevo, we can match you with the right certified Brevo Agency partner.

💬 Was this article helpful?

2 out of 2 found this helpful