Lightspeed enhanced conversions for Google Ads
Send hashed customer data from Lightspeed orders with each Google Ads conversion, only when the visitor allowed ad user data.
On Lightspeed, Product Metrics hashes email, phone, name and address from the Lightspeed order with SHA-256 and sends it with each purchase conversion through Google’s Data Manager, only when the visitor allowed ad user data. There is no Google tag setting and no code.
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.
- Server-side tracking for Lightspeed in Google Ads set up first. It needs a Lightspeed eCom (C-Series) administrator login (Europe or United States cluster) with an enabled API key that has Read on Content, Products, Customers and Orders, and Read and Write on Settings and Tracking; and your shop domain on Cloudflare, DNS record proxied (the orange cloud), with a workspace admin who can sign in to Cloudflare.
- Admin access to the Google Ads account, to accept the customer data terms.
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.
Turn on Enhanced Conversions 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.Turn on Enhanced Conversions 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.Turn on Enhanced Conversions 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.Turn on Enhanced Conversions 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. Check server-side tracking runs
Enhanced conversions are not a separate switch: once the shop sends orders to the Product Metrics conversion actions, each order carries the customer data it has.
You should see: every Product Metrics conversion action created under Tracking → Conversion actions. If not, finish server-side tracking for Lightspeed in Google Ads.
2. Set consent
In Tracking → Configure consent, choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. What each choice lets through: Consent.
You should see: Tracking → Configure consent names the banner your shop actually shows.
3. Accept Google’s customer data terms
Google rejects conversions with customer data until the account accepts its terms. Only you can do this, in Google Ads.
- In Product Metrics, open Tracking → Google Ads. Under Enhanced conversions, look at Customer data terms.
- If it reads Not accepted, select Open Google Ads settings. Under Customer data terms, choose View terms and agree.
- If Data Manager acceptance reads Rejected, select Turn on enhanced conversions. In Google Ads, open Goals → Settings, expand Customer data use, tick Turn on enhanced conversions, then agree and save.
- Select Re-check in Product Metrics.
If Product Metrics says Terms are managed on account with another number, that is your manager account. Accept the terms there.
You should see: Ready under Enhanced conversions. Re-check runs a new check. What each state means:
| In the app | What to do |
|---|---|
| Ready | Nothing. Customer data goes with every consented order. |
| Setting up | Wait. Data Manager needs about 15 minutes to recognise new conversion actions. |
| Action required | Accept the customer data terms, or turn on enhanced conversions (step 3). |
| Check failed | Reconnect Google Ads, or select Re-check in a moment. |
| Not checked yet | Open Tracking → Google Ads and select Re-check. |
| No Google Ads account | Connect Google Ads first. |
4. Check an order
Place and pay for a test order.
You should see: the order for the linked property, and under the Cloudflare gateway in Tracking, Live endpoints lists the Tracking SDK and Event collector on your shop domain.
Fields sent
| Customer data | Where it comes from on Lightspeed | Sent to Google Ads as |
|---|---|---|
| Email address | The Lightspeed order; hashed in the browser before it is sent | Hashed email |
| Phone number | The Lightspeed order | Hashed phone, with the country code and + |
| Name, country and postcode | The Lightspeed order’s address | Hashed first and last name, with country and postcode, only as a complete set |
| Ad click | The visitor’s click on your ad | gclid, gbraid or wbraid, with ad storage consent |
| New or returning customer | The customer’s order history | Sent with the conversion |
Product Metrics only sends what the order already has. It adds no checkout fields and guesses nothing.
Troubleshooting
Orders are missing in Google Ads
Check that Tracking → Configure consent names the banner your store actually shows (step 2).
FAQ
Do I need Google Tag Manager for Enhanced Conversions?
No. Product Metrics sends the hashed customer data server-side with each order through Google’s Data Manager, so there is no Google tag setting and no code on your Lightspeed shop.
Is the email hashed in the browser on Lightspeed?
Yes. The email is hashed with SHA-256 in the browser before it is sent. Phone, name and address from the Lightspeed order are hashed too.
Which consent banners work on Lightspeed?
OneTrust, Cookiebot, Usercentrics or Osano. Choose the one your shop shows under Tracking → Configure consent.
What if a visitor declines ad user data?
Google Ads still receives the order when the visitor allowed ad storage, but without the hashed customer data. With neither ad user data nor ad storage, the order isn’t sent.
Where next
- Lightspeed: the full platform setup
- Server-side tracking for Lightspeed in Google Ads: the step before this one
- Meta Conversions API on Lightspeed: the same customer data, sent to Meta
- Google Ads: the channel setup and troubleshooting
- Enhanced Conversions: every platform and channel
- On the website: Full Signal Tracking, first-party cookie, GCLID, Product Metrics for Lightspeed