Skip to content
Meta

WooCommerce POAS bidding: Meta Conversions API with profit

Send profit from WooCommerce orders to Meta through the Meta Conversions API with Advanced Matching, and optimise on it with a ROAS goal.

Every paid WooCommerce order goes to your Meta pixel through the Meta Conversions API, server-side, with its profit in the custom event PMOrderProfit. Optimise on a custom conversion on it and Meta steers on profit (POAS). Each event carries hashed customer data for Advanced Matching, so Meta can match it to the person who clicked.

Set it up with AI

Connect your assistant

First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.

In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:

https://www.productmetrics.io/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Setting it up with AI takes one prompt and 60 seconds: paste it into your assistant.

Set up POAS bidding (bidding on profit) 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.
Set up POAS bidding (bidding on profit) 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.
Set up POAS bidding (bidding on profit) 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.
Set up POAS bidding (bidding on profit) 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.

Prerequisites

  • Editor or admin on the property in Product Metrics, with Pro (Full Signal Tracking).
  • Your WooCommerce store connected: a WordPress administrator login, WordPress 6.4+ and PHP 8.1+ with WP-Cron running, and the shop at the root of an HTTPS domain (no subfolder, no custom port). You install the Product Metrics plugin, connect it with a one-time setup token, choose your paid order statuses and link the store to your property. See WooCommerce.
  • Access to your pixel in Meta Events Manager, to copy its ID and generate a Conversions API access token.

In the app

1. Connect your WooCommerce store and Meta

Connect your store with WooCommerce. Then, under Tracking → Meta Conversions API → Connect Meta, add your Pixel or Dataset ID and a Conversions API access token from Events Manager, and send a test event: Meta.

Connect your store, step by step:

Open Ecommerce platforms

Go to Integrations → Ecommerce platforms and select Connect on WooCommerce.

The store platform list in Ecommerce platforms: WooCommerce, Magento, Shopware 6, Lightspeed and Custom Store / Webhook Integration, each with a Connect button, with WooCommerce outlined.

Start the setup

The WooCommerce page lists three steps: connect your store, install and connect the plugin, and link a property. Select Connect WooCommerce.

The WooCommerce page under Integrations → Ecommerce platforms: 0 of 3 steps done, step 1 Connect your store with the Connect WooCommerce button, then Install and connect the plugin and Link a property.

Enter your store URL

Enter your WooCommerce shop address, starting with https://, and select Create connection.

The Connect WooCommerce dialog: an empty store URL field and the Cancel and Create connection buttons.

Install and pair the plugin

Download the plugin ZIP and install it in WordPress Admin, then paste the one-time setup token from this page under WooCommerce → Product Metrics and select Connect store. The page updates by itself once WooCommerce confirms the connection.

Follow the setup guide

Select Setup guide for every step in WordPress and WooCommerce, with screenshots. You can also download it as a Word document.

The WooCommerce setup guide panel in Product Metrics: a Download Word document button, then Before you begin: a WordPress administrator login, access to your Product Metrics workspace, your shop's web address starting with https:// and a test payment method.

Link a property

With the store connected, choose which Product Metrics property receives its orders under Link property. Then authorise Google Ads conversions.

The WooCommerce page under Integrations → Ecommerce platforms for northwind-outfitters.example, Active, 2 of 3 steps done: Connect your store and Install and connect the plugin are done, and Link a property is next, with the Default storefront scope.
Example data.

Then add the Meta destination:

Open Tracking

Go to Integrations → Tracking. Under Destinations, select Meta Conversions API.

Open the Meta panel

The panel lists the events Product Metrics sends and what you need: a Pixel or Dataset ID and a Conversions API access token from Events Manager. Select Connect Meta.

The Meta Conversions API panel, Not configured: Product Metrics sends AddToCart, InitiateCheckout and Purchase from the server to your Meta pixel, with hashed customer data when the shopper consented to marketing, plus revenue, profit, new and returning customer, and LTV events, which also need analytics consent. You need a Pixel or Dataset ID and a Conversions API access token from Events Manager. A Connect Meta button.

Add the Meta destination

Choose the store, enter the Pixel or Dataset ID and the Access token, and optionally a Test event code. Keep Send events to Meta on and select Add destination.

The Add Meta destination dialog for the example store Northwind Outfitters: empty Pixel or Dataset ID, Access token and Test event code (optional) fields, each with where to find it in Events Manager, the Send events to Meta switch on, and the Cancel and Add destination buttons.
Example data.

Create custom conversions in Meta

In Events Manager, create a custom conversion for each Product Metrics event you want to measure, using the event names listed in the panel.

The Set up custom conversions in Meta section of the Meta Conversions API panel: the steps in Events Manager, then a table of each conversion and its event: New customer revenue PMNewCustomer, New customer profit PMNewCustomerProfit, Returning customer revenue PMReturningCustomer, Returning customer profit PMReturningCustomerProfit and Order revenue PMOrderRevenue.

On WooCommerce, Product Metrics reads consent from the banner chosen under Tracking → Configure consent (OneTrust, Cookiebot, Usercentrics or Osano). Left on Not configured, consent counts as not given. The profit event also needs analytics consent. See Consent.

Open Tracking

Go to Integrations → Tracking. The checklist shows six steps: start by connecting your store, or use Cloudflare Tracking if you have no store platform.

Tracking in Product Metrics with the Complete your tracking setup checklist of six steps, starting with Connect your store.

Follow the next step

Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.

The Complete your tracking setup checklist in Tracking: 3 of 6 essential steps completed, with Connect your store, Link the store to this property and Install storefront tracking ticked, and Configure consent open as step 4 with the consent platform still Not configured.

Configure consent

Under Configure consent, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.

The Consent management panel in Tracking: the storefront script collects nothing until your cookie banner says the visitor agreed, a Not configured status, and the Consent platform dropdown.

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. Activate your additional costs

Product costs come from the source you chose in the plugin under Product cost: WooCommerce Core COGS or a Product meta key. If you set Payment cost or Actual shipping cost to an Order meta key, those per-order costs are used instead of the estimates. Everything else comes from your additional costs.

Then, under Tracking → Add your additional costs, check the defaults for your country, set Product cost fallback (%) and select Activate additional costs: Costs.

Add your additional costs

Product costs come from your store where it reports them. Under Add your additional costs, add shipping, handling, returns and payment fees, set Product cost fallback (%) and select Activate additional costs, so the profit conversions carry real profit.

You should see: the Profit tracking section says your additional costs are active.

3. Create a custom conversion on PMOrderProfit

This step happens in Meta. PMOrderProfit only appears in Meta’s selector after Meta has received one, so first place a test order with consent accepted and your costs active.

  1. In Events Manager, choose Custom conversions → Create custom conversion.
  2. Select your pixel and the event PMOrderProfit.
  3. Add the event parameter rule pm_purpose equals ORDER_PROFIT.
  4. Choose Purchase as the category. Use the event’s value and currency; leave the fixed conversion value unset.

For ROAS, skip this: the standard Purchase event already carries revenue.

Once your test order arrived, remove the test event code, or events keep landing under Test events only.

You should see: the custom conversion shows in Events Manager.

4. Optimise on profit

In your sales campaign, choose the PMOrderProfit custom conversion as the conversion event, optimise for value and set a ROAS goal as a percentage: 100% is break-even, 150% keeps €0.50 profit per €1 of ad spend. For revenue (ROAS), use Purchase with your revenue target, for example 420% for a ROAS of 4.2.

Moving a campaign from revenue to profit? Lower the goal: POAS and ROAS bidding.

You should see: the ad set’s conversion event is your PMOrderProfit custom conversion.

5. Check it works

Open Tracking → Meta Conversions API: Check tracking works.

You should see: Access token: Saved, Sending: On with test mode off, and the delivery counts; recent orders arrive with a known profit.

How it works on WooCommerce

On WooCommerceSent as
RevenueThe order’s revenuePurchase (and PMOrderRevenue, ORDER_REVENUE)
Product costsWooCommerce Core COGS, or the product meta key you chose in the pluginTaken off profit
Payment feesAn order meta key you chose for Payment cost; otherwise your additional costsTaken off profit
Shipping, handling, returnsYour additional costsTaken off profit
ProfitRevenue ex tax − all costsPMOrderProfit (ORDER_PROFIT); 0 for a loss, signed value in pm_contribution_profit
RefundsYour store reports themNot sent: Meta events aren’t revised

Meta rejects events older than 7 days, so past orders are not imported.

Troubleshooting

ProblemFix
Orders arrive with revenue onlyA cost of the order is still unknown. Complete your costs under Profit tracking → Edit costs: an order is sent with profit only once every cost is known (profit rules).
Events only show under Test eventsRemove the test event code from your Meta destination under Tracking → Meta Conversions API.
Nothing reaches MetaCheck that Tracking → Configure consent names the banner your store shows. Left on Not configured, Product Metrics can’t read the visitor’s choice and treats it as not given.

FAQ

Which WooCommerce costs make up the profit Meta receives?

Product costs come from WooCommerce Core COGS or the product meta key you chose in the plugin. Payment fees come from an order meta key if you set one for Payment cost, otherwise from your additional costs, like shipping, handling and returns.

OneTrust, Cookiebot, Usercentrics or Osano, chosen under Tracking → Configure consent. PMOrderProfit needs both marketing and analytics consent.

Do I still need my Meta pixel?

You can keep it. Purchase uses the order transaction ID, so Meta counts it once when your pixel and the Meta Conversions API both send it within 48 hours. The server-side events also carry hashed customer data for Advanced Matching.

Does Meta get past orders or refunds?

No. Meta rejects events older than 7 days, so past orders aren’t imported, and a later refund doesn’t revise the order’s Meta events.

Where next

On the website: POAS, target ROAS, POAS calculator, Product Metrics for WooCommerce

Developers: do the same with the CLI or the API.