Lightspeed server-side tracking with the Meta Conversions API
Send every purchase from your Lightspeed shop 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 Lightspeed eCom orders and sent to your Meta pixel from the server, through the Meta Conversions API. Nothing in the browser talks to Meta, so an ad blocker has nothing to block. Each event carries hashed customer data for Advanced Matching.
Prerequisites
- Workspace admin in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking).
- A Lightspeed eCom (C-Series) administrator login (Europe or United States cluster) with an enabled API key (Read on Content, Products, Customers and Orders; Read and Write on Settings and Tracking), and your shop domain on Cloudflare: DNS record proxied (the orange cloud).
- Access to your pixel in Meta Events Manager, to copy its ID and generate a Conversions API access token.
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 server-side conversion tracking 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 server-side conversion tracking 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 server-side conversion tracking 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 server-side conversion tracking 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.In the app
1. Connect Lightspeed and Meta
- Store: add a Lightspeed API key in Product Metrics and sign in to Cloudflare for the gateway, then link the shop to your property. See Lightspeed.
- 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.
You should see: Connection status, Credential status and Installation status read Active, Configured and Active, and the gateway says Gateway setup complete; 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 shop shows: OneTrust, Cookiebot, Usercentrics or Osano. See Consent.
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 shop 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. Follow Create 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 Tracking, open the Tracking SDK link under the Cloudflare gateway’s Live endpoints: it returns JavaScript (the collector only accepts POST requests). Then place and pay for a test order.
You should see: Live endpoints lists the Tracking SDK and Event collector on your shop domain, and the order appears for the linked property; in Events Manager, the order shows as Purchase, plus the Product Metrics custom events your visitor’s consent allows. More checks: Check tracking works.
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
Why does Lightspeed tracking for Meta use Cloudflare?
Lightspeed eCom has no app proxy, so a Cloudflare gateway on your shop’s zone serves the script and collector on your shop domain. Product Metrics never changes your DNS.
When is a pay-on-pickup order sent to Meta?
When Lightspeed marks it paid. Meta refuses events more than 7 days old, so an order paid later than that doesn’t reach Meta.
Can I keep the Meta pixel on my Lightspeed shop?
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.
Do Lightspeed credit notes change the Meta event?
No. Sent Meta events aren’t revised. Credit notes adjust the Google Ads conversion only.
Where next
- Lightspeed: the full platform setup
- Meta: what Product Metrics sends and how to troubleshoot it
- Server-side tracking for Lightspeed in Google Ads: the same shop, the other channel
- Meta Conversions API on Lightspeed: the customer data each event carries
- Server-side conversion tracking: every platform and channel
- On the website: Full Signal Tracking, ad blocker conversion tracking check, first-party cookie, Product Metrics for Lightspeed