Lightspeed eCom server-side tracking and profit bidding (POAS)
Connect Lightspeed eCom (C-Series) with an API key and Cloudflare, get server-side conversion tracking live in Google Ads, Meta and ChatGPT Ads, and bid on profit, new customers or lifetime value.
Lightspeed tells Product Metrics about every paid order through webhooks Product Metrics registers for you, with the cost price on each line. A Cloudflare gateway on your shop domain serves the tracking. Product Metrics adds profit, new or returning customer and lifetime value, and sends it server-side to each ad channel. No code and no Google tag.
Prerequisites
- A Lightspeed eCom (C-Series) administrator login, on the Europe or United States cluster, for a shop that isn’t connected to another Product Metrics workspace.
- A shop domain that runs through Cloudflare with its DNS record proxied (the orange cloud) and a Cloudflare login for that account. Product Metrics never changes your DNS.
- A workspace on Pro (Billing), a property for the orders, and a workspace admin for the Cloudflare step.
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.
Connect my Lightspeed eCom shop to Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something; I'll enter the API key and secret in the app myself.Connect my Lightspeed eCom shop to Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something; I'll enter the API key and secret in the app myself.Connect my Lightspeed eCom shop to Product Metrics and walk me through each open setup step, giving me the link when I need to click something; I'll enter the API key and secret in the app myself. 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).Connect my Lightspeed eCom shop to Product Metrics and walk me through each open setup step, giving me the link when I need to click something; I'll enter the API key and secret in the app myself. 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).In the app
1. Create the API key in Lightspeed
- Sign in to the Lightspeed back office. Select Help (bottom left) and note the Store ID below your name, and your public shop hostname.
- Open Settings → Store Settings → Developers, select New API key (Dutch: Nieuwe API key), name it Product Metrics, Save.
- Under SETTINGS, enable the key and set:
| Section | Read | Write |
|---|---|---|
| Content (Inhoud) | ✓ | |
| Products (Producten) | ✓ | |
| Customers (Klanten) | ✓ | |
| Orders | ✓ | |
| Settings (Instellingen) | ✓ | ✓ |
| Tracking | ✓ | ✓ |
- Save (Opslaan). A new key starts disabled with nothing ticked. Write access to Settings lets Product Metrics add its shop script for you.
- Under DETAILS, copy the API key, select Show and copy the API secret.
You should see the key enabled, with the API key and secret copied.
2. Connect your store
Go to Ecommerce platforms → Connect Lightspeed, fill in Cluster, Store hostname, Shop ID, API key and API secret, and select Connect Lightspeed.
Cluster is EU for shops on .webshopapp.com and US for .shoplightspeed.com; a shop on its own domain keeps its original cluster. Store hostname is the shop’s hostname without /admin, and Shop ID is the Store ID.
The API key and secret are credentials. Enter them in the app and keep them out of chats. An assistant never needs them repeated back.
Product Metrics checks the key, saves the connection, registers its order webhooks and detects your shop language.
You should see Connection status Active, Credential status Configured and Installation status Active, then Configuration is current under Manage Lightspeed → Connection details and removal.
3. Send the shop’s orders to a property
In Tracking → Complete your tracking setup, select Link the store to this property.
You should see Link the store to this property ticked.
4. Connect Cloudflare
A browser step for a workspace admin. In Tracking, under Install storefront tracking:
- Select Connect Cloudflare and approve access on Cloudflare’s screen. Product Metrics asks only for Account Read, Zone Read, DNS Records Read, Workers Scripts Write, Workers Routes Write and Offline Access.
- Choose the Cloudflare account and the Cloudflare zone your shop domain is in.
- Select Set up gateway and keep the page open (usually under a minute).
Product Metrics then points its Lightspeed shop script at your domain. Nothing to paste into your theme. You should see Gateway setup complete.
5. Finish tracking setup
The setup checklist in Tracking opens each of these in turn:
- Consent: choose your banner (OneTrust, Cookiebot, Usercentrics or Osano). See Consent.
- Channels: connect Google Ads (with Data Manager access), Meta and ChatGPT Ads (OpenAI).
- Google Ads conversion actions: create them.
- Additional costs: product costs come from Lightspeed; add the rest, including payment fees.
You should see the badge next to Tracking read Tracking active.
6. Check it works
Place and pay for a test order, then follow Check tracking, or ask your assistant whether the order arrived. Under the Cloudflare gateway, Live endpoints lists the Tracking SDK and Event collector on your domain. The collector accepts only POST, so opening it in a browser isn’t a test.
You should see the Tracking SDK link return JavaScript, and your test order arrive.
How it works on Lightspeed
| On Lightspeed | |
|---|---|
| Install | Lightspeed API key and secret, plus Cloudflare approved once by a workspace admin |
| Order sent | When Lightspeed marks it paid |
| Product cost | Cost price on each order line; payment fees from your additional costs |
| Consent | OneTrust, Cookiebot, Usercentrics or Osano |
| Customer identity | Lightspeed’s new-customer flag and order history |
| Refunds | Lightspeed reports order, invoice and return changes; credit notes become a refund on the same order, a cancelled order is marked cancelled |
| Remove | Manage Lightspeed → Remove connection: type the hostname, tick the acknowledgement, confirm. The Cloudflare gateway is removed too |
What you get on Lightspeed
| Feature | Channels | On this platform |
|---|---|---|
| Server-side conversion tracking | Google Ads · Meta · ChatGPT Ads | Sent once paid (pay-on-pickup when paid); a Cloudflare gateway serves the script. |
| Enhanced Conversions | Google Ads · Meta · ChatGPT Ads | The email is hashed in the browser; sent only with ad user data consent. |
| Customer lists | Google Ads | Six Customer Match lists, filled from your Lightspeed orders. |
| POAS and ROAS bidding | Google Ads · Meta · ChatGPT Ads | Cost price per order line; payment fees from your additional costs. |
| New customer bidding | Google Ads · Meta | Lightspeed’s new-customer flag plus the customer’s order history. |
| Returning customer bidding | Google Ads · Meta | Orders from customers who bought before, as their own conversion. |
| LTV bidding | Google Ads · Meta · ChatGPT Ads | Observed value from paid orders, not a prediction. |
Troubleshooting
“The Lightspeed credentials could not be verified”
Check the cluster, Shop ID, key and secret, and that the key is enabled with the permissions in step 1.
“This store is already connected”
The shop is connected in another workspace. Remove that connection first, with its owner’s agreement.
Active, but publication stays pending
Wait and reopen Manage Lightspeed. If it stays pending, check the error shown or contact support.
“Proxy the storefront DNS record first”
Turn on the orange cloud for the shop’s DNS record in Cloudflare, then choose the zone again.
“Update the storefront domain first”
The zone doesn’t contain your shop domain. Select Change storefront domain, enter the hostname customers use without https://, and choose the zone again.
“Some permissions were not granted”
Select Connect Cloudflare again and approve every permission.
FAQ
Do I need a developer to set it up on Lightspeed?
No. You create an API key in the Lightspeed back office, enter it in Product Metrics and approve Cloudflare once. Product Metrics registers its order webhooks and adds its shop script for you; nothing goes into your theme.
Which Lightspeed shops does it work with?
Lightspeed eCom (C-Series), on the Europe or United States cluster.
How is Product Metrics billed on Lightspeed?
Connecting Lightspeed needs Pro, paid through a Stripe subscription. Server-side tracking is included in Pro, not billed separately.
Where do product costs come from on Lightspeed?
From the cost price on each Lightspeed order line. Lightspeed reports no payment fees, so add those with your other additional costs.