Tracking pixel

A tracking pixel is a snippet of code from an ad platform, such as the Meta Pixel or the LinkedIn Insight Tag, that reports what visitors do on your website back to that platform.

Reviewed by Calum Peak, CTO Last reviewed

Enquiry sent

javaroasters.co.uk/thank-you

Visitor accepted cookies

Visitor's browser Meta Pixel

Reports the enquiry

Java Roasters' server Conversions API

Can report the same enquiry

Meta

Conversions

1

Counted once

One enquiry reported by the pixel in the visitor's browser. The server route, dimmed, is a Conversions API.

What it means for your advertising

The name comes from early versions, which loaded an invisible image one pixel across. Today's pixels are short scripts, and Google calls its version the Google tag. Each reports events: a page viewed, a form sent, a purchase made.

Those events do three jobs. They count conversions (conversion tracking), they build remarketing audiences from your visitors, and they show the platform which kinds of people convert, which improves its targeting and its lookalikes.

Pixels run in the visitor's browser, so they need consent (PECR) and can be stopped by ad blockers and browser privacy settings. A Conversions API sends the same events from your server to fill the gaps.

An example

Java Roasters' site carries the Meta Pixel and the Google tag, both loaded through Google Tag Manager. When a visitor who has accepted cookies sends an office coffee enquiry, each reports a conversion to its own platform.

Java Roasters is a fictional business, and its figures are illustrative.

How we handle it

We help you add the pixels and tags your campaign needs through Google Tag Manager, set to wait for consent, and check they fire before launch. Our guide to tracking your ad enquiries walks through the setup.

Are you ready to grow your business?

No retainers. No lock-ins. Campaigns when you need them.

Book a strategy call Start in the Guru

Strategy calls run for 30 minutes — bring your business and your goal, we will do the rest.