Measurement ยท Guide 8 of 12

Meta Pixel, Conversions API and Events Manager

Meta can only optimize for actions it can see. The Meta Pixel and the Conversions API send those actions from your website or server, and Events Manager is where they are managed and checked. This is the most technical guide in the series, and also one of the most important.

At a Glance
Browser tracking
Meta Pixel (formerly Facebook Pixel)
Server tracking
Conversions API
Management
Events Manager
Event types
Standard events, custom events, custom conversions
Deduplication
Matching event_id across browser and server events
Verification
Test Events and Diagnostics in Events Manager
On This Page
  1. Meta Pixel
  2. Standard and Custom Events
  3. Conversions API
  4. Events Manager
  5. Privacy Changes and Aggregated Event Measurement
  6. Checking Your Setup
  7. Putting This to Work
  8. In Practice
  9. Key Terms
  10. Key Facts
  11. Sources

Meta Pixel

The Meta Pixel is a snippet of JavaScript placed on every page of a website. It records page views and events such as ViewContent, AddToCart, Lead and Purchase, and sends them to Meta along with browser information. The Pixel was renamed from Facebook Pixel in 2022, and the code is the same product.

Standard and Custom Events

Standard events are predefined actions Meta recognizes for optimization and reporting, such as Purchase, Lead, CompleteRegistration and AddToCart. Custom events are actions you define yourself. Custom conversions let you create a reportable conversion from a URL rule or an existing event without changing code.

Conversions API

The Conversions API sends events from your server to Meta instead of, or in addition to, the browser. It is more resilient to browser restrictions and ad blockers. Meta's documentation recommends a redundant setup in which the same events are sent from both the browser and the server, with each pair sharing an event_id so Meta can deduplicate them.

Events Manager

Events Manager lists your data sources, shows which events are arriving, reports event match quality and offers Test Events for checking a setup before launch. It is also where you configure the Conversions API, generate access tokens and manage integrations with platforms such as Shopify and Google Tag Manager.

Privacy Changes and Aggregated Event Measurement

Since 2021, Apple's App Tracking Transparency framework reduced the data available from iOS users. Meta responded with Aggregated Event Measurement, which limits the number of web events an advertiser can prioritize per domain and relies on domain verification. The practical effect is that server-side tracking and clean event setup matter more than they did before.

Checking Your Setup

Use Test Events to confirm events fire with the right parameters, check the Diagnostics tab for warnings, and review event match quality for server events. A setup is ready when the key conversion event arrives from both browser and server, deduplicates correctly and matches a high share of users.

Putting This to Work

If your account cannot see purchases, bookings or leads accurately, every other setting is working with bad information. Tracking is the first thing to check when results are disappointing.

In Practice

An online store had the Pixel installed but no server-side tracking. After adding the Conversions API, Meta saw almost half again as many purchases, and campaigns optimized toward buyers instead of browsers.

Watch Out

Sending the same event from browser and server without a shared event_id inflates conversion counts and distorts optimization.

Key Terms

Standard event
A predefined event name Meta recognizes, such as Purchase.
event_id
A unique identifier shared by a browser event and its server copy so Meta can deduplicate them.
Event match quality
Meta's score for how well server events can be matched to accounts.
Domain verification
Proving ownership of a domain inside Business Settings.

Key Facts

  • Meta's developer documentation describes redundant browser and server setup as the recommended approach.
  • Conversions API events are sent to the same Pixel ID used by the browser Pixel.

Sources

  1. Conversions API overview, Meta for Developers developers.facebook.com
  2. Conversions API, using the API, Meta for Developers developers.facebook.com
  3. Meta Pixel standard events, Meta for Developers developers.facebook.com
  4. Meta Pixel, Meta for Developers developers.facebook.com
  5. Events Manager business.facebook.com
  6. Meta Business Help Center www.facebook.com
  7. Search Engine Land, measurement and privacy searchengineland.com

Last reviewed October 6, 2026. Platforms change often, so confirm details in the sources above before acting on them. This guide is general information and is not marketing advice for your business.

Have Our Team Handle This

Our team runs this every day. Book a call and we will plan it for your business.

Request a ProposalBook a Call