--- title: "Lightspeed eCom Server-Side Tracking | Product Metrics" description: "Server-side tracking for Lightspeed eCom. Every paid order reaches Google Ads and Meta from your shop domain, through every ad blocker, with its profit for POAS bidding." canonical: "https://www.productmetrics.io/platforms/lightspeed" pageType: integration language: en publisher: "Product Metrics" dateModified: 2026-10-22 --- > Content index: https://www.productmetrics.io/llms.txt # 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. - Every ad blocker - Your own store domain - Included in Pro ## What every Lightspeed order sends Order #1042: | Signal | Value | | --- | --- | | Revenue | €139.99 | | Profit | €50.91 | | Customer | New | | Lifetime value | €420 | - Sent from yourshop.com/… - Through every ad blocker - Google Ads: Received - Meta: Received - POAS bidding on both _Illustrative data_ ## A browser tag or Product Metrics on Lightspeed. What reaches Google Ads and Meta. A browser tag and Product Metrics on Lightspeed compared: | What counts | A browser tag / GTM | Product Metrics on Lightspeed | | --- | --- | --- | | Ad blockers | ✗ Blocked, also behind Google tag gateway or server-side GTM | ✓ Gets through every ad blocker | | Safari ITP | — Tags load, cookies cut to 7 days | ✓ First-party cookie lasts 30 days | | Where it runs | — In the visitor’s browser | ✓ Server-side, from your own shop domain | | Purchases | — As the browser reports them | ✓ Confirmed from the Lightspeed order; refunds adjust | | Profit | — Order value only | ✓ From the cost price on each order line | | New customers | — Not marked by default | ✓ Marked new or returning, with lifetime value | | POAS bidding | ✗ Not without profit in the conversion | ✓ On Google Ads and Meta | - [See the ad blocker test](https://www.productmetrics.io/ad-blocker-conversion-tracking) ## What it adds to your Lightspeed store. Profit, every purchase, new customers. - **Bid on profit with POAS.** Each 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. - **Every 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. - **Win new customers.** Each 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. - [POAS vs ROAS](https://www.productmetrics.io/blog/poas-vs-roas) - [How Full Signal Tracking works](https://www.productmetrics.io/server-side-tracking) - [MER and nCAC calculator](https://www.productmetrics.io/mer-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 ## 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 | ROAS | Contribution margin | POAS | After €100 of ads | | --- | --- | --- | --- | --- | | Product A | 4 | 40% | 1.6 | Earns €60 | | Product B | 4 | 20% | 0.8 | Loses €20 | _Illustrative data_ - [Work out your POAS](https://www.productmetrics.io/poas-calculator) ## Live in 4 easy steps. Then approve Cloudflare once. 1. **Create API credentials in Lightspeed.** In 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 Metrics.** In 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 Cloudflare.** Authorise 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 action.** Connect 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. - [Analyse your products for free](https://app.productmetrics.io/): Log in with Google, no credit card ## How it runs on Lightspeed. What runs where. Product Metrics on Lightspeed: | | Lightspeed | | --- | --- | | 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](https://www.productmetrics.io/ad-blocker-conversion-tracking): 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](https://www.productmetrics.io/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](https://www.productmetrics.io/mer-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](https://www.productmetrics.io/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? Yes. Full Signal Tracking sends revenue, profit, new and returning customers and lifetime value to Google Ads and Meta, so POAS bidding works on both. ### Do I need margin data to start? No. It works on ROAS right away; connect margins to switch to POAS. Full Signal Tracking is included in the Pro subscription. ### Which Lightspeed product does Product Metrics work with? Lightspeed eCom, the C-Series webshop platform, on the EU and US clusters. ### Why does Lightspeed need Cloudflare? To serve tracking from your own shop domain. Product Metrics adds a relay to the Cloudflare zone your domain runs through, and the shop script loads tracking from there. ### What happens with pay-on-pickup orders? They reach Google Ads and Meta once Lightspeed marks them paid, with the amount on the order. ### Will Google Ads count orders twice next to my current tag? The order is sent as the transaction ID. Google Ads deduplicates matching IDs within the same conversion action. If your existing tag uses a separate purchase action, choose which purchase action is primary for bidding and keep the other secondary; the ID alone does not deduplicate across actions. ### Is Product Metrics an attribution tool? No. It sends every confirmed purchase to Google Ads and Meta, with consent, so their bidding learns from all of them. It doesn’t share credit across channels. ### Does it get through adblockers? Yes. Full Signal Tracking runs on a unique endpoint on your own domain, and if that endpoint is ever blocked, it auto-rotates to a fresh one. Consent still decides what is sent. ## Product Metrics on other platforms. Same tracking, each platform’s own setup. - [Shopify](https://www.productmetrics.io/platforms/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](https://www.productmetrics.io/platforms/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](https://www.productmetrics.io/platforms/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](https://www.productmetrics.io/platforms/shopware): 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. ## Related pages. - [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking): how server-side, auto-rotating tracking works on every platform - [Adblocker benchmark](https://www.productmetrics.io/ad-blocker-conversion-tracking): which blockers stop the standard Google tags, tested with the real extensions - [Product Segmentation](https://www.productmetrics.io/product-segmentation): products segmented by clicks and return, written to Merchant Center labels - [Break-even ROAS calculator](https://www.productmetrics.io/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. - [Analyse your products for free](https://app.productmetrics.io/): Free analysis, no credit card - [Find your hidden profit](https://www.productmetrics.io/pricing#calculator): 30-second estimate · no login - [Book a demo](https://cal.com/berend-vrakking/demo): a video call with Berend, then a demo account --- Published by Product Metrics (Berend Vrakking, founder). HTML version: https://www.productmetrics.io/platforms/lightspeed