Email tracking pixels: the Garante's guidelines and what to document
The Italian data protection authority's guidelines on email tracking pixels (Garante provvedimento of 17 April 2026, reg. provv. n. 284, docweb 10241943, Italian text; Gazzetta Ufficiale, Serie Generale n. 98, 29 April 2026) address anyone who uses a tracking pixel in an email. They require information to the recipient and, save in the cases where consent is not needed, which the Garante illustrates with examples, the recipient's prior consent. The Garante's six-month adaptation period ends on 29 October 2026.
Below is what the provvedimento says, paragraph by paragraph, and what to document. The article describes the text and the evidence to keep. It does not assess your organisation's situation. The guidelines are in Italian; the English descriptions and translations here, including the English rendering of the title, are our own unofficial ones, and the Italian text prevails.
At a glance
| Item | Detail |
|---|---|
| Act | Provvedimento of the Italian data protection authority (Garante per la protezione dei dati personali) of 17 April 2026, "Linee Guida in materia di utilizzo di tracking pixel nelle comunicazioni di posta elettronica" (guidelines on the use of tracking pixels in email), reg. provv. n. 284 |
| Publication | Gazzetta Ufficiale, Serie Generale n. 98 of 29 April 2026 (code 26A02030) |
| Rules applied | Art. 122 of the Italian Privacy Code (d.lgs. 196/2003), which transposes Directive 2002/58/EC; Regulation (EU) 2016/679, in particular Arts. 5, 7, 12 et seq., 25 and 26 |
| Who it addresses | the parties listed in the operative part, down to any other party that uses tracking pixels in any capacity |
| Date | six months from publication in the Gazzetta Ufficiale (operative part), that is 29 October 2026 |
What a tracking pixel is
The provvedimento describes tracking pixels as images, often transparent and only one pixel in size, that are not contained in the email itself but hosted on remote servers (para. 1). When the message is opened, the image is downloaded from the sender's server, and the process lets the sender or one of its partners learn that the email was opened and possibly derive further information such as the type of device, the time spent reading and the number of later openings (para. 1).
On that basis the Garante concludes that the ePrivacy Directive and Art. 122 of the Privacy Code apply to the use of tracking pixels in email (para. 1). In the inspections it carried out to prepare the guidelines, the authority found pixels in use in almost every case, for purposes ranging from deliverability and fighting spam to audience measurement and personalising messages (para. 2).
Information to the recipient
For the use of tracking pixels in email to be lawful, it must be made known to the recipient in advance, whatever the purpose of the message or the type of sender (para. 4). The information may be given in layers (para. 4), for example in short form on the form where you collect the address, with a link to more detailed information.
If you already send emails with tracking pixels, the Garante lets you give the information with the next useful message, or at the first break in the existing relationship (para. 4). This covers the information only; for consent, where it is needed, paragraph 6 applies.
Examples where consent is not needed
Art. 122(2-bis) of the Privacy Code sets a general prohibition, save for the exceptions the provision allows (para. 5). The Garante considers that a specific consent can be dispensed with in a significant number of cases, for example (para. 5):
- a statistical count of the overall open rate of messages, using anonymisation techniques so that no personalised measurement is possible; the authority suggests using the same pixel for every recipient of a campaign and anonymising the other related technical data (IP address, client);
- security measures in a user authentication process, for example confirming an account activation, a password change request or a data-subject rights request, to check that the message is opened on a device known to belong to the user;
- institutional or service messages the controller is legally required to send, where the recipient's actual awareness of the message matters.
These are examples. Placing a processing operation under one of the exceptions is first of all the controller's assessment, under the GDPR's accountability regime (para. 5). The information to the recipient is still due in these cases, since the Garante requires it whatever the purpose of the message (para. 4).
Consent and withdrawal
In the other cases, a controller that wants to use pixels must obtain the recipients' prior consent (para. 6). The Garante's examples include measuring individual open rates to improve promotional campaigns, adapting how often you send to the interest observed, and using reading data to build commercial profiles (para. 6). Also in paragraph 6:
- for new processing, consent should preferably be collected when the email address is collected;
- consent to the tracking can, in principle, form part of the more general consent to receive promotional messages, provided the request is phrased neutrally and without pressure;
- withdrawal must be easy and must also be possible in granular form, that is limited to the tracking alone while still receiving the emails, for example through a standard icon or a link in the footer;
- for processing already under way that involves sending commercial emails with pixels, on the basis of consent or another valid legal basis, the controller, after giving the information with the next useful message, must put in place and make known a mechanism for withdrawal, including granular withdrawal; the Garante calls this arrangement a transitional regime that applies only to processing already under way, to be phased out as new processing becomes subject to prior consent;
- a recipient who refuses the tracking must keep full use of the service, with no limitation for that reason alone;
- the controller records every choice the data subject makes (with a reference to Art. 7(1) GDPR);
- for privacy by design (Art. 25 GDPR), the Garante suggests an unintelligible, non-sequential identifier in place of the email address, with the link between the two kept in a separate internal layer of the platform.
Roles: sender, providers, technology
The provvedimento lists the parties involved: the sender, the email-sending service provider, the provider of rented distribution lists, the tracking-technology provider, the content creator and the recipient (para. 3). The parties that use tracking pixels must each define their own role under data protection law case by case, in line with the accountability principle in Art. 5(2) GDPR and, where relevant, Art. 26 GDPR on joint controllership (para. 3).
The 29 October 2026 date
The operative part sets a period of six months from publication in the Gazzetta Ufficiale. The guidelines were published in the Gazzetta Ufficiale, Serie Generale n. 98 of 29 April 2026, so the adaptation period ends on 29 October 2026. The period runs from publication in the Gazzetta, and 17 April 2026 is the date of adoption.
What to document
First, check whether the guidelines concern you: they address anyone who uses tracking pixels in email (operative part). The obligation in ObligoBoard applies if the emails your organisation sends contain tracking pixels or similar open-tracking. If it applies, this is its evidence list, each item with the paragraph of the provvedimento it relates to:
- inventory of your email tools with their tracking settings (para. 2);
- the consent wording and where it is captured (para. 6);
- the record of each recipient's tracking choices, including withdrawals of the tracking alone (para. 6);
- the suppression rule for recipients without consent (para. 6);
- the withdrawal mechanism (para. 6);
- confirmation that recipients who refuse or withdraw tracking consent keep full use of the service (para. 6);
- the agreements setting out the role of your email service provider and any list or tracking-technology provider (para. 3);
- the relevant privacy-notice extract (para. 4);
- the retention setting (a process choice: the provvedimento does not set a period);
- if you rely on a case where consent is not needed: which one, for which emails, and why (para. 5).
If the obligation does not apply, keep a dated statement with a screenshot of the settings showing open-tracking disabled, and re-confirm it every year. The statement and the annual cadence are process choices.
Finding it in ObligoBoard
In ObligoBoard this obligation is "Email tracking pixels — consent and transparency (Garante guidelines)", and it is tracked with the reference to the Garante's provvedimento (reg. provv. n. 284, docweb 10241943). Organisations whose country is Italy receive it in the GDPR Basics framework: its guidance sets out the steps described here, the evidence is the list above, and it is reviewed annually.
ObligoBoard isn't open yet. See what ObligoBoard is
General information, not legal advice or an attestation; drafted with AI assistance. The official text of the provvedimento prevails. For any question of interpretation, consult your adviser.
Related Posts
Legislative Decree 179/2026 on AI in Italy. Authorities, fines, employers
Italy's Legislative Decree 179/2026, in force from 23 October 2026, names the AI authorities and sets duties for employers using AI. What to document.
Law 132/2025: obligations and Decree 160/2026, what to document
The obligations under Italian Law 132/2025 and Legislative Decree 160/2026 on AI: what the rules say, what to document and do, and where to read the text.