What a tracking pixel is
A tracking pixel is a small piece of code or a tiny image, often invisible, that a website or an email loads from another server. When the page or message is opened, the browser or email app requests that resource, and the request itself passes some information to the server that provided it. Platforms for advertising, analytics and email use this approach to count visits, link actions to campaigns and build audiences.
You may also hear the term “tag”. A tag is usually a script that runs on the page and can do more than a plain image, such as record clicks, form submissions or purchases and send those events along. Tools called tag managers help site owners add and organise several of them. In practice marketers use the words loosely, and in this article “pixel” covers both the image and the script type. This is general information, not legal advice; the rules on tracking technologies vary by country and change.
What they commonly collect
Exactly what a pixel collects depends on the provider and how it is configured, so check each tool’s current documentation rather than assuming. In general terms, the following kinds of information are commonly involved:
- Technical details. The address of the page, the type of browser and device, screen size, language and the time of the visit. A request to a server also normally includes an IP address.
- Identifiers. A cookie or other identifier that lets the provider recognise the same browser again, sometimes across visits or across sites.
- Referrer data. Where the visitor came from, such as a search result or an ad.
- Events. Actions such as viewing a product, adding to a basket, submitting a form or completing a purchase, sometimes with details like the product or the order value.
- Logged-in or form details. If configured to do so, some tools can receive details such as an email address, often in a scrambled form. Whether and how this happens depends on the setup.
In email, a pixel in the message can signal that it was opened, along with the time and device type. Several mail apps now load images in ways that blur this signal, so open counts are less dependable than they once were.
Why this raises privacy questions
A pixel usually means a third party receives information about your visitors. The visitor may not be aware of this, and the third party may combine what it learns with data from elsewhere. Many privacy rules therefore expect site owners to be open about it and, depending on the law and the type of tracking, to ask for permission before the pixel runs. This is a large part of why cookie consent banners exist.
Some situations deserve extra caution. Pages related to health, finance, children or other sensitive subjects can reveal a lot about a person just by being visited. Sending event details from those pages to an advertising platform could be a serious concern in some places. If your site touches such areas, get proper advice before adding marketing tags.
Good practice for site owners
Know what is installed
Make a list of every pixel and tag on your site. Many sites carry old ones left by a former agency or an abandoned campaign. For each, write down the provider, the purpose, who set it up and what data it sends. A tag manager’s overview can help, but also check the page itself, since not everything is loaded that way.
Keep only what you use
If a tag has no current purpose, remove it. This is data minimisation applied to technology. Fewer tags can also help page speed, which affects user experience.
Configure with care
Review the settings of each tool. Many offer options to limit data collection, shorten retention or avoid sharing certain details. Which options exist and what they do changes over time, so read the provider’s current documentation. Avoid sending personal details in page addresses or event names, because these can end up in reports.
Respect consent choices
If your rules require consent for certain tags, make sure those tags do not load until the visitor agrees. A common mistake is a banner that records a choice while the tags fire anyway. Test it: open the site in a fresh browser session, decline non-essential options and check what loads, using the browser’s developer tools. This is worth rechecking after site changes.
Disclose in plain language
Your privacy notice should say what kinds of tracking technologies you use, why, who receives the data and how people can control it. “We use analytics and advertising tools to understand visits and measure our ads” is easier to understand than a long list of vendor names alone, though naming providers is also helpful. Keep it accurate as you add or remove tools.
Check your agreements
When you use a platform’s pixel, you typically accept its terms, which may place responsibilities on you, such as having proper notice and consent. Read them rather than skimming.
Pixels, retargeting and measurement
Pixels support retargeting, conversion measurement and audience building. These uses can be reasonable when disclosed and permitted. They also depend on technology that browsers and regulators keep changing, which is part of the story of fewer third-party cookies. Treat the data from any pixel as an imperfect estimate. It can miss visitors who decline tracking or use blockers, and it can double count.
A short audit checklist
- List every pixel and tag on your site and in your emails.
- Remove the ones you no longer use.
- Record the purpose and data sent by each.
- Confirm that consent-dependent tags wait for consent where required.
- Make sure your notice describes them accurately.
- Set a reminder to review the list on a regular schedule.
None of this ensures compliance with every law, and requirements differ widely. If you are unsure, take advice from a qualified professional familiar with the rules where your visitors live.