Glossary entry

What is a Tracking Pixel?

A tracking pixel is a tiny invisible image (or script) loaded on your site that signals an event back to an ad platform. It's how Meta, TikTok, Google, and others know who visited, who converted, and how to optimize. Modern best practice pairs every pixel with a server-side Conversion API.

How pixels work

When a user lands on your page, the pixel fires and tells the platform: who, what page, what action. The platform uses that to attribute conversions, build remarketing audiences, and train its bidding algorithm. Without it, the algorithm is bidding blind.

Pixel vs. Conversion API

Pixels run client-side and are blocked by ad blockers, ITP, and iOS 14 opt-outs. Conversion APIs run server-side and bypass all three. Use both: pixel for immediate signals, CAPI for completeness.

Common pixel mistakes

Firing the pixel on every page (events become noise), missing the conversion event on the right page, double-firing on cart confirmations, and not deduplicating events between pixel and CAPI.

How Unled Network helps

Managed Campaigns includes pixel + CAPI implementation, deduplication, and event taxonomy. We rebuild broken tracking before changing a single bid.

Frequently asked

Do I need a pixel for every platform?

Yes - Meta Pixel, TikTok Pixel, Google Tag, LinkedIn Insight, etc. They don't share data.

Where do I put the pixel?

Sitewide base code in . Event-specific code on conversion pages.

Are pixels GDPR compliant?

Only with valid consent. Use a CMP (consent management platform) and fire conditionally.

Pixel or Conversion API?

Both, deduplicated. Pixel alone is increasingly broken on iOS.