Pixel tracking is a way for a website or email to tell another service that someone viewed it or did something on it. The name comes from the original technique: a tiny, invisible 1x1 image. When your browser loads that image from the tracking company's server, the request itself reports the visit.
How a tracking pixel reports an event
An image request carries information: the page address, the time, the browser, and any cookies that server previously set. Add details to the image URL, such as ?event=purchase&value=49, and the server learns what happened. Modern "pixels" like the Meta Pixel, TikTok Pixel or the Google tag are mostly JavaScript snippets rather than images, but they work the same way: code on your page sends events (PageView, AddToCart, Purchase) to the platform. Many also fall back to a plain image request when scripts are blocked.
Email uses the original image method. A hidden image in a newsletter loads when the email is opened, which is how email tools count opens.
A real example: tracking a sale from an ad
A skincare shop installs the Meta Pixel and fires a Purchase event with the order value on its thank-you page. When someone clicks an Instagram ad and buys, Meta matches the event to the ad click and reports the sale in Ads Manager. That same data builds retargeting audiences and helps the ad system find similar buyers. Without the pixel, the campaign's ROAS cannot be measured.
Where pixels fall short
Ad blockers, Safari and Firefox tracking protection, and Apple's Mail Privacy Protection (which preloads images, inflating open counts) all reduce accuracy. Because of this, Meta offers the Conversions API and Google offers server-side tagging, which send the same events from your server instead of the visitor's browser. Many sites run both side by side.
When a small business needs one
If you run paid social or search ads that aim for sales or leads, install the relevant pixel or tag before spending, ideally through Google Tag Manager. If you do not advertise, you probably do not need ad pixels at all, only privacy-friendly analytics.
Pixel tracking mistakes
- Firing before consent. In the EU and UK, ad pixels usually need consent under GDPR and cookie rules.
- Double-firing purchases, for example when the thank-you page is refreshed, which inflates results.
- Sending personal data in URLs, such as raw email addresses in event parameters.
- Never testing. Use Meta's Events Manager test tool or Tag Assistant to confirm events arrive.
Related terms
- Cookie: how a pixel recognises a returning browser.
- Retargeting: the main use of pixel audiences.
- Google Tag Manager: a tidy way to install pixels.
- GDPR: the consent rules pixels must respect.