What is a Pixel?

"Pixel" gets thrown around constantly in advertising (Meta Pixel, Google Ads pixel, conversion pixel), but most explanations stop at "it tracks stuff." A pixel is simply a small piece of code placed on a website that sends a signal back to an ad platform when something specific happens: a page loading, a purchase completing, or a form being filled.

That is the basic mechanic, and it is usually where the conversation ends.

More than once, I've run a conversion campaign that looked like it was underperforming, only to find out later the campaign was fine and the tracking was not. Nobody starts with "let's check the tracking." Everyone starts with "let's fix the targeting." Half the time, targeting was never the problem.

A broken pixel is like driving with a faulty speedometer

You're still moving. The car still works. But you have no real idea if you're going 40 or 90, and every decision you make about when to brake or accelerate is based on a number that might be quietly wrong.
That's what a broken or thin pixel does to a campaign. Everything downstream still runs. Spend goes out and ads deliver, but the decisions being made off the reporting are only as good as a signal that might not reflect reality.

Why it breaks, and why nobody notices at first

Website redesigns, plugin updates, and browser privacy changes can all break a pixel without anyone touching the ad account. The event stops firing or fires on the wrong trigger, and the only sign is usually a conversion number that looks a bit off. Meta, Google, and TikTok often model in an estimate when a direct signal is missing, which softens the drop and makes the problem even easier to miss.

Programmatic advertising doesn't have that cushion. The pixel is the actual signal the algorithm bids against in real time, whether that's a display campaign or something running through a platform like Krypton. A broken pixel doesn't just misreport what happened; it pushes budget towards the wrong audiences while going completely unnoticed. In my experience, this is where the real money gets lost. It is not in the reporting, but in the decisions the algorithm quietly keeps making off bad information.

Even when the pixel works, tracking is trickier than it looks

A working pixel isn't the end of the story. There are a few inherent gaps built into tracking itself that catch people off guard:

• Cross-Device Gaps: Someone scrolls past an ad on their phone, does nothing, and converts on a laptop two days later. A pixel on its own can't always connect those moments because it's tied to a browser or device, not a person. Platforms bridge this either through logged in user accounts or less exact methods like IP addresses and device IDs. Without those bridges, the conversion shows up as disconnected, and the mobile ad gets zero credit.
• Multi-Touch Attribution: One pixel event doesn't automatically give one ad full credit. Someone might see a programmatic display ad, then a Meta ad, then a Google ad before converting. Attribution models decide how credit gets split across those touchpoints. Whether a model uses last click or multi-touch fundamentally changes how successful any single platform looks.
• Signal Degradation: First-party pixels are controlled directly by the website owner, while third-party pixels belong to the ad platforms. Browser restrictions and updates like Apple's App Tracking Transparency have noticeably weakened third-party signals over the last few years. This is why platforms are pushing heavily towards first-party data and server-side options to own more of the signal directly.

None of that means give up on tracking. It means build it properly.

Most setups stop at page load, add to cart, and purchase. But a well-built pixel can capture product views, category views, on-site searches, sign-ups, newsletter subscriptions, video views, scroll depth, and form abandons. Each event marks a distinct level of user intent.

On top of each event sits granular detail:

• Purchase value and currency
• Product ID and category
• Quantity
• New versus returning customer status

The event tells you something happened. The detail tells you what actually happened, and that's the part most accounts skip.

Passing revenue, not just a conversion flag

A pixel that only fires "purchase" tells you someone bought something. It doesn't tell you if that sale was worth $5 or $500. Passing actual value changes everything you can do with the data:

• Smarter Bidding: Value-based bidding, true ROAS, and dynamic CPA are built on actual revenue numbers.
• Better Lookalikes: Instead of modelling seed audiences off everyone who bought something, you can model strictly off your highest value buyers.

Without value attached, every sale looks identical to the platform, flattening the exact signal worth optimising towards.

Why extra detail actually matters

Every event you track creates a distinct group of people you can act on:

• Category Viewers: Retarget with broader, category-level messaging.
• Repeat Product Viewers: Retarget aggressively with high-intent, specific messaging.
• Recent Buyers: Exclude from retargeting so you stop wasting ad spend on completed conversions.
• High-Value Buyers: Use as the seed audience for high-performing lookalikes.

More detail simply means better groups to retarget, exclude, or build lookalikes from.

Google Tag Manager ties it all together

In practice, pixels for Meta, Google, TikTok, and programmatic platforms are rarely managed individually on a website. They sit inside Google Tag Manager (GTM), a container tool holding every tag a site needs. Instead of a developer manually pasting separate tracking codes across pages, GTM holds them in one central place, firing tags based on standardised triggers.

Even with central management in GTM, each platform's tag behaves differently and needs individual testing. A tag firing correctly for Meta doesn't guarantee Google or TikTok is set up properly.

What brands actually need on their end

For any of this to work, a few technical prerequisites must be met on the website side:

• Consistent Product and Item IDs: Ensures revenue values and product details pass back to the pixel seamlessly.
• Upfront Event Planning: Key events must be planned before site development starts, not bolted on as an afterthought.
• Direct GTM Access for Marketers: Media managers need direct access to GTM rather than relying on developers for minor tag fixes.

Without these, dynamic product ads and reliable revenue reporting are impossible, regardless of how well the ad account is managed. Tracking is a website conversation before it's an ad campaign conversation.

Where this all ties together

The events, parameters, revenue data, and site structure all feed the same engine: the signal that programmatic systems, including the ones we run through Krypton, bid against in real time.

A better signal doesn't just mean prettier reports; it means the algorithm is actively chasing the right business outcomes instead of a distorted metric. A pixel is a tiny piece of code, but very little downstream works properly without getting it right first.