A tracking pixel is a tiny, usually invisible piece of code — historically a 1x1 image, now more often a JavaScript snippet — placed on a web page or in an email that fires a request to a server when the page or message is loaded.
Definition
A tracking pixel is a tiny, usually invisible piece of code — historically a 1x1 image, now more often a JavaScript snippet — placed on a web page or in an email that fires a request to a server when the page or message is loaded. That request tells the server the page was viewed, from what device and IP, and can carry additional data such as a page identifier or a conversion value.
Ad platforms use pixels to record conversions on an advertiser's site and to build audiences.
The pixel is the browser-side counterpart to a server-to-server postback. Where a postback is a direct server call that does not depend on the user's browser, a pixel runs in the browser and is therefore vulnerable to ad blockers, tracking-prevention features, cookie restrictions and script failures.
Modern setups often use both: a pixel for audience building and platform optimisation, and a postback for reliable conversion attribution.
In context
For iGaming acquisition, the pixel's main job is feeding the ad platform's optimisation model: when a pixel fires on a first deposit, the platform learns which impressions preceded it and bids toward similar users. Sending the right event (a qualified deposit, not a raw registration) and a value (deposit tier or predicted LTV) makes the model chase better players.
On iOS, App Tracking Transparency and browser tracking prevention have degraded pixel reliability, so operators increasingly rely on server-side event delivery (a conversions API) that sends the same events from their backend, with the pixel as a supplementary signal.
Pixel hygiene matters. A double-firing pixel inflates conversions; a pixel that fires on page load rather than on the actual conversion event mislabels traffic; a pixel with no deduplication against the server-side event double-counts.
Affiliates and operators test pixels the way they test postbacks — trigger a real conversion, confirm exactly one event arrives with the correct value — before trusting the data or letting an algorithm optimise against it. Privacy law also applies: pixels that set cookies or collect data need a lawful basis and, in many markets, prior consent.
Worked example
An operator finds its optimisation is chasing cheap minimum deposits. The pixel was firing a generic "deposit" event with no value.
It updates the pixel and its server-side conversions API to send the deposit amount as the event value, deduplicated by a shared event ID, and within two weeks the algorithm shifts spend toward higher-value players.
Related terms
Frequently asked questions
Browse the full iGaming & affiliate glossary — hundreds of EN/RU terms with examples.
← Back to glossary