# Meta pixel and Conversions API on WooCommerce

> On WooCommerce, the official "Meta for WooCommerce" extension enables the pixel and the Conversions API together from initial setup, with automatic deduplication by event_id. It handles most of the work, but not all of it: I always check what falls to it and what doesn’t.

- Source canonique : [https://allaux.fr/en/services/tracking/pixel-meta-api-conversions-woocommerce](https://allaux.fr/en/services/tracking/pixel-meta-api-conversions-woocommerce)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> Install the official Meta for WooCommerce plugin: it enables the pixel and the Conversions API from the same screen and handles deduplication by event_id. Above all, check it is linked to the right Business account and the right data source. If another plugin or a snippet in functions.php already installs the pixel, remove it: that is the usual cause of duplicated Purchase events.

## What I see most often

- Meta for WooCommerce installed "by default" when the shop was set up, never reconfigured since
- Uncertainty over what the extension actually sends to Meta: pixel only, or pixel plus Conversions API
- Purchase events that seem to be missing even though the extension is active
- A customised checkout (extra fields, steps modified by another plugin) partly slipping past standard tracking
- Confusion between the old "Facebook for WooCommerce" extension and its current name, "Meta for WooCommerce"

## What I configure and check

1. **Connecting the Meta Business account** — I check the extension is linked to the right Business account and the right data source (pixel) in Meta Events Manager, not a test account created by mistake.
2. **Enabling pixel and Conversions API** — The extension offers both in the same setup screen: once the account is connected, it enables the browser pixel and generates the token needed for server-side sending itself.
3. **Checking standard WooCommerce events** — I check the events covered by default (ViewContent, AddToCart, InitiateCheckout, Purchase) actually match the shop’s real checkout flow, especially if a third-party plugin changes the order steps.
4. **Verifying deduplication** — In Meta Events Manager’s event overview tab, I confirm each key event appears with two sources (browser and server) merged, a sign that event_id deduplication is working as advertised.
5. **Edge cases not covered** — I look at journeys that fall outside the standard funnel (phone orders entered manually, offline payment, a custom order form): they don’t go through the extension and stay invisible to Meta.

## What’s automatic, what isn’t

Once connected, the extension handles most of it automatically: setting up the pixel, generating the Conversions API token, sending standard WooCommerce events from both sides with the same event ID, and deduplication on Meta’s end. That’s what sets it apart from a manual setup where every step has to be wired by hand.

What still falls to me: checking the configuration matches the shop’s real checkout flow (not just the default WooCommerce one), confirming in Events Manager that deduplication is actually happening rather than just assumed, and covering order journeys that don’t go through the standard WooCommerce cart.

A well-connected extension doesn’t remove the need for a check in Events Manager: that’s the only place, and nowhere else, where you can see whether the two sources are truly merged.

## The most integrated of the three platforms

> This is the simplest setup to put in place among PrestaShop, WooCommerce and Shopify for this specific topic: the official extension links pixel and Conversions API in a single configuration, where the other two require more manual assembly.

## Related pages

- **The same topic on PrestaShop** — No official equivalent as integrated: the principle stays the same, the configuration has to be checked module by module. ([/services/tracking/pixel-meta-api-conversions-prestashop](/services/tracking/pixel-meta-api-conversions-prestashop))
- **The same topic on Shopify** — Native Meta channel or custom pixels depending on Shopify’s checkout changes. ([/services/tracking/pixel-meta-api-conversions-shopify](/services/tracking/pixel-meta-api-conversions-shopify))
- **The ecommerce events that matter** — The prioritisation logic to know on the GA4 side, with the same demand for reliable parameters. ([/services/tracking/evenements-ecommerce-qui-comptent](/services/tracking/evenements-ecommerce-qui-comptent))
- **Duplicate statistics** — Common causes of duplicates, including when two extensions set up the same pixel. ([/services/tracking/doublons-statistiques-causes](/services/tracking/doublons-statistiques-causes))
- **WordPress / WooCommerce** — The hub for WooCommerce work: modules, migrations, performance, integrations. ([/wordpress-woocommerce](/wordpress-woocommerce))
- **ChatGPT Ads conversion tracking** — OpenAI pixel, Conversions API, oppref and consent: the same pixel-plus-server logic, applied to ChatGPT ads. ([/services/tracking/suivi-conversions-chatgpt-ads](/services/tracking/suivi-conversions-chatgpt-ads))
- **ChatGPT Ads extension for WooCommerce** — OpenAI pixel and Conversions API, compatible with HPOS, the block checkout and consent plugins: built and installed by me. ([/wordpress-woocommerce/extension-chatgpt-ads](/wordpress-woocommerce/extension-chatgpt-ads))

## FAQ

### Are Meta for WooCommerce and Facebook for WooCommerce the same extension?

Yes, it’s the same product renamed. If an old "Facebook for WooCommerce" version is still active, I check it’s been properly migrated to the current one before doing anything else.

### Does the extension handle deduplication automatically?

Yes, in standard configuration it sends the same event_id via the pixel and the server for each event. I still check in Events Manager that this deduplication is actually happening, not just theoretical.

### Does the extension cover a customised checkout?

It covers the standard WooCommerce funnel. If a plugin changes the order steps or adds an offline payment method, it needs checking case by case to see whether the corresponding events are still captured.

### Should I remove an old pixel module before installing Meta for WooCommerce?

Yes, in most cases, to avoid two sources setting up the same pixel and skewing statistics with duplicates.

### How long does the setup take?

Connecting the account and enabling the pixel with the Conversions API usually takes under an hour. Checking deduplication and edge cases takes a bit longer.