The Meta Pixel is a snippet of JavaScript that a website owner places on its pages so that visits and actions, such as a product view, a sign-up or a purchase, are reported to Meta Platforms. Meta uses those reports for three jobs: measuring which Facebook and Instagram ads led to a sale, telling its delivery system which people are likely to convert, and building audiences for retargeting. It exists because an advertiser selling on its own website has no other way to tell Meta what happened after someone clicked or saw an ad. Until the company renamed itself in October 2021, the same tag was called the Facebook Pixel, and that name persists in code, cookies and court filings.

How the tag works

Installation starts in Events Manager, the Meta interface where an advertiser creates a pixel and receives a numeric pixel ID. The base code defines a global function, fbq, and asynchronously loads a library, fbevents.js, from connect.facebook.net. Two calls follow: fbq('init') with the pixel ID, and fbq('track', 'PageView'), which fires on every page load. A noscript block holds a hidden 1x1 image pointing at facebook.com/tr, the collection endpoint, for browsers with JavaScript switched off. By default, according to Meta's developer documentation, the pixel records the URLs and domains visited and the visitor's device.

Everything beyond a page view is an event. Meta defines 17 standard events, among them ViewContent, AddToCart, InitiateCheckout, Lead, CompleteRegistration and Purchase. Each accepts parameters: content_ids, contents, num_items, value and currency. Purchase is the only event for which value and currency are mandatory. Advertisers may also send custom events with names of their own choosing, or define custom conversions, rules that treat a URL pattern as a conversion without extra code.

Identification relies on cookies. When first-party mode is on, the pixel writes _fbp on the advertiser's domain, a value such as fb.1.1596403881668.1116446470 combining a subdomain index, a creation time in milliseconds and a random number. When a visitor arrives from an ad, the fbclid click identifier in the URL is stored in a second cookie, _fbc, which Meta suggests keeping for 90 days. A visitor logged in to Facebook in the same browser may also send Meta's own cookies, c_user and fr, which tie the hit to an account.

Advanced matching adds personal data to improve match rates. The tag can pass email, phone, first and last name, city, state, postcode, country and an advertiser's own external_id; the JavaScript library hashes these values with SHA-256 before sending them. A manual version passes the fields in the init call; an automatic version, enabled in Events Manager, reads them from form fields.

Consider an online shoe retailer. A shopper clicks an Instagram ad, lands on a product page carrying fbclid, adds a pair to the basket and pays 89 euros. The pixel fires PageView, ViewContent, AddToCart and finally Purchase with value 89 and currency EUR. Meta matches the hit to the account that clicked, credits the ad if the purchase falls inside the ad set's attribution window, typically one or seven days after a click, and feeds the outcome into bidding for similar shoppers.

Server-side partner

Browsers increasingly block the requests a pixel makes. Meta's answer is the Conversions API, which sends the same events from the advertiser's server. Meta recommends running both, so a purchase can arrive twice; it discards the duplicate when event_name and event_id match within 48 hours. Events Manager now groups browser and server events for one property in a dataset.

Operators on the buy side are the advertiser, its agency and often a tag management or e-commerce platform such as Shopify or WooCommerce. On the sell side sits Meta alone: unlike a programmatic tag, the pixel serves a single, closed buying system.

Origin and evolution

Before 2015 Facebook ran two separate tags, a conversion tracking pixel and a Custom Audience pixel. On October 14, 2015, a post on Facebook's developer blog by Cecile Ho announced a unified Facebook pixel with nine standard events and custom conversions, and said support for the old conversion pixel would end in the second half of 2016. Meta's documentation records that the conversion tracking pixel was deprecated in February 2017.

On October 24, 2018, Facebook added a first-party cookie option, letting the tag set identifiers on the advertiser's domain as browsers restricted third-party cookies. The server pathway, first called the Server-Side API, was operating as the Conversions API by autumn 2020.

Apple's App Tracking Transparency prompt, in force from iOS 14.5 in April 2021, forced a redesign of measurement. Meta introduced Aggregated Event Measurement, which capped each domain at eight prioritised conversion events. Dave Wehner, then Meta's chief financial officer, said on February 2, 2022 that Apple's changes would cost the company "on the order of $10 billion" in revenue that year. Meta later dropped the eight-event prioritisation, according to consultant Jon Loomer, whose account of the change was last updated in March 2025.

Why it matters

The pixel is the main bridge between Meta's advertising system and the sites where sales actually happen. Meta's auction estimates the probability that a person will act, and those estimates depend on conversion signals the pixel and its server partner return. Reach is vast: BuiltWith counted the tag on more than 5.8 million websites and HTTP Archive on 2.4 million, according to figures cited in coverage of the 2025 localhost disclosure.

Signal quality has a price. Meta says advertisers with a web Conversions API set-up averaged 17.8% lower cost per result than those without one, a platform figure rather than an independent audit. An IAB survey run between July and August 2025 found that 67% of conversion API implementations operate alongside pixels. Because the pixel is one of many similar tags, it also belongs to the wider category of site tags.

Limitations and disputes

Measurement loss is the first limitation. Ad blockers, Safari's tracking prevention and cookie consent refusals all stop browser events, and attribution rules remain contested. Meta's help pages state that click-through credit counts clicks that "may include interactions such as likes, shares and saves", a detail advertisers flagged in October 2025.

Privacy is the larger dispute. In June 2022 The Markup found the pixel on 33 of Newsweek's top 100 US hospitals, sending data when visitors booked appointments, and inside seven health systems' password-protected patient portals. In November 2022 it reported tax filing services transmitting taxpayer data through the tag; a congressional report led by Senator Elizabeth Warren confirmed the finding on July 12, 2023. The US Department of Health and Human Services issued a bulletin on December 1, 2022 treating such tracking as a potential disclosure of health information, but a Texas federal court vacated the bulletin's central theory on June 20, 2024. Advocate Aurora Health settled a pixel class action for $12.25 million in July 2024.

In June 2025, researchers including Gunes Acar of Radboud University and Narseo Vallina-Rodriguez of IMDEA Networks showed that the pixel, in Android browsers, sent the _fbp cookie to local ports where Facebook and Instagram apps listened, defeating cookie clearing and incognito mode. Meta stopped the behaviour by June 3, 2025.

European courts focus on consent and joint responsibility. The Court of Justice's Fashion ID ruling of July 29, 2019 made sites embedding Facebook code joint controllers for the collection stage. On February 3, 2026, the Dresden Higher Regional Court awarded four users 1,500 euros each over Meta's Business Tools, including the pixel, finding that data reached Meta even when users refused cookies; about 10,000 similar claims were pending in Germany. The Jena court awarded 3,000 euros on March 2, 2026.

Meta's position is that its terms prohibit advertisers from sending sensitive data. Since early 2025 it has classified some data sources as health and wellness, blocking lower-funnel events such as purchases for those accounts and, under a regime called core setup, stripping URL detail and custom parameters, according to accounts by Triple Whale and Ours Privacy. Meta has not published the full criteria.

Not the same as

Conversions API. The server-to-server route for the same events. The pixel runs in the visitor's browser; the API runs on the advertiser's infrastructure.

Facebook SDK. Code compiled into mobile apps. The August 2025 Flo Health verdict, in which a jury found Meta liable under the California Invasion of Privacy Act, concerned an SDK, not the pixel.

Like button and social plugins. Embedded Facebook widgets that also transmit visitor data but exist to display social features, not to report conversions.

Google tag. A rival site tag sending events to Google's systems, built on the same principle.

Recent developments

On April 15, 2026, Meta announced AI-assisted enrichment that attaches product names, availability and business details to pixel events automatically, with a 30-day notice for existing users and an opt-out in Events Manager. A one-click, Meta-enabled Conversions API that mirrors pixel events server-side was confirmed live on April 27. IAB Tech Lab, with Meta contributors, finalised ECAPI 1.0, a common conversion API format, on May 3.

Litigation has moved to AI products. A May 13, 2026 complaint alleges the pixel sent ChatGPT conversation titles to Meta, allegations OpenAI had not answered at the time. An IMDEA study reported on October 5, 2026 found the tag collecting Grok conversation identifiers. In the US, Washington's Supreme Court is weighing whether pixel tracking on Seattle Children's Hospital's website intercepts private communications, and California's SB 690, signed on September 30, 2026, ends private pen-register claims over website tracking from January 1, 2027, while leaving wiretap claims available. Reporting has also shrunk: from January 12, 2026, Meta's Ads Insights API stopped returning seven-day and 28-day view-through data.

Timeline

  • June 10, 2015: Facebook announces an upgrade path for its existing pixels
  • October 14, 2015: Facebook announces the unified Facebook pixel, merging conversion tracking and Custom Audience pixels
  • February 2017: Facebook deprecates the conversion tracking pixel
  • October 24, 2018: First-party cookie option rolls out for the pixel
  • July 29, 2019: Court of Justice of the EU rules in Fashion ID (C-40/17) on joint controllership for embedded Facebook code
  • Autumn 2020: The Server-Side API is operating as the Conversions API
  • April 2021: iOS 14.5 enforces App Tracking Transparency; Aggregated Event Measurement rolls out
  • October 2021: Facebook Inc renames itself Meta Platforms; the tag becomes the Meta Pixel
  • February 2, 2022: Meta estimates a $10 billion 2022 revenue hit from Apple's privacy changes
  • June 2022: The Markup finds the pixel on 33 of the top 100 US hospital websites
  • November 2022: The Markup reports tax filing sites sending taxpayer data through the pixel
  • December 1, 2022: HHS publishes its online tracking technologies bulletin
  • February 2023: Conversions API gains full offline event support
  • July 12, 2023: Congressional report on tax preparers' use of the pixel
  • June 20, 2024: Federal court in Texas vacates part of the HHS tracking bulletin in AHA v. Becerra
  • July 2024: Advocate Aurora Health's $12.25 million pixel settlement receives final approval
  • Early 2025: Meta begins restricting health and wellness data sources
  • June 3, 2025: Meta stops localhost communication from the pixel on Android
  • August 4, 2025: Jury finds Meta violated CIPA in the Flo Health SDK case
  • January 12, 2026: Seven-day and 28-day view-through windows removed from the Ads Insights API
  • February 3, 2026: Dresden Higher Regional Court awards 1,500 euros each to four users over Business Tools
  • March 2, 2026: Jena Higher Regional Court awards 3,000 euros for pixel tracking without consent
  • April 15, 2026: Meta announces AI-assisted pixel enrichment and one-click Conversions API
  • May 3, 2026: IAB Tech Lab finalises ECAPI 1.0
  • May 13, 2026: Class action alleges the pixel sent ChatGPT conversation titles to Meta
  • September 30, 2026: California Governor Gavin Newsom signs SB 690
  • January 1, 2027: SB 690 takes effect

Summary

Who. Meta Platforms builds and operates the pixel. Advertisers, their agencies and e-commerce or tag management platforms install it; regulators, courts, researchers and privacy plaintiffs scrutinise it.

What. A JavaScript tag that sends page views, standard and custom events, cookies and optionally hashed personal data to Meta for conversion measurement, ad optimisation and audience building, usually paired with the server-side Conversions API.

When. Facebook unified its earlier pixels into one tag on October 14, 2015. It gained a first-party cookie option in October 2018, took the Meta name after the October 2021 rebrand and received AI-assisted enrichment in April 2026.

Where. On advertisers' websites worldwide, with data flowing to Meta's facebook.com/tr endpoint and managed through Events Manager.

Why. Meta needs off-platform conversion data to price and target ads on Facebook and Instagram. The same data flow has made the tag a focus of health privacy investigations, GDPR damages claims and US wiretap litigation.