The Meta Pixel is a tracking code on your website that reports visitor actions such as add to cart and purchase to Meta from the browser. The Conversions API (CAPI) sends the same events from your server or store platform. You set up both and deduplicate them with an event ID (event_id), so sales lost to browser restrictions get measured.
Accurate measurement is the foundation of Facebook and Instagram ads: if the platform can't tell which ad drove a sale, sales campaigns can't learn who to show ads to. This article explains both tools, why they're used together, and how to set them up on Shopify and WooCommerce. Interface names are described in general terms as of October 2026.
The Meta Pixel is a piece of JavaScript placed on your site that sends visitor actions to Meta as events. Meta's Meta Pixel help page covers the tool in detail.
The standard events most used in ecommerce:
With these events, the pixel does three jobs: it measures ad results, feeds optimization for events like purchases, and lets you build retargeting audiences from site visitors.
The Conversions API is an integration method that sends events directly from your server or store platform to Meta's servers instead of from the visitor's browser. Because it travels server to server, it isn't affected by browser ad blockers, cookie restrictions or a page being closed halfway.
CAPI can also send events the browser never sees, such as an order whose payment is confirmed later or a sale completed over the phone.
You should use the pixel and the Conversions API together because each covers the other's blind spot. The pixel is good at capturing browser behavior and browser-specific information; CAPI provides a reliable second channel that isn't affected by browser restrictions.
Browser-side measurement has become harder in recent years:
Because of these restrictions, a pixel-only setup may never report some of your sales to Meta. Shopify's data-sharing help page states this plainly: browser-based ad blockers can stop the pixel from sharing data, while events sent server to server aren't affected by them.
Event deduplication means counting the two copies of the same event, one from the pixel and one from the Conversions API, as a single event; Meta does this when the event name and event ID match. Without deduplication, each purchase may be counted twice and your reports will look better than reality.
According to Meta's deduplication documentation, the recommended method works like this:
event_name in CAPI.eventID must match event_id in CAPI. An order number or a unique ID generated for each event is typically used.event_id arriving within a set period (48 hours in the documentation) is treated as a duplicate and discarded.Example: A customer completes order 10482. The browser pixel sends the Purchase event with eventID: "order_10482", and your server sends event_name: "Purchase" with event_id: "order_10482". Meta matches the two and counts one sale.
Events sent through the Conversions API include customer information (such as email and phone) in hashed form so Meta can match the event to the right person. Events Manager shows a match quality indicator for each event. Better matching means more sales are attributed to the right ad. When sharing this data, make sure you meet the requirements of your privacy policy and applicable data protection laws.
Setup depends on your store platform; if you use a hosted ecommerce platform, the official integration is the easiest and least error-prone route. The general flow is:
value (amount) and currency, ROAS can't be calculated.On Shopify, setup runs through the Facebook & Instagram sales channel app. After installing the app and connecting your Meta account, business portfolio and pixel, you choose a level in the data-sharing settings. According to Shopify's help page, there are three levels:
To reduce measurement loss, it makes sense to choose a level that includes the Conversions API rather than Standard. If an old pixel code was added manually to your theme, remove it so events aren't sent twice.
On WooCommerce, the official route is the "Meta for WooCommerce" extension. According to its documentation, it supports pixel setup and comes with the Conversions API integrated out of the box. After installing it and connecting your Meta account, check in Events Manager that events arrive from both browser and server and are deduplicated. If you also use another pixel plugin, keep only one active to avoid conflicts.
The most common mistake is installing the same pixel through several routes: when code added to the theme, a plugin and a platform integration all run at once, events are sent two or three times. Deduplication is designed only to match browser and server copies; events arriving twice from the same browser can corrupt reports.
Other common mistakes:
These mistakes share the same outcome: the ads dashboard doesn't reflect reality and budget decisions rest on bad data. Fixing measurement before scaling a campaign is far cheaper than the budget you'd lose afterwards.
You check the setup by running a real shopping flow on your site and confirming the events land in Events Manager with the right name, the right value and only once.
Checklist:
Once measurement is in place, metrics like ROAS and CPA become meaningful; we cover them in our guide on what ROAS is and how to calculate it. Ad tools like 14ads also read sales and revenue data in their reports from these events.
The Meta Pixel is code that runs in the visitor's browser and sends events to Meta from there. The Conversions API sends events directly to Meta from your server or store platform. Because server-side sending isn't affected by browser restrictions such as ad blockers, the two are used together.
Not if they're set up correctly. Meta counts the browser and server copies of the same event as one event when the event name and event ID (event_id) match. If those two fields don't match, events can be double-counted and your reports will be inflated.
The easiest way on Shopify is to install the Facebook & Instagram sales channel app and connect your Meta account. In the app's data-sharing settings, the Standard level uses only the pixel, while the Enhanced and Maximum levels add the Conversions API on top of the pixel.
Use the Test Events tool in Meta Events Manager, browse your site and go through the purchase steps to see whether events arrive in real time. The Meta Pixel Helper browser extension can also check the browser side. Make sure each event arrives from both the browser and the server and is deduplicated.
You can, but Meta won't know which ad drove a sale. Sales and revenue reports stay empty, ROAS can't be calculated, and campaigns optimizing for purchases can't learn who to target. For sales-focused ads, the pixel and Conversions API are effectively required.