Ecommerce platform
Product MetricswithLightspeed
Server-side tracking for Lightspeed eCom, built for POAS bidding on Google Ads and Meta.
Connect your Lightspeed eCom (C-Series) shop to Product Metrics. Every paid order then reaches Google Ads and Meta from your own shop domain, confirmed from Lightspeed, with its revenue, profit, customer type and lifetime value.
Log in with Google, no credit card
- Every ad blocker
- Your own store domain
- Included in Pro
What every Lightspeed order sends
Order #1042Paid
- Revenue
- €139.99
- Profit
- €50.91
- Customer
- New
- Lifetime value
- €420
- Sent fromyourshop.com/…
- Through every ad blocker
- Google AdsReceived
- MetaReceived
POAS bidding on both
Illustrative data
Compare
A browser tag or Product Metrics on Lightspeed. What reaches Google Ads and Meta.
| What counts | Product Metrics on LightspeedFull Signal Tracking, server-side | A browser tag / GTMGoogle tag, Google Tag Manager or Meta Pixel |
|---|---|---|
| Ad blockers | Gets through every ad blocker | Blocked, also behind Google tag gateway or server-side GTMSee the ad blocker test |
| Safari ITP | First-party cookie lasts 30 days | Tags load, cookies cut to 7 days |
| Where it runs | Server-side, from your own shop domain | In the visitor’s browser |
| Purchases | Confirmed from the Lightspeed order; refunds adjust | As the browser reports them |
| Profit | From the cost price on each order line | Order value only |
| New customers | Marked new or returning, with lifetime value | Not marked by default |
| POAS bidding | On Google Ads and MetaGoogle AdsMeta | Not without profit in the conversion |
- Yes
- Partly or not by default
- No
Why it pays
What it adds to your Lightspeed store. Profit, every purchase, new customers.
Bid on profit with POAS
Google AdsMetaEach order reaches Google Ads and Meta with its profit, so both can bid on POAS. It works on ROAS right away; connect margins to switch to POAS.
POAS vs ROASEvery purchase counts
Full Signal Tracking gets through every ad blocker. It runs on a unique endpoint on your own domain that auto-rotates if it is ever blocked.
How Full Signal Tracking worksWin new customers
Google AdsMetaEach purchase is marked new or returning, with its lifetime value, so Google Ads and Meta can tell first orders apart and bid for new customers.
MER and nCAC calculator
Trusted by ecommerce teams running Google Shopping at
- DocHorse
- Rajapack
- Soundimports
- FDX.com
- beterwitgoed.nl
- snackje.nl
- 1M+ products analysed
- €750K+ monthly Shopping spend under management
- Founder's work nominated at the Dutch Search Awards: Best Measurement Campaign 2023 · Best Use of Data 2024
POAS
Same ROAS, different profit. POAS shows which product pays.
POAS = ROAS × contribution margin %. At a POAS of 1 a product breaks even; above 1 it earns more than its ads cost.
Product A
- ROAS
- 4
- Contribution margin
- 40%
- POAS
- 1.6
After €100 of ads:Earns €60
Product B
- ROAS
- 4
- Contribution margin
- 20%
- POAS
- 0.8
After €100 of ads:Loses €20
Illustrative data
Work out your POASInstall
Live in 4 easy steps. Then approve Cloudflare once.
Log in with Google, no credit card
- Create API credentials in Lightspeed
- Connect the shop in Product Metrics
- Approve Cloudflare
- Pick your purchase conversion action
Step details and who does it
- 1.Create API credentials in LightspeedIn your Lightspeed back office, create an API key and secret with read access to orders, customers, products and content, and write access to settings and tracking.
- 2.Connect the shop in Product MetricsIn Workspace → Ecommerce Platforms, pick your cluster (EU or US) and enter your shop domain, Store ID, API key and secret. Product Metrics adds its order webhooks and the shop script.
- 3.Approve CloudflareAuthorise Cloudflare and pick the zone your shop domain runs on. Product Metrics adds a small relay there that serves tracking from your own domain.
- 4.Pick your purchase conversion actionConnect Google Ads in Workspace → Tracking and choose where purchases land.
Who does it
Someone with access to the Lightspeed back office and to the Cloudflare account that serves the shop’s domain.
At a glance
How it runs on Lightspeed. What runs where.
- Install
- Lightspeed listing, or connect in Workspace → Ecommerce Platforms with your Lightspeed API key and secret
- Tracking endpoint
- A relay on your Cloudflare zone serves script and collector on random paths on your shop domain
- Consent
- Cookiebot, OneTrust, Usercentrics or Osano, as Consent Mode v2 signals
- Orders and refunds
- Order, invoice and return webhooks, then a read through the Lightspeed API; credit notes included
- Cost price
- The cost price on each Lightspeed order line
- New customers
- Lightspeed’s new-customer flag and the customer’s order history
- Versions
- Lightspeed eCom (C-Series), EU and US clusters
Your endpoint runs on your own shop domain. Through a relay on your Cloudflare zone.
Product Metrics serves tracking through the Cloudflare account your shop domain already runs through. A relay Worker on your zone serves the script and the collector on random paths of your own shop domain, and signs every request it passes on.
An adblocker sees a request to your own shop, not to a tracking domain.
- Adblocker benchmark: which blockers stop the standard Google tags, tested with the real extensions.
Consent comes from your consent tool. Denied until the visitor agrees.
Pick Cookiebot, OneTrust, Usercentrics or Osano in Product Metrics. The visitor’s analytics and marketing choices reach Google Ads as Consent Mode v2 signals; until the visitor chooses, everything stays denied.
The email address is hashed in the browser before it is sent.
Orders come from Lightspeed, not from the browser. A purchase counts once it is paid.
Lightspeed sends a webhook when an order, invoice or return changes. Product Metrics then reads the order through the Lightspeed API: its products, invoices, shipments, returns and the customer. A purchase reaches Google Ads and Meta once Lightspeed marks the order paid, so a pay-on-pickup order counts when it is paid.
Credit notes, which Lightspeed records as negative invoices, become a refund on the same order, and a cancelled order is marked cancelled.
Lightspeed’s cost price becomes profit per order. From every order line.
Lightspeed keeps a cost price on each order line. Product Metrics reads it with the order, so each purchase reaches Google Ads and Meta with its profit. Lines without a cost use the cost in Merchant Center or your cost settings.
Product Segmentation works on ROAS straight away. Connect margins to switch it to POAS.
- Break-even ROAS calculator: the return each product needs from its price and costs.
New customers are marked before Google Ads and Meta see them. With profit and lifetime value.
Lightspeed flags a customer’s first order, and Product Metrics checks the customer’s order history as well. The first paid order makes a new customer; every later one is returning.
Each purchase reaches Google Ads and Meta marked new or returning, with its revenue, profit and lifetime value. In Google Ads, that is eight conversion actions Product Metrics creates and manages for you:
- Product Metrics - New Customer
- New Customer Profit
- Returning Customer
- Returning Customer Profit
- Revenue
- Profit
- Revenue LTV
- Profit LTV
Product Metrics shows nCAC, what you pay for a new customer, per product and as an average, so you can increase priority on products that bring in first orders.
- MER and nCAC calculator: work out nCAC from your own totals.
Google Shopping for Lightspeed shops. Keep your feed, add the signal.
Your Lightspeed products reach Google Shopping through a product feed in Merchant Center. Keep the feed you use: Product Metrics is not a feed tool.
Product Metrics adds what Google Ads learns from: every paid Lightspeed order sent server-side as new or returning with its profit, and your products segmented by clicks and return into Merchant Center labels that your Shopping and Performance Max campaigns use.
- Product Segmentation: products segmented by clicks and return, written to Merchant Center labels.
Requirements and limits. What to check before you connect.
- Lightspeed eCom (C-Series), on the EU or US cluster.
- A shop domain that runs through Cloudflare, with its DNS record proxied, and access to that Cloudflare account.
- An API key and secret with the permissions listed in the first step.
- Payment fees aren’t available from Lightspeed; they come from your cost settings.
Questions about Lightspeed. Short answers.
Does it send Lightspeed orders to Meta too?
Do I need margin data to start?
Which Lightspeed product does Product Metrics work with?
Why does Lightspeed need Cloudflare?
What happens with pay-on-pickup orders?
Will Google Ads count orders twice next to my current tag?
Is Product Metrics an attribution tool?
Does it get through adblockers?
Other platforms
Product Metrics on other platforms. Same tracking, each platform’s own setup.
Shopify
Install the app from the Shopify App Store. Orders go to Google Ads and Meta from your own store domain, with profit from the costs you keep in Shopify.
WooCommerce
Install a WordPress plugin and paste a token. Orders go to Google Ads and Meta from your own domain, with profit from your WooCommerce costs.
Magento
Install the module for your Magento version, OpenMage included. Orders go to Google Ads and Meta from your own domain, with profit from your Magento costs.
Shopware 6
Install the Shopware 6 plugin and paste a token. Orders go to Google Ads and Meta from your own domain, with profit from your Shopware purchase prices.
Keep exploring
Related pages.
Full Signal Tracking
How server-side, auto-rotating tracking works on every platform.
Adblocker benchmark
Which blockers stop the standard Google tags, tested with the real extensions.
Product Segmentation
Products segmented by clicks and return, written to Merchant Center labels.
Break-even ROAS calculator
The return each product needs from its price and costs.
See your products’ profit in Google Ads. Start with a free analysis.
Not ready to connect? Book a demo: a video call with Berend, then a demo account.