How to Set Up Meta Conversions API on WooCommerce

On WooCommerce you do not build the Conversions API yourself. Meta publishes its own plugin, Meta for WooCommerce, and once you connect it the server-side events start with no extra setting. Your real work is the checks after the connection: removing any second pixel, testing a purchase from a non-admin account, and checking deduplication, coverage and match quality in Events Manager. The steps below follow Meta’s and WooCommerce’s own documentation and the plugin’s source code.

Which plugin does Meta support for WooCommerce?

Use the plugin listed on WordPress.org as Meta for WooCommerce, published by Facebook. It was called Facebook for WooCommerce, and WooCommerce’s own documentation now says “formerly Facebook for WooCommerce” (WooCommerce docs). The plugin’s URL slug still reads facebook-for-woocommerce, so both names point to the same plugin.

As of 2 Oct 2026, WordPress.org shows version 3.7.6, last updated 23 July 2026, with 400,000+ active installations. The plugin’s own header requires WordPress 5.6, PHP 7.4 and WooCommerce 6.4 or later (plugin source, v3.7.6).

Meta also lists WooCommerce among the commerce platforms in its partner integrations for website events, alongside BigCommerce, Ecwid and PrestaShop (About partner integrations for website events).

What do I need before I connect?

Meta’s checklist (Connect your WooCommerce account to Meta):

• A WordPress site where you have the administrator role.
• WooCommerce installed.
• Full control of your Meta business portfolio, or permission to manage the Page, Instagram profile, catalogue, ad account and pixel.
• Two-factor authentication turned on for the business portfolio.

How do I install and connect Meta for WooCommerce?

1. Open WordPress and go to Plugins > Add new plugin, search “Meta for WooCommerce”, click Install now, then Activate.
2. Go to Marketing > Facebook in the WordPress menu and click Get started.
3. Log in to Facebook with the account that manages your business portfolio.
4. Choose or create the business portfolio, Page, Instagram profile, catalogue, ad account and Meta pixel when prompted.
5. Enter your shop details, such as contact email, return policy and privacy policy.
6. Authorise the connection between WooCommerce and Meta.
7. Check back after 10 to 30 minutes, the time Meta gives for the integration to publish your shop.

You can see the connected assets later under Marketing > Facebook > Connection (WooCommerce docs).

Do I need to switch the Conversions API on?

No. WooCommerce’s documentation says the Conversions API is integrated out of the box, and once the extension is set up “no additional setting is required from you” (WooCommerce docs).

The plugin’s source code shows what that means in practice. In version 3.7.6, each of these events is sent from the browser pixel and from the server, with the same event ID (events tracker, v3.7.6):

The Purchase event also carries the order value, currency, order ID and customer details taken from the billing address. Those details are what Meta uses to match the server event to a Meta account.

Will the pixel and server events be counted twice?

Not if they share an event ID. Meta deduplicates a pixel event and a server event when the event name and the event ID match, and only within 48 hours of receiving the first one (Meta for Developers, deduplication). Meta says partner integrations such as WooCommerce handle these parameters for you (About deduplication), and the plugin’s code attaches the same ID to both copies.

What breaks this is a second pixel. If a theme snippet, Google Tag Manager or another tracking plugin also fires your pixel, that copy carries its own event ID, so Meta cannot pair it with the plugin’s events by event ID. For a step-by-step hunt, read how do I diagnose duplicate events between pixel and CAPI?

How do I test that it works?

1. Open Events Manager, click Data sources, select your pixel and open the Test events tab (Test events tool).
2. Enter your store URL and click Open website, keeping the Test events page open while you browse.
3. Log out of WordPress, or use a customer account, before you buy anything.
4. Place a real low-value order and confirm a Purchase arrives from both the browser and the server.
5. Check that Test events shows the second copy as deduplicated, then refund the order.

Step 3 matters. The plugin skips the Purchase event for any user who can manage WooCommerce, which includes administrators and shop managers (plugin utilities, v3.7.6). A test order placed while logged in as admin will look like a broken setup.

Test data stays in the tool for 24 hours or until you click Clear activity, and Meta says it can take 30 minutes or more for events to show in your analytics.

What should I check in Events Manager after a week?

Meta’s own maintenance list (Monitor and improve your Conversions API setup) gives four checks:

• Event coverage. Compare server events with unique browser events. Meta says to aim for a 75% coverage ratio.
• Event deduplication. The tab shows which deduplication keys you send. Expect event ID on every event the plugin sends.
• Event match quality. A score from 0 to 10 based on the customer details sent with each server event, calculated on the last 48 hours (About event match quality). Email and click ID carry the highest priority; how do I improve Event Match Quality on Meta? covers the rest.
• Diagnostics. Open the Diagnostics tab for active warnings and the steps Meta gives to fix each one.

If the numbers look wrong rather than missing, should I check tracking before optimising Meta ads? covers what to fix first. The wider setup questions sit in the Meta Pixel and CAPI guide.

What usually goes wrong on WooCommerce?

• A caching plugin swallows events. WooCommerce says some caching plugins’ JavaScript optimisation stops pixel events from firing, and the fix is to disable JS grouping in the caching plugin.
• The plugin is out of date. Meta’s page tells you to keep it updated from Plugins > Installed plugins, where you can also click Enable auto-updates.
• You wanted another tool to own tracking. WooCommerce documents a filter, facebook_for_woocommerce_integration_pixel_enabled, that turns off the plugin’s pixel and Conversions API so a different tool can take over. Use it rather than running two.
• Two-factor authentication is off. The connection needs it on the business portfolio.

FAQ

Is Meta for WooCommerce free?

Yes. The plugin is free to download from WordPress.org and is licensed GPLv2 or later. Its server events go out from your own WordPress server, so the running cost sits in your hosting. A separate tracking tool or managed server container, if you choose one instead, is a separate cost.

Is Meta for WooCommerce the same as Facebook for WooCommerce?

Yes. WooCommerce’s documentation calls it Meta for WooCommerce, formerly Facebook for WooCommerce, and the WordPress.org listing still uses the old URL slug. If you have the old name installed, update it in Plugins > Installed plugins rather than installing a second copy.

Why don’t my test purchases show up?

The most common reason is testing while logged in as an administrator or shop manager, because the plugin skips Purchase for those users. Log out, keep the Test events page open, and buy again. If events still do not arrive, check your caching plugin’s JavaScript settings.

Can I use PixelYourSite or GTM instead?

Yes, but pick one owner for the pixel and server events. Meta lists PixelYourSite and Google Tag Manager as partner integrations too. Running them alongside Meta for WooCommerce without turning one off sends events with different event IDs, which Meta cannot deduplicate by event ID.

Sources

Sources: Meta for WooCommerce on WordPress.org; WooCommerce documentation for Meta for WooCommerce; plugin source v3.7.6 on GitHub; Meta Business Help Center: Connect your WooCommerce account to Meta, About partner integrations for website events, About deduplication, Test events tool, Monitor and improve your Conversions API setup, About event match quality; Meta for Developers, deduplicate pixel and server events (checked 2 Oct 2026).