> ## Documentation Index
> Fetch the complete documentation index at: https://e328d4e-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://e328d4e-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://e328d4e-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://e328d4e-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# WooCommerce server-side tracking with the Meta Conversions API (/docs/tracking/server-side/woocommerce-meta)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1949 · updated: 2026-11-16 -->
Related: [Shopify server-side tracking for Google Ads](/docs/tracking/server-side/shopify-google-ads.md), [WooCommerce server-side tracking for Google Ads](/docs/tracking/server-side/woocommerce-google-ads.md), [Magento server-side tracking for Google Ads](/docs/tracking/server-side/magento-google-ads.md), [Lightspeed server-side tracking for Google Ads](/docs/tracking/server-side/lightspeed-google-ads.md), [Shopware server-side tracking for Google Ads](/docs/tracking/server-side/shopware-google-ads.md), [Server-side tracking for Google Ads on any website with Cloudflare](/docs/tracking/server-side/cloudflare-google-ads.md)

> Send every purchase from your WooCommerce store to Meta from the server through the Meta Conversions API, with Advanced Matching and the script served from your own domain.

Each purchase is confirmed from **your WooCommerce orders** and sent to your Meta pixel [from the server](/docs/concepts/server-side-tracking), through the **Meta Conversions API**. Nothing in the browser talks to Meta, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block. Each event carries hashed customer data for [Advanced Matching](/docs/tracking/enhanced-conversions/woocommerce-meta).

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking).
* **A WordPress administrator login**, PHP 8.1+ and WordPress 6.4+ with WP-Cron running, and the shop at the root of an HTTPS domain (such as `https://shop.example.com`: no subfolder, no custom port).
* **Access to your pixel in Meta Events Manager**, to copy its ID and generate a Conversions API access token.

## Set it up with AI



Paste the prompt into your assistant.



First connect the Product Metrics MCP server ([https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp); see [Connect your assistant](/docs/mcp/connect)).

**Claude or ChatGPT:** "Set up server-side conversion tracking for my WooCommerce store in Meta with Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something."

**Claude Code or Codex:** "Set up server-side conversion tracking for my WooCommerce store in Meta with Product Metrics. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser."

## In the app

### 1. Connect WooCommerce and Meta

* **Store:** install the **Product Metrics for WooCommerce** plugin, then paste your one-time setup token under **WooCommerce → Product Metrics** and select **Connect store**. Then link the store to your property. See [WooCommerce](/docs/platforms/woocommerce).
* **Meta:** in Events Manager, copy your **Pixel or Dataset ID** and generate a Conversions API access token, then add both under **Tracking → Meta Conversions API → Connect Meta** and send a test event. See [Meta](/docs/channels/meta).



![The Add Meta destination form with Pixel or Dataset ID, Access token, Test event code (optional) and the Send events to Meta switch, then the saved Meta Conversions API destination showing Active, the access token Accepted by Meta and Sending On.](/docs/_assets/b8f3701ffab8399a9aad9788c63abe4161115d01a029732731a74012315454bb)

*Figure: Add Meta destination: paste the Pixel or Dataset ID and access token, keep Send events to Meta on.*

**You should see:** the plugin says **Store connected successfully.** and **Webhooks: 2 of 2 active**; Events Manager shows the test event under **Test events**.

### 2. Choose your consent banner

In Product Metrics, open **Tracking → Configure consent** and choose the banner your store shows: OneTrust, Cookiebot, Usercentrics or Osano.

After you change it, clear your full-page cache so every page loads the new setting. Left on **Not configured**, Product Metrics can't read the visitor's choice and treats it as not given. See [Consent](/docs/concepts/consent).



> **Warning:** Meta has no consent mode. Product Metrics sends an event only when the visitor allowed ad user data; the custom events also need analytics consent. A wrong banner here means nothing reaches Meta.

**You should see:** **Configure consent** names the banner your store actually shows.

### 3. Create custom conversions

In Events Manager, create a custom conversion for each Product Metrics value you want to bid on, with the rule `pm_purpose` equals the purpose: `PMOrderRevenue` (`ORDER_REVENUE`) for revenue, `PMOrderProfit` (`ORDER_PROFIT`) for profit, every other event in [Meta events](/docs/concepts/conversion-actions-and-events#meta-events). Follow [Create custom conversions in Meta](/docs/using/conversion-actions#custom-conversions-in-meta) once a test order has reached Meta.

**You should see:** your custom conversions show in Events Manager.

### 4. Check it works

In WordPress, under **WooCommerce → Product Metrics**, select **Verify with next paid order**, place and pay for a test order within ten minutes, then select **Refresh connection status**.

**You should see:** **Live order delivery** reads **Verified**; in Events Manager, the order shows as `Purchase`, plus the Product Metrics custom events your visitor's consent allows. More checks: [Check tracking works](/docs/using/check-tracking).



**How it works on WooCommerce**

* **Script and collector served by:** The plugin, from your WordPress site: its collector is a WordPress REST route on your domain (`/wp-json/<namespace>/c/<key>`, with a namespace generated for your store). No Cloudflare step, no DNS change, no script tag
* **Purchase confirmed from:** Your WooCommerce orders
* **Sent:** When the order reaches a status you selected under **Paid order statuses**
* **Delivered:** Server-side, through the Meta Conversions API: `Purchase` plus the Product Metrics custom events
* **Refunds and cancellations:** Sent events aren't revised. Meta refuses events more than 7 days old
* **Consent read from:** OneTrust, Cookiebot, Usercentrics or Osano

## Troubleshooting

### The event isn't in Meta's custom conversion selector

Meta lists an event only after it received it. Place a test order with all cookies accepted, then create the custom conversion.

## FAQ

### Can I keep the Meta pixel on WooCommerce?

Yes. Meta counts an event once when the pixel and the Meta Conversions API send the same event name and event ID within 48 hours. `Purchase` uses the order transaction ID, so it deduplicates on its own. `AddToCart` and `InitiateCheckout` need your developer to pass Product Metrics' event ID to the pixel.

### When does a WooCommerce order reach Meta?

When it reaches a status you selected under **Paid order statuses**. Make sure that happens within 7 days of the order: Meta refuses older events.

### What customer data does Advanced Matching send to Meta?

With marketing consent, each event carries the hashed email, name, postal code and country, plus IP address and browser, through the Meta Conversions API. See [Meta Conversions API on WooCommerce](/docs/tracking/enhanced-conversions/woocommerce-meta).

### Why do custom events show fewer orders than Purchase?

`Purchase` needs ad user data consent, while the Product Metrics custom events such as `PMOrderProfit` also need analytics consent. Visitors who allowed only ad user data count in `Purchase` alone.

## Where next

* [WooCommerce](/docs/platforms/woocommerce): the full platform setup
* [Meta](/docs/channels/meta): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for WooCommerce in Google Ads](/docs/tracking/server-side/woocommerce-google-ads): the same store, the other channel
* [Meta Conversions API on WooCommerce](/docs/tracking/enhanced-conversions/woocommerce-meta): the customer data each event carries
* [Server-side conversion tracking](/docs/features/ad-blocker-proof-tracking): every platform and channel
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [Product Metrics for WooCommerce](https://www.productmetrics.io/platforms/woocommerce)

Developers: do the same with the [CLI](/docs/cli/commands#destinations) or the [API](/docs/api/destinations/set-meta).
