Definition
A tracking pixel is a script supplied by an advertising platform and run in the visitor's browser on the advertiser's website. When it loads, it identifies the site to the platform and sends events: a page view by default, plus whichever actions the advertiser has chosen to report. The platform matches those events to people who saw or clicked its ads, which is how it counts conversions and decides whom to show ads to next.
The name is historical. Early versions loaded an invisible image one pixel in size, and the request for that image carried the information. Modern pixels are JavaScript tags that send structured events, though the old name stuck. Meta's help centre describes the Meta Pixel and TikTok's describes the TikTok Pixel; a site that advertises on several platforms runs several pixels, each reporting to its own owner.
Standard events, custom events and parameters
A pixel's value lies in the events it sends, not in the base code. Platforms publish a fixed list of standard events, such as viewing a product, adding to cart, starting checkout, purchasing and submitting a lead. Delivery systems can optimise towards standard events without further setup, which is why the platforms recommend them wherever one fits. Custom events cover actions the standard list does not, at the cost of extra configuration before a campaign can use them.
Parameters travel with each event and make it useful. A purchase needs its value and currency for any return on spend figure; commerce events need product identifiers so that catalogue ads can match what was viewed to what is shown. The Meta pixel setup tutorial walks through the parameters that matter and why they should be read from structured page data rather than from page text, and the TikTok pixel and Events API tutorial does the same for TikTok's event names, which must be spelt exactly as documented or they are treated as custom.
In practice
Most pixels are installed through a tag manager rather than pasted into page templates. The base code becomes one tag that fires on every page, each event becomes another tag with its own trigger, and values come from a Data LayerA structured object on a web page that passes values to a tag manager for tags to use. that the shop or form platform fills. Installing this way makes the pixel testable and reversible, and puts it behind the same consent rules as every other tag.
Testing happens before anything is trusted. Each platform offers a test view or browser extension that shows the events arriving, their names and their parameters. The routine check is to walk the real journey once and confirm that every event fires once, at the right moment, with the right values. The Meta measurement hub explains why the event chosen for optimisation shapes everything delivery does afterwards, and the Meta Ads account audit checklist treats a clean, deduplicated event setup as a precondition for judging any campaign.
Pixels also build audiences. Visitors and purchasers recorded by the pixel become website audiences for retargeting and exclusion, as the custom audiences guide describes, so a pixel gap is also a targeting gap.
Limits: blockers, consent and the server-side pair
Everything a pixel reports depends on the browser running it. Content blockers stop some scripts from loading; browser privacy features shorten how long identifiers last; visitors who decline consent should not be tracked at all where consent is required. Each of these removes events the platform would otherwise have seen, and the loss is uneven across devices and markets.
The platforms' answer is to send the same events from the advertiser's server as well. Meta calls its version the Conversions APIServer-side event sharing with Meta., and TikTok calls its version the Events API. The server route recovers events the browser lost, but it creates a new risk: the same action can arrive twice. A shared event identifier on both copies lets the platform count it once, which is the job of DeduplicationRemoving double counts when one conversion is reported by more than one source.. The Conversions API guide covers that pairing; neither route replaces the need for consent.
A supplement shop's sales double overnight
Sandhill Sports Nutrition installs its pixel's purchase event on the order confirmation page, with the trigger set to every view of that page. Over one fortnight the ad platform reports 486 purchases against 251 orders in the shop. The test view shows why: customers reload the confirmation page or return to it from the emailed receipt, and each view sends another purchase. The developer moves the event to a data layer message the shop sends once per completed order and adds the order number as the event ID, ready for a server connection later. The next fortnight the platform reports 263 purchases against 258 orders, and the cost per purchase the team had been celebrating rises to its true level.
Related terms
The Conversions APIServer-side event sharing with Meta. is the server-side partner to the pixel, and DeduplicationRemoving double counts when one conversion is reported by more than one source. is what stops the two from counting one action twice. A Custom AudienceAn ad audience built from the advertiser's own sources: customer lists, site visitors or engagers. built from website visitors exists only because a pixel recorded them. The Data LayerA structured object on a web page that passes values to a tag manager for tags to use. is the structured source from which a well-built pixel reads order values, currencies and product identifiers.
Common confusions
- A pixel is not analytics. It reports to one ad platform for that platform's purposes; it does not replace a site's own analytics or order records.
- Installed is not working. A base code that loads proves nothing about whether purchase events fire once, with the right value.
- One pixel per platform, not one per campaign. Pixels belong to the website and outlive campaigns and agencies.
- Server events do not make the pixel redundant. The two are designed to run together, joined by event IDs.
