Lightspeed server-side tracking for Google Ads
Send every purchase from your Lightspeed shop to Google Ads from the server, with the script served from your own domain.
Each purchase is confirmed from your Lightspeed eCom orders and sent to Google Ads from the server, through Google’s Data Manager. Nothing in the browser talks to Google, so an ad blocker has nothing to block.
Prerequisites
- Workspace admin in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking). Google Ads needs Merchant Center connected.
- A Lightspeed eCom (C-Series) administrator login (Europe or United States cluster) and an enabled API key with Read on Content, Products, Customers and Orders, and Read and Write on Settings and Tracking.
- Your shop domain on Cloudflare, DNS record proxied (the orange cloud), and a workspace admin who can sign in to Cloudflare.
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 Google Ads 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 Google Ads 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 Google Ads 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 Google Ads 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 Google Ads
- Store: add a Lightspeed API key in Product Metrics and sign in to Cloudflare for the gateway. See Lightspeed.
- Google Ads: under Ecommerce platforms, select your store → Connect Google Ads → Continue with Google, pick the client account that runs your campaigns and grant Data Manager access. See Google Ads.
You should see: Connection status, Credential status and Installation status read Active, Configured and Active, and the gateway says Gateway setup complete; Product Metrics lists your Google Ads account under your store.
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.
You should see: Configure consent names the banner your shop actually shows.
3. Create the conversion actions
In Product Metrics, select Tracking → Create Google Ads conversions → Create 8 conversion actions. All eight are secondary, so nothing changes in your campaigns until you make one primary. See Conversion actions.
Then add your additional costs, so the profit actions carry profit.
You should see: the badge next to Tracking reads Tracking active.
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. More checks: Check tracking works.
Troubleshooting
Orders are missing in Google Ads
Check that Tracking → Configure consent names the banner your store actually shows: Product Metrics sends an order only with the consent this page lists. See Consent.
FAQ
Why does Lightspeed tracking use Cloudflare?
Lightspeed eCom has no app proxy, so a Cloudflare gateway (a Worker on your shop’s Cloudflare 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 Google Ads?
When it is paid. Lightspeed orders are sent once Lightspeed marks them paid, not when they are placed.
Are Lightspeed credit notes sent to Google Ads?
Yes. Lightspeed reports order, invoice and return changes; credit notes become refunds and the Google Ads conversion is adjusted.
Will this change my Google Ads bidding straight away?
No. The eight Product Metrics conversion actions start as secondary, so nothing changes in your campaigns until you make one primary in Google Ads.
Where next
- Lightspeed: the full platform setup
- Google Ads: what Product Metrics sends and how to troubleshoot it
- Server-side tracking for Lightspeed in Meta: the same shop, the other channel
- Enhanced conversions for Lightspeed in Google Ads: add hashed customer data
- 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