Skip to content
Google Ads

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.
  • Your Lightspeed eCom (C-Series) shop connected: a back-office administrator login (an API key can’t sign in), the shop’s cluster, hostname and numeric Shop ID, and an enabled API key with its secret that has Read on Content, Products, Customers and Orders, and Read and Write on Settings and Tracking. The shop can’t already be connected to another workspace, and it reads Active with Configuration is current before you link your property. See Lightspeed.
  • Your shop domain on Cloudflare, with its DNS record proxied (the orange cloud), and a workspace admin who signs in to Cloudflare once.

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.

Open Ecommerce platforms

Go to Integrations → Ecommerce platforms and select Connect on Lightspeed.

Ecommerce platforms under Integrations, listing the supported store platforms with a Connect button on Lightspeed.

Start the setup

The Lightspeed page lists three steps: connect your store, verify the connection and link a property. Select Connect Lightspeed.

The Lightspeed page under Integrations → Ecommerce platforms: 0 of 3 steps done, step 1 Connect your store with the Connect Lightspeed button, then Verify the connection and Link a property.

Enter your shop details

Choose the Cluster, then enter the Store hostname, Shop ID, API key and API secret. You create the API key in the Lightspeed back office under Settings → Store Settings → Developers.

The Connect Lightspeed dialog: Cluster set to Europe, then empty Store hostname, Shop ID, API key and API secret fields, each with where to find it in the Lightspeed back office, including the API key permissions, and the Cancel and Connect Lightspeed buttons.

Connect the store

Select Connect Lightspeed. Product Metrics checks the key, saves the connection, registers its order webhooks and detects your shop language.

The Lightspeed page after Connect Lightspeed, with the store's connection, credential and installation status.
Example data.

Follow the setup guide

Select Setup guide for every step in the Lightspeed back office, including the permissions the API key needs.

The Lightspeed setup guide panel in Product Metrics: every step in the Lightspeed back office, including the permissions the API key needs.

Google Ads: connect it in onboarding (Connect Google Ads and Merchant Center) or on Integrations, pick the client account that runs your campaigns and grant Data Manager access. See Google Ads.

Connect Google

On Connect Google Ads and Merchant Center, select Continue as your Google account and sign in with the account that can see your Google Ads. Tick Google Ads on Google’s screen: Merchant Center connects with the same sign-in.

The Connect step of onboarding, Connect Google Ads and Merchant Center: Google Ads and Merchant Center both Not connected, a Use our manager account link for when you can't sign in with that Google account, and the Continue as sam@northwind-outfitters.example button.
Example data.

Pick the client account

Choose the Google Ads client account that runs your campaigns, not a manager account. The workspace is named after the account you pick.

The account step of onboarding: the Google Ads accounts the signed-in Google account can see, to pick the one Product Metrics should analyse.
Example data.

Already have a workspace? Open Integrations and select Connect Google Ads on the Google Ads row (Add account once one is connected). The same sign-in and account steps follow.

Integrations in Product Metrics: the required connections first, Google Ads and Merchant Center with your product feed, each row with its status and one action.
Example data.

You should see: Connection status, Credential status and Installation status read Active, Configured and Active, publication reads Configuration is current, and the gateway says Gateway setup complete; your Google Ads account shows on Integrations.

In Product Metrics, open Tracking → Configure consent and choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. See Consent.

Open Tracking

Go to Integrations → Tracking. The checklist shows six steps: start by connecting your store, or use Cloudflare Tracking if you have no store platform.

Tracking in Product Metrics with the Complete your tracking setup checklist of six steps, starting with Connect your store.

Follow the next step

Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.

The Complete your tracking setup checklist in Tracking: 3 of 6 essential steps completed, with Connect your store, Link the store to this property and Install storefront tracking ticked, and Configure consent open as step 4 with the consent platform still Not configured.

Configure consent

Under Configure consent, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.

The Configure consent step in the tracking checklist, with the list of consent platforms to choose from.

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.

Create Google Ads conversions

Under Create Google Ads conversions, select Create 8 conversion actions. Product Metrics manages one Google Ads conversion action per purpose; they start as secondary goals, and you choose the primary goal in Google Ads.

The Conversion actions page in Product Metrics, opened from Tracking: Not configured, 0 of 8 managed and the Create 8 conversion actions button. Below it, Customer types (New customer revenue and profit, Returning customer revenue and profit) and Order value (Order revenue, Order profit), each Missing with Google goal status Unknown, and the Lifetime value group.

Then add your additional costs, so the profit actions carry profit.

Add your additional costs

Product costs come from your store where it reports them. Under Add your additional costs, add shipping, handling, returns and payment fees, set Product cost fallback (%) and select Activate additional costs, so the profit conversions carry real profit.

The Add your additional costs step in Tracking, prefilled for your country: shipping, handling, returns and payment fee fields, a Product cost fallback (%) field and the Activate additional costs button.

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.

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/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Paste 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.

How it works on Lightspeed

On Lightspeed
Script and collector served byA Cloudflare gateway (a Worker on your shop’s Cloudflare zone), as Lightspeed eCom has no app proxy. Product Metrics never changes your DNS
Purchase confirmed fromYour Lightspeed eCom orders
SentWhen Lightspeed marks the order paid (a pay-on-pickup order when it is paid)
DeliveredServer-side, through Google’s Data Manager, to the eight Product Metrics conversion actions
Refunds and cancellationsLightspeed reports order, invoice and return changes; credit notes become refunds and the Google Ads conversion is adjusted
Consent read fromOneTrust, Cookiebot, Usercentrics or Osano

Troubleshooting

ProblemFix
Orders are missing in Google AdsCheck 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

On the website: Full Signal Tracking, ad blocker conversion tracking check, first-party cookie, Product Metrics for Lightspeed

Developers: do the same with the CLI or the API.