Tracking pixels in emails: what changes on 14 July 2026

Tracking pixels in emails: what changes on 14 July 2026

In brief

  • The CNIL adopted a recommendation on tracking pixels in emails on 12 March 2026. Companies have until 14 July 2026 to comply: pixels used for marketing purposes (performance measurement, profiling) require the recipient's prior consent. Only certain purposes (strict deliverability, security) remain exempted.

What is a tracking pixel?

A tracking pixel is an invisible image, often just one pixel in size (1×1), hosted on a remote server and inserted into the body of an email. When the recipient opens the message, their email client loads the image: this request tells the server that the email has been opened, at what time, from what type of device and from which IP address.

This technology produces the famous open rate displayed by email marketing tools. Without a pixel, this statistic does not exist.

The key point: displaying the pixel triggers reading of information on the recipient's device. It is precisely this mechanism that brings pixels within the scope of Article 82 of the French Data Protection Act.

Why the CNIL regulates tracking pixels

Email is a personal space, accessed after authentication. Placing a tracker there amounts to reading data on a private device. The CNIL indicates it receives a growing number of complaints about these practices, which led it to publish a dedicated recommendation.

This recommendation is based on guidelines 2/2023 of the European Data Protection Board (EDPB), which confirm that Article 5.3 of the ePrivacy Directive — transposed into Article 82 in France — does apply to pixels inserted in emails.

The golden rule to remember: it is the purpose of the pixel that determines whether consent is required, not the technology or the message format.

Consent required or exempted? The reference table

The core of the recommendation rests on a simple distinction between marketing purposes (consent) and strictly necessary purposes (exemption).

Purpose of the pixelConsentRegime
Measure and optimise campaign performanceRequiredMarketing
Profile interests to target elsewhereRequiredMarketing
Detect/analyse suspected fraudRequiredMarketing
Open measurement outside deliverabilityRequiredMarketing
Security and user authenticationExemptedNecessary
Strict deliverability (clean inactive addresses, adjust frequency)ExemptedNecessary
Transactional emails (invoice, password, confirmation)ExemptedNecessary

To remain within the 'deliverability' exemption, the CNIL recommends applying the principle of data minimisation: keep only the date of last opening (to the day, without the time), updated with each opening. See our dedicated article: Open rate: is consent required?.

Who is responsible? Roles according to the CNIL

The recommendation asks each player in the email chain to determine their role within the meaning of the GDPR:

  • The sender (the company that decides the sending and purposes) is the controller. They remain so even if they outsource tracker management.
  • The email service provider generally acts as a processor, according to the sender's instructions.
  • The tracking technology provider may become a joint controller if they use the data for their own purposes.
  • The email service provider is neither processor nor controller as long as they do not use the pixel data.

Note: a simple contractual clause transferring consent collection to a third party is not sufficient to discharge the sender from their obligation to provide evidence.

What to do before 14 July 2026? Two options

Option 1 — Disable marketing pixels. You give up performance measurement and pixel-based profiling. Result: no more consent to manage for these purposes. If your email tool does not allow you to disable these pixels, it may be necessary to consider another provider.

Option 2 — Keep marketing pixels.

  1. New contacts: collect consent from the point of email address collection, with a mention on forms, a withdrawal link and a record in the register.
  2. Existing database: for addresses collected before the recommendation, clearly inform of pixel usage and allow easy opposition by 14 July.

Good news: genuinely anonymised data may be reused without consent (the GDPR remains applicable to the anonymisation processing itself).

How to collect and withdraw consent

  • At the right time: from the point of email address collection, with a link to detailed information.
  • Purpose by purpose: each distinct purpose must be able to be accepted or refused separately (no bundling).
  • Without dark patterns: refusing must be as simple as accepting; inactivity means refusal.
  • Easy withdrawal: a withdrawal link in the footer of each email, without having to re-enter your address.
  • Choices remembered: no longer re-solicit for approximately six months after a refusal.

Finally, the company must be able to prove consent in an individualised manner (Article 7.1 of the GDPR): the record of each person and the conditions of collection.

Pixel and email: two distinct regimes

A common confusion: the right to send an email (governed by the CPCE) and the right to place a pixel in it (Article 82) are independent. Marketing to a customer about similar products may be permitted without consent… but inserting a performance measurement pixel in that same email may itself require the recipient's consent. See also: B2B prospecting and GDPR and B2C prospecting and GDPR.

Sources: CNIL, Recommendation on tracking pixels in emails, version adopted on 12 March 2026; EDPB, guidelines 2/2023 (version 2.0, 7 October 2024).

Take action

Measure your GDPR score from E to A with our free self-assessment, and prepare for the 14 July 2026 deadline with Data Comply One.

Measure my GDPR score →Request a demo

Frequently asked questions

Does the open rate require consent?

Yes, when it is used to measure and optimise campaign performance. It is exempted only if used strictly for deliverability (cleaning inactive addresses, adjusting frequency).

What is the compliance deadline?

Approximately three months after publication of the recommendation of 12 March 2026, i.e. 14 July 2026, with inspections announced.

Are transactional emails concerned?

Transactional emails (invoice, password, confirmation) fall under exempted purposes, but a marketing pixel inserted in such an email may itself require consent.

Is a clause with my service provider sufficient?

No. As the sender, you remain responsible for proving valid consent; a contractual clause does not replace this evidence.