Magento POAS bidding: Meta Conversions API with profit
Send profit from Magento orders to Meta through the Meta Conversions API with Advanced Matching, and optimise on it with a ROAS goal.
Every paid Magento 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.
The module, installed once by a developer.
Your pixel ID and a Conversions API access token.
Meta optimises on profit through a custom conversion on PMOrderProfit.
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/mcpClaude Code: run this in your terminal.
claude mcp add --transport http product-metrics https://www.productmetrics.io/mcpSetting it up with AI takes one prompt and 60 seconds: paste it into your assistant.
Set up POAS bidding (bidding on profit) for my Magento 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 Magento 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 Magento 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 Magento 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 Magento store view connected: Magento 2.4, 2.0 or 1.9 / OpenMage, Magento Admin access, the public HTTPS shop address and the store-view ID, and a developer with access to your server who installs the Product Metrics module (Composer or ZIP), adds the store view’s private configuration file and keeps Magento cron running. The connection reads Active before you link your property. See Magento.
- 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 Magento store and Meta
Connect your store with Magento. 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 Magento.
Start the setup
The Magento page lists three steps: connect your store, install the module and link a property. Select Connect Magento.
Describe your store
Choose your Magento version, enter the Store URL and the numeric Store view ID, then select Create module configuration. Download the configuration file and share it with your developer privately: it holds a private key.
Install the module
Your developer installs the module. Select Setup guide and choose your Magento version and installation method: it walks your developer through installing the module and verifying the connection.
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.
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.
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.
Magento’s cookie restriction notice does not grant consent. Choose OneTrust, Cookiebot, Usercentrics or Osano under Tracking → Configure consent, or have your developer pass the visitor’s choices to Product Metrics. 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.
Follow the next step
Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.
Configure consent
Under Configure consent, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.
You should see: under Manage Magento, the connection is Active and your property is linked; Events Manager shows the test event under Test events.
2. Activate your additional costs
Product costs come from the cost stored on each Magento order item, read when the order currency matches your base currency. 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.
- In Events Manager, choose Custom conversions → Create custom conversion.
- Select your pixel and the event
PMOrderProfit. - Add the event parameter rule
pm_purposeequalsORDER_PROFIT. - 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 Magento
| On Magento | Sent as | |
|---|---|---|
| Revenue | The order’s revenue | Purchase (and PMOrderRevenue, ORDER_REVENUE) |
| Product costs | The cost on each Magento order item (order currency = base currency) | Taken off profit |
| Payment fees | Your additional costs | Taken off profit |
| Shipping, handling, returns | Your additional costs | Taken off profit |
| Profit | Revenue ex tax − all costs | PMOrderProfit (ORDER_PROFIT); 0 for a loss, signed value in pm_contribution_profit |
| Refunds | Your store reports them | Not sent: Meta events aren’t revised |
Meta rejects events older than 7 days, so past orders are not imported.
Troubleshooting
| Problem | Fix |
|---|---|
| Orders arrive with revenue only | A 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 events | Remove the test event code from your Meta destination under Tracking → Meta Conversions API. |
FAQ
Which Magento costs make up the profit Meta receives?
Product costs come from the cost stored on each Magento order item, read when the order currency matches your base currency. Payment fees, shipping, handling and returns come from your additional costs.
Does Magento’s cookie notice count as consent for Meta?
No. Magento’s cookie restriction notice doesn’t grant consent. Choose OneTrust, Cookiebot, Usercentrics or Osano under Tracking → Configure consent, or have your developer pass the visitor’s choices to Product Metrics.
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 Magento