The essentials
- Definition: the Meta pixel is a fragment of JavaScript code placed on a site that records visits and actions (page view, add to cart, form, purchase) and sends them to Meta, linked where possible to a Facebook or Instagram user.
- Three uses: measuring campaign conversions, optimising delivery towards the people likely to convert, building remarketing audiences and sources for lookalikes.
- Essential complement: the conversions API (CAPI), which sends the same events from the server and recovers 10 to 30% of the conversions lost to browsers and consent.
- 2026 : renamed “dataset” in Events Manager; subject to consent in Europe.
The aim of Meta pixel, long known as the Facebook pixel, is the measurement device for advertising on Facebook and Instagram. Without it, a campaign delivers blind: no conversion measured, no optimisation possible, no retargeting audience. With it, but without its server-side complement, a share of conversions escapes. This article defines the pixel, what it collects, its three uses in advertising, the role of the conversions API and the effect of consent. The detailed installation procedure is in installing and configuring the Meta pixel.
What the pixel collects
| Data | Detail | Use |
|---|---|---|
| PageView event | Every page loaded, with the URL | Visitor audiences, measurement of campaign traffic |
| Standard events | ViewContent, AddToCart, InitiateCheckout, Purchase, Lead, CompleteRegistration, Contact, Schedule, Search… | Conversions and optimisation; these are the events campaigns can target |
| Parameters | Value, currency, product identifiers, content, category | ROAS, catalogue and dynamic retargeting |
| Matching data | Meta cookie if the user is logged in and has consented, click identifier (fbclid), and, via advanced matching, hashed email or phone number | Linking the action to a profile for attribution and audiences |
| Technical context | Browser, device, referrer | Diagnosis |
The pixel does not “see” the identity of a visitor who is not logged in or who has refused cookies; it then records an event that is barely or not at all attributable, hence the measurement losses.
The three uses in advertising
- Measure: attribute conversions (purchases, leads) to campaigns, ad sets and ads, with Meta's attribution windows (7 days after click, 1 day after view by default). Without a pixel, the report shows only clicks.
- Optimise: choose a conversion event as the ad set objective; the algorithm then delivers to the people most likely to complete it. It needs around 50 events per week per ad set to learn; see social ads objectives.
- Build audiences: page visitors, people who completed an event (abandoned carts, buyers), for remarketing and as a source for lookalike audiences; see retargeting on social media.
Why the conversions API has become essential
| Loss | Cause | What the conversions API changes |
|---|---|---|
| Ad blockers | The pixel script is not loaded | The event leaves from the server, outside the browser |
| Safari, iOS, Firefox | Cookies limited to 7 days or blocked, App Tracking Transparency | Matching on hashed email or phone number, sent server-side |
| Consent refused | The pixel doesn't fire | The API also respects consent; it does not bypass a refusal, but it makes what is allowed more reliable |
| Slow pages, drop-offs | The event does not have time to leave | The server sends it afterwards |
Meta recommends the hybrid setup: browser pixel and conversions API sending the same events with a common identifier for deduplication. Advertisers who switch it on see 10 to 30% more conversions measured and a better match quality score, so a lower cost per result. Native integrations (Shopify, WooCommerce, PrestaShop) or the gateway hosted by Meta make the setup accessible without a developer.
Consent and the legal framework
- The pixel drops cookies for advertising purposes: prior consent is mandatory in Europe (GDPR, French regulator guidance). No event before agreement.
- Deployment via Google Tag Manager with a consent condition (
ad_storagegranted) is the standard method; see Consent Mode v2 for the mechanism. - Declaration in the privacy policy: purposes, recipient (Meta), duration, rights.
- No sensitive data (health, religion, orientation) in events; Meta filters them and may block.
- Consent rate in France: 60 to 80% on well-designed sites; audiences and measured conversions are therefore structurally incomplete, which Meta's modelling partly compensates for.
Checking your pixel
- Meta Pixel Helper (Chrome extension): a single pixel per page, the expected events, no warning.
- Events Manager: Test events tab, diagnostics, browser and server deduplication.
- Match quality score per event: above 6 out of 10, the matching is sound.
- Consistency with GA4: Meta purchases or leads and GA4 key events should be of the same order (a 10 to 20% gap is normal); see conversion tracking in SMA.
The limits
- The pixel only measures what happens on the site; sales in store or by phone go through offline conversions or the CRM.
- Meta attribution is generous (1-day post-view) and differs from GA4; use GA4 or the CRM to arbitrate between channels.
- Custom events are not used for optimisation; favour the standard ones.
- A badly deployed pixel (duplicates, Lead on a button click, with no value) produces false data that misleads the algorithm for months.
How GreenRed helps
Rather than juggling several tools, GreenRed's social media tracking brings these metrics together in a single dashboard, compares them over time and tells you which actions come first. You can try it free, with no card, from the Pricing.
Frequently asked questions
Is the Facebook pixel still called that?
No: Meta has called it the “Meta pixel” since 2021 and, in Events Manager, a “dataset” since 2023-2024, in order to group web (pixel), server (conversions API), app and offline events under a single identifier. The code and how it works are the same.
Is the Meta pixel legal in France?
Yes, provided you obtain the user's consent before any firing (advertising cookies), state it in the privacy policy and transmit no sensitive data. Deployment via Google Tag Manager with a consent condition is the recommended practice.
Do you need the conversions API as well as the pixel?
Yes: blockers, Safari and iOS, consent refusals and drop-offs make the pixel alone lose 10 to 30% of conversions. The conversions API sends events from the server, with deduplication; the native integrations of e-commerce CMSs and the Meta gateway make the setup accessible without a developer.
How many events are needed for campaigns to optimise?
Around 50 conversion events per week per ad set to leave the learning phase. If your final event (purchase, lead) is rarer, optimise temporarily on a more frequent event in the funnel (add to cart, checkout initiated), then move back up.