Tracking

Tracking Pixel

In short

A tracking pixel is a piece of code from an ad platform that records page views and conversions in the browser and reports them back to the platform.

Also known as: browser pixel, pixel tracking

A tracking pixel is a small piece of code from an ad platform that you add to your website. It records what visitors do in the browser, such as page views, purchases or enquiries, and reports those events back to the platform.

How does a tracking pixel work?

The name used to be literal: an invisible 1x1 image whose download sent a request to the ad server. Today a pixel is usually a JavaScript tag, for example the Meta Pixel, the TikTok Pixel, the LinkedIn Insight Tag or the Google Tag.

The script loads from the platform's servers, sets cookies such as _fbp, reads click IDs from the URL and sends events when a defined action happens. Pixel tracking is therefore the typical form of client-side tracking.

Why does a tracking pixel matter?

For many advertisers, the pixel is the foundation of conversion tracking. Without events the platform cannot tell which ads work and cannot optimise for purchases or leads. Retargeting audiences are built on pixel data too.

Limits of browser pixels

  • Ad blockers know the platforms' domains and block the script.
  • Intelligent Tracking Prevention in Safari shortens the lifetime of script-set cookies to 7 days.
  • Consent: in the EU the pixel should not load until the visitor agrees in the cookie banner.
  • Setup errors: duplicate or misconfigured pixels distort your numbers.

The result is signal loss. That is why pixels are now usually paired with a server API like the Conversions API, with deduplication keeping conversions from being counted twice. The article pixel vs. Conversion API compares both approaches.

Example

You run an online store. The pixel reports ViewContent on product pages, InitiateCheckout when checkout starts and Purchase on the order confirmation, each with the order value. Meta learns which ads drive revenue and can re-engage people who abandoned their cart.

Tracking pixels with LeadSignal

With LeadSignal you do not install pixels one by one. You connect Meta, Google Ads, LinkedIn and TikTok in the app, and the LeadSignal script loads the right pixels automatically, but only after consent. For Meta, LinkedIn and TikTok you can also switch on server-side delivery. See all supported platforms on the integrations page.

Frequently asked questions

Why is it called a pixel?+

Originally a tracking pixel really was an invisible 1x1 image. Loading the image triggered a request to the platform's server. Today it is usually a JavaScript tag, but the name stuck.

Do I still need the Meta Pixel if I use the Conversions API?+

Meta recommends running both. The pixel provides browser context, while the Conversions API catches events lost in the browser. A shared event ID removes duplicates.

Can I load tracking pixels without consent?+

In the EU, generally not. Marketing pixels set cookies and transfer user data, so you need consent through a cookie banner first.

Guides on this topic

Articles on this topic

Related terms