Lightspeed POAS bidding: Meta Conversions API with profit
Send profit from Lightspeed orders to Meta through the Meta Conversions API with Advanced Matching, and optimise on it with a ROAS goal.
Every paid Lightspeed 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.
An API key from Lightspeed, then a Cloudflare sign-in.
Your pixel ID and a Conversions API access token.
Meta optimises on profit through a custom conversion on PMOrderProfit.
Prerequisites
- Editor or admin on the property in Product Metrics, with Pro (Full Signal Tracking).
- Your Lightspeed eCom (C-Series) shop connected: a back-office administrator login (an API key can’t sign in), the shop’s cluster, hostname and numeric Shop ID, and an enabled API key with its secret that has Read on Content, Products, Customers and Orders, and Read and Write on Settings and Tracking. The shop can’t already be connected to another workspace, and it reads Active with Configuration is current before you link your property. See Lightspeed.
- Your shop domain on Cloudflare, with its DNS record proxied (the orange cloud), and a workspace admin who signs in to Cloudflare once.
- 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 Lightspeed shop and Meta
Connect your store with Lightspeed. 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.
On Lightspeed, Product Metrics reads consent from the banner chosen under Tracking → Configure consent (OneTrust, Cookiebot, Usercentrics or Osano). The profit event also needs analytics consent. See Consent.
You should see: Connection status, Credential status and Installation status read Active, Configured and Active, publication reads Configuration is current, and the gateway says Gateway setup complete; Events Manager shows the test event under Test events.
2. Activate your additional costs
Product costs come from the cost price on each Lightspeed order line. Lightspeed doesn’t report payment fees, so those always come from External payment fixed cost and External payment (%). 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.
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.
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/mcpPaste the prompt into your assistant.
Set up POAS bidding (bidding on profit) for my Lightspeed shop 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 Lightspeed shop 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 Lightspeed shop 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 Lightspeed shop 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.How it works on Lightspeed
| On Lightspeed | Sent as | |
|---|---|---|
| Revenue | The order’s revenue | Purchase (and PMOrderRevenue, ORDER_REVENUE) |
| Product costs | The cost price on each Lightspeed order line | Taken off profit |
| Payment fees | Your additional costs (Lightspeed reports no payment fees) | 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 Lightspeed costs make up the profit Meta receives?
Product costs come from the cost price on each Lightspeed order line. Lightspeed reports no payment fees, so those come from your additional costs, as do shipping, handling and returns.
Which consent banners work with Lightspeed?
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 Lightspeed