The Meta pixel is a snippet of code that reports website events to Meta from the browser; the Conversions API (CAPI) is a second path that sends the same events from your server. In 2026, browser restrictions, declined consent and content blockers mean pixel-only accounts lose part of their conversions. The correct setup is to run both and match events with an event_id so nothing is counted twice.
What is the Meta pixel and what does it do?
The Meta pixel is a JavaScript snippet you add to your site. When a visitor opens a page, adds to cart or completes a purchase, it reports that event to Meta. Meta uses those signals for two jobs: showing ads to the right people (optimization) and reporting results back to you (measurement). Weak signal means both an incomplete report and a poorly trained algorithm.
How do you install the Meta pixel?
Setup takes four steps and the order matters. Adding CAPI before your events are defined just sends incomplete data down two channels instead of one.
- Add the base code: create a pixel in Events Manager and place the base code on every page.
- Define events: set up business-outcome events like Purchase and Lead first, then add funnel events.
- Connect the Conversions API: send the same events from your server with the same customer parameters.
- Deduplicate: give each event a unique event_id and use the same ID on both channels.
Why did the Conversions API become essential?
Browser-side measurement erodes in four places: declined consent, content blockers, in-app browser behavior, and cookie lifetime limits. Server-side sending recovers a significant part of that erosion because it delivers the event independently of the browser. We covered the general logic in server-side tracking and signal loss.
Is your measurement actually solid?
Ads Sensor puts your Meta and Google data next to GA4 and explains inconsistencies in conversion counts through AI analysis.
How do you raise event match quality?
Event match quality is a score out of 10 showing how confidently your event can be matched to a Meta user. What drives it is the set of customer information parameters you send with the event. In practice the biggest jump comes from adding email and phone number, followed by first name, last name, city and country.
- Email and phone: the two strongest matching fields, and you already have them at checkout.
- External ID: sending your own customer ID strengthens matching for repeat buyers.
- IP and user agent: must be passed on server-side events, otherwise matching weakens.
- fbc and fbp: forward the click and browser identifiers to the server; these are the most commonly skipped CAPI fields.
How do you verify the setup?
Finishing the setup is not the same as verifying it. Use the test tool in Events Manager to see events arriving, check the deduplication indicator to confirm matching works, and verify that purchase values line up with real order totals. For overall account health, use our ad account audit checklist.
Measurement infrastructure is the invisible half of ad performance. To see whether your Meta and Google numbers agree, join the Ads Sensor beta: four platforms and GA4 in one dashboard, with drift explained.