Tracking Pixel
A tracking pixel is a small piece of code that an advertising or analytics platform gives you to place on your website. When a page loads or a visitor does something, the pixel sends a report back to the platform. That report is how the platform knows an ad led to a sale, a lead, or a signup.
What is a tracking pixel?
The name comes from how it used to work. Early tracking pixels were literally a one-pixel by one-pixel transparent image. The image was hosted on the ad platform's server, so every time a browser loaded it, the platform got a request it could count. Nobody saw the image, but the platform saw the visit.
Today most "pixels" are short JavaScript snippets, not images. The Meta Pixel, the TikTok Pixel and the LinkedIn Insight Tag are all JavaScript. The name stuck anyway, so ad platforms still call the code a pixel and searchers still type "pixel" when they want to set one up.
Some platforms call the same thing a tag instead. Google calls it the Google tag, Microsoft calls it the UET tag, Pinterest calls it the Pinterest Tag. They all do the same job.
How a tracking pixel works
Every tracking pixel has two separate jobs.
First, it loads on every page and records a page view. Platforms call this the base code. It tells the platform someone visited, and it usually sets a cookie so the platform can recognize that browser later.
Second, it fires events when something happens. A form is submitted, an order is placed, an account is created. These are the events the ad platform actually cares about, because they are the conversions it is trying to get more of. The base pixel does not know when these things happen on its own. Something on your site has to tell it.
That second part is where most setups fall short. Installing the base code takes a minute. Getting the right event to fire, with the right value, at the right moment, from the plugin you actually use, is the real work.
Tracking pixels by ad platform
Each platform has its own pixel. The names differ, the job is the same.
| Platform | Pixel name | Also has a server-side option |
|---|---|---|
| Meta Ads | Meta Pixel (formerly the Facebook Pixel) | Yes, the Conversions API |
| Google Ads | Google tag (gtag.js) with a conversion tag | |
| TikTok Ads | TikTok Pixel | |
| LinkedIn Ads | LinkedIn Insight Tag | |
| Microsoft Ads | UET tag (Universal Event Tracking) | |
| Pinterest Ads | Pinterest Tag | Yes, the Conversions API |
| Snapchat Ads | Snap Pixel | Yes, the Conversions API |
| Reddit Ads | Reddit Pixel | Yes, the Conversions API |
| X Ads | X Pixel (formerly the Twitter pixel) | |
| OpenAI Ads | OpenAI Ads pixel | Yes, the Conversions API |
Analytics platforms use the same idea. A Google Analytics tag, a Plausible script or a Fathom script is a tracking pixel in everything but name.
Tracking pixel vs cookie
People mix these up because they usually show up together.
A pixel is code that runs and sends data. A cookie is a small file the pixel leaves behind in the browser so the platform can recognize the same visitor next time. The pixel does the reporting, and the cookie does the remembering.
You can have a pixel without a cookie. Some privacy-focused analytics tools work that way. You cannot have an ad platform cookie without something like a pixel to set it.
Tracking pixel vs conversions API
A pixel runs in the visitor's browser, and that is its weakness. Ad blockers, browser privacy settings and slow page loads can all stop it from firing, so the ad platform misses conversions that really happened.
A conversions API sends the same event from your web server directly to the platform, with no browser in the middle. Meta, Pinterest, Snapchat, Reddit and OpenAI Ads each offer one. Most sites run both, the pixel and the API, and use an event ID so the platform can deduplicate the two copies.
The plain-language guide to conversions APIs covers when the server-side option is worth turning on.
Tracking pixels and consent
A tracking pixel that sets a cookie and reports behavior to an ad platform counts as marketing tracking. In most privacy laws it needs consent before it runs. In practice that means the pixel should not load, or should not send events, until the visitor has accepted marketing cookiesA small piece of data stored in a user’s browser that helps websites remember user activity, preferences, or sessions across visits. in your consent banner.
How Conversion Bridge helps
Conversion Bridge adds the pixel for every ad platform you connect and, more importantly, fires the events those pixels need. When a visitor submits a form, buys something, joins a membership or makes a donation through one of the 71 supported WordPress plugins, the matching event goes to every connected pixel at once. Purchase to Meta, TikTok and Google Ads together, with the order value attached.
For platforms that offer a conversions API, Conversion Bridge can send the same event server-side with a shared event ID so nothing gets counted twice. It hashes customer details like email and phone before sending them, which raises match rates and scores like Meta's Event Match Quality. And when a supported consent banner is active, pixel events wait for marketing consent before they fire.
Frequently Asked Questions
Is a tracking pixel the same as a tag? Yes, they are two names for the same kind of code. Meta and TikTok say pixel, while Google, Microsoft and Pinterest say tag.
Do I need a pixel if I use a conversions API? Most platforms recommend that you run both. The pixel gives the platform browser signals it cannot get from the server, and the API catches conversions the pixel misses. DeduplicationDeduplication prevents the same conversion from being counted twice. It keeps your data accurate and is handled automatically by Conversion Bridge. keeps them from double counting.
Can I run more than one pixel on a WordPress site? Yes, and most sites advertising in more than one place do. A site advertising on Meta and Google Ads runs both pixels, and each needs its own conversion events. Conversion Bridge fires one detected conversion to every connected platform, so you set the event up once.
Does a tracking pixel slow down my site? A little, but less than you might think. Each pixel is another script the browser downloads. The bigger cost is usually not the base pixel but the extra tag manager and custom code people add to make events fire. Firing events from the plugin directly avoids most of that.