Core concepts
What is Tracking pixel?
A snippet of code (historically a 1×1 image, now usually JavaScript) that an ad platform loads to record visits, events, and conversions in the browser.
Definition
A tracking pixel is code an ad platform places on a site to record browser-side activity — page views, add-to-carts, purchases — and tie it back to ad exposure. The Meta Pixel and TikTok Pixel are the best-known examples.
The name is historical: the original pixels were invisible 1×1 images. Modern pixels are JavaScript, but the job is the same — fire an event with parameters the platform attributes to a campaign.
Why it matters for agencies
Pixels are the browser-side half of ad attribution, and they’re increasingly unreliable on their own — ad blockers, ITP, and consent gating drop a meaningful share of firings. That’s why pixels now pair with a server-side Conversions API.
Agencies that run a pixel without its server-side counterpart are leaving attribution (and therefore optimization signal) on the table, and usually double-counting or under-counting without realizing it.
Tracking pixel in Phloz
Phloz models pixels (Meta Pixel, TikTok Pixel) as nodes, and the audit engine specifically flags a pixel with no paired Conversions API endpoint and duplicate pixels on the same client — two of the most common, most costly setup mistakes.
Frequently asked questions
- Are tracking pixels going away?
- The browser-only pixel is degrading, not disappearing. The durable pattern is pixel + Conversions API together, with deduplication so the same event isn’t counted twice.
- How many pixels should a client have?
- Per platform, exactly one. Duplicate pixels — a common artifact of agency handoffs and theme apps — inflate conversion counts and corrupt optimization. Auditing for duplicates is a standard onboarding check.
Related terms
Other tracking-infrastructure concepts agencies run into alongside this one.
14 days free · No credit card · Starter tier free forever