Definition:
Meta Pixel, formerly known as Facebook Pixel, is a JavaScript tag that records actions performed on a website and sends those events to Meta. It is used to measure advertising results, attribute conversions, create audiences and provide signals for campaign optimisation across Meta’s advertising platforms.
Unlike a traditional tracking pixel, it does not simply load a transparent 1 x 1 pixel image. Its base code runs in the browser and can record a page visit, a purchase, a form submission or another interaction defined in the implementation.
The available data depends on the event, its parameters, the website configuration, applicable consent and browser or device restrictions. Meta Pixel therefore provides information for advertising measurement, but it is not by itself a complete record of all activity on a website.
Table of contents
How Meta Pixel works
When a person opens a page containing the tag, the browser loads the code and may send an event to Meta. The event identifies the observed action and may include parameters that describe its context, such as the value and currency of a purchase or a product identifier.
The base code commonly records PageView. Events for other actions are then added to that foundation. Depending on the configuration and available permissions, Meta may use the received signals to connect website activity with campaigns, build remarketing audiences or help its advertising system find people who are more likely to complete an action.
A received event does not automatically become a conversion attributed to an ad. Attribution depends on the applicable rules and windows, the match Meta can establish and the quality of the submitted data.
Installation and configuration
Meta Pixel can be added through an integration with the website platform, a tag manager or a manual installation. Each method uses a pixel identifier associated with the corresponding data source in Events Manager.
A basic implementation contains several parts:
- Base code: loads Meta’s library and enables pages containing it to send events.
- Events: describe relevant actions through either Meta’s standard events or custom events.
- Parameters: add context to an event, such as content, category, value or currency where appropriate.
- Conversion rules: classify specific events or visits that meet defined conditions as conversions.
The installation should be checked in Events Manager, where test events, received activity and configuration diagnostics can be reviewed. The Meta Pixel documentation describes the current setup options.
Standard and custom events
Standard events use names and parameters recognised by Meta. Common examples include ViewContent, Search, AddToCart, InitiateCheckout, Purchase, Lead, CompleteRegistration and Contact. The selected event should describe the action that actually occurs on the website.
A custom event uses a defined name for an interaction that is not accurately represented by a standard event. It may then support analysis or a custom conversion, provided the configuration complies with Meta’s policies.
Custom conversions can also be defined with rules based on URLs, events or parameters. This does not replace a correct implementation: a rule can only classify information that the website already sends.
Meta Pixel and Conversions API
The Conversions API is not a form of the pixel and does not run JavaScript in the browser. It is a separate method for sending events from a server, commerce platform or another connected source to Meta. It can complement Meta Pixel and reduce exclusive reliance on the browser, but it does not remove consent, transparency or data protection obligations.
The same action may be sent from both the browser and the server. In that case, the two copies need consistent identifiers so Meta can deduplicate them. This commonly involves sharing the event name and a unique identifier, preventing one purchase or lead from being counted twice.
Meta Pixel and Conversions API can coexist because they observe and transmit signals from different environments. Combining them can improve measurement continuity in some situations, although the result still depends on implementation quality and Meta’s ability to match the events.
Advertising uses
The recorded information can support several advertising functions:
- Measurement: connect website events with campaigns and analyse results in Meta’s tools.
- Optimisation: use the selected event as a signal that helps the system adjust ad delivery.
- Remarketing: build audiences from visits or actions, subject to configuration and eligibility requirements.
- Lookalike audiences: use a source audience to find profiles with similar characteristics when this feature is available.
These functions do not guarantee more sales or exact attribution. Results should be interpreted alongside campaign settings, event quality and other measurement sources.
Privacy and measurement limits
Meta Pixel may process identifiers and interaction data. Its use requires organisations to define what information is sent, avoid prohibited data and apply the consent and transparency mechanisms required in each context.
Measurement may be affected by blockers, cookie restrictions, browsers, connectivity, tagging errors and consent choices. Duplicate events, incomplete parameters or actions triggered at the wrong time may also occur. Each event’s actual journey should therefore be tested and diagnostics reviewed regularly, because the mere presence of the code does not demonstrate accurate measurement.