CNIL Email Pixel FAQ Analysis: Links Not Directly In Scope

The click map in an email platform looks harmless until a regulator asks what, exactly, the click revealed about a person. Opened, clicked, browsed, scored, added to a segment, then retargeted, this is how a one pixel measurement habit becomes a profile. CNIL’s 22 juillet 2026 FAQ lands in that familiar compliance zone: tracking links are Non, pas directement covered by the email pixel recommendation, but the answer is narrower than growth dashboards would prefer. That matters because the practical question is not whether a link is shaped like a pixel. It is whether the email analytics stack reads or writes information, identifies a recipient, and then uses the event for deliverability, audience measurement, personalization, or something more ambitious. The law is rarely impressed by UI labels.

What the recommendation actually covers CNIL’s own

Recommendation on tracking pixels in emails frames the issue around invisible pixels inserted into emails, which it says are used for deliverability, audience measurement, and personalization. CNIL also notes that email is a personal space for consulting private content, accessible after authentication, which is a polite way of saying that the inbox is not a public billboard. The Recommendation points to the European Data Protection Board’s Guidelines 2/2023 on the technical scope of Article 5(3) of the ePrivacy Directive, as transposed into Article 82 of France’s Data Protection Act. For builders, Article 82 is not a slogan. It means the product team needs to know when its email instrumentation reads from or writes to a user’s terminal, what purpose that operation serves, and whether the resulting event is tied back to an identifiable person. A pixel used only to test deliverability is not the same product feature as a pixel feeding an individual interest score. If those two uses share the same event table, your documentation problem is already visible from the hallway.

The link answer is narrow, not permissive CNIL’s

FAQ answer on tracking links is counterintuitive because it says the pixel recommendation does not directly cover them. That is the Non, pas directement part, and it is doing real work. A tracked link is not an invisible image loaded in an email, so the Recommendation’s object is not automatically the same object. But the FAQ also points teams back to the same principles for assessing compliance, which is the part likely to survive the first enthusiastic sales meeting. If a link redirect records the recipient, campaign, timestamp, device information, and downstream behavior, the product has still created an analytics trail around email engagement. The cleaner implementation is to separate link routing needed for basic email operations from link tracking used for measurement, scoring, or personalization. Vendor contracts should require purpose level controls, clear event fields, retention settings, and a way to honor the recipient state your legal basis depends on.

France is not Italy, and that is the point Lewis Silkin’s comparative analysis

of CNIL and Italy’s Garante is useful because it distinguishes legal character from practical risk. According to Lewis Silkin, the Garante’s Guidelines carry regulatory force and impose a binding compliance deadline, while CNIL’s Recommendation is expressly neither regulatory nor exhaustive. The same analysis says CNIL has signalled that enforcement activity will follow, with a transitional period expected while CNIL provides guidance to professional stakeholders, including webinars. Mailjet also describes France and Italy as having published new recommendations for emails sent from and to people living in those countries, following public consultations. That is the operational headache. A single email product may need to support multiple country positions without pretending that an EU wide contact list has one uniform analytics rule. If your data model cannot turn off individual level open or click analytics by geography and purpose, the policy team will eventually discover that the product architecture has been voting without them.

What email analytics teams should change now Inside Privacy reported that

CNIL published its Recommendation on April 14, 2026, which gives teams a concrete document to map against their own systems. Start with the event inventory, not the consent banner copy. For every email event, identify whether it comes from a pixel load, a link redirect, or another mechanism, then record the purpose, stored fields, retention period, and whether the event is used at individual or aggregate level. The product decision that follows is usually less dramatic than the internal memo. Turn tracking features into purpose based switches, avoid bundling deliverability diagnostics with personalization analytics, and make aggregate reporting genuinely aggregate rather than a thin wrapper over user level logs. If the vendor answer is we welcome clarity from regulators, ask for the data flow diagram, the configuration screen, and the deletion behavior. Their lawyers may be panicking, but your release train still needs tickets. The next thing to watch is not a slogan about privacy friendly analytics. It is whether CNIL’s promised stakeholder guidance and later enforcement activity treat link tracking as a close cousin of pixels in practice. Email teams that design around purpose separation now will have less refactoring to do when the regulator stops explaining and starts asking for records.