Definition
Meta Pixel
A JavaScript snippet on your website that records visits and actions such as leads and purchases and sends them to Meta for measurement and ad optimization.
The Meta Pixel loads a small library of functions on the page. By default it records page URLs, domains and device information, and you call fbq('track', ...) to send standard events such as Lead or Purchase, or custom events. Meta uses this to measure conversions, build audiences and optimize campaigns.
Because it runs in the browser, the Pixel can be blocked or limited by ad blockers, browser privacy features and consent choices. Meta's answer is to pair it with the Conversions API and deduplicate the two streams.
Common problems: the base code installed twice (once in the theme and once in Tag Manager), events firing on button clicks rather than confirmed submissions, and events that stop after a site rebuild because the trigger relied on a CSS class or URL that changed.
Related terms
- Meta Conversions API (CAPI)
- Meta's server-to-server connection for sending web, app, offline and messaging events from your server or CRM directly to a Meta dataset.
- event_id and deduplication
- Meta drops a duplicate when a Pixel event and a Conversions API event share the same event name and event ID and arrive within 48 hours of each other.
- fbp and fbc
- Meta's first-party browser ID (
_fbp) and click ID (_fbc) cookies; passing both to the Conversions API, unhashed, helps match server events to ad clicks. - Data layer (dataLayer)
- A JavaScript array that the site pushes events and values into so Google Tag Manager and gtag.js can read them, instead of scraping the page.
Sources
Checked against the official documentation in November 2026. Platforms change; check the source for current details.