Meta Pixel

The Meta Pixel is a JavaScript snippet you place on your website to track activity from people who arrive from Meta ads. You get the base code from Events Manager. It contains your Pixel ID in a script block and a noscript image fallback. Meta says to place it between the head tags on every page you want to track, ideally in a site-wide header. Each time the base code runs it fires a PageView event automatically, and Meta tells you to leave that call intact. The Pixel ID is the thing that ties the code to your data set in Events Manager. If you run the Pixel through a plugin or a tag manager, the ID is entered in a settings field and the plugin writes the base code for you.

Beyond page views, you add standard events with a call like fbq('track', 'Purchase', {currency: 'USD', value: 30.00}). Standard events are predefined actions, such as Purchase, Search, InitiateCheckout, and CompleteRegistration. Custom events use trackCustom, and their names must be strings no longer than 50 characters. The value parameter is required for purchase events and for anything that uses value optimization, and it needs a matching currency. Meta uses Facebook cookies to match visitors to accounts, and the Pixel stores a first-party _fbp browser ID when first-party cookies are in use. Standard events carry parameters that make them useful. A Purchase with a value and currency lets Meta optimize toward revenue, and a Lead with no parameters can only be counted. Add the fields you will want to report on, not just the event.

The Pixel connects to the rest of your Meta setup in three ways. It feeds website custom audiences, so you can retarget visitors. It gives delivery events to optimize toward when you choose a conversion objective. And it supports custom conversions, which you create in Events Manager from rules like a URL containing thank-you, up to 100 per ad account. Because it runs in the browser, it is exposed to ad blockers, tracking prevention, and consent refusals, so many teams pair it with the Conversions API using a shared event_id. Custom conversions are a lighter-weight option for sites you cannot edit. They use a rule such as a URL containing a word, so a thank-you page can be counted without extra code, though a coded event is more precise.

Common mistakes: installing the base code but never adding purchase or lead events, so Meta can only optimize toward page views. Firing the Purchase event on page load of a page people can revisit. Leaving out value and currency. Using lowercase or misspelled standard event names, which turn into custom events. Installing the Pixel twice, through a plugin and by hand, which doubles events. On a site built with a tag manager, forgetting that a Pixel pasted separately into the theme also fires. Pixel installs often go wrong after a redesign. A new theme drops the header snippet, or a checkout app moves the thank-you page to another domain, and events quietly stop. Compare event counts weekly against real orders.

To check it, load a page with the Pixel and look for a new PageView in Events Manager, waiting a few minutes if it is missing. Meta also points to its Meta Ads Data Advisor Chrome extension for diagnosing problems. This week, open Events Manager, confirm your most important event (Purchase or Lead) is firing once per real conversion with a value, and compare its count with your store or CRM. A large gap means signal loss that the Conversions API can help recover. When counts look low, check browser, consent, and tag settings first. Meta's debugging extension and the test events tool in Events Manager show whether the browser is sending what you think it is.