Skip to content
Customer lists

Lightspeed Customer Match lists in Google Ads

Create six Customer Match lists in Google Ads and keep them filled from Lightspeed, from first-time buyers to lapsed customers.

Product Metrics creates six Customer Match lists in your Google Ads account and keeps them up to date from your Lightspeed orders, moving each customer to the right lists after every paid order (for example from First-time buyers to Second-time buyers). You choose where to use them: Product Metrics never changes your campaigns.

Prerequisites

  • Workspace admin in Product Metrics, 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.
  • Google Ads connected to your property, with its conversion actions created and conversion tracking on in Google Ads, and a Google login allowed to manage the account, to accept the Customer Match terms. See Google Ads.

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.

Create the six Product Metrics customer lists for my Lightspeed shop in Google Ads and keep them filled. Check my setup status first, walk me through each open step, and give me the link when I need to click something.
Create the six Product Metrics customer lists for my Lightspeed shop in Google Ads and keep them filled. Check my setup status first, walk me through each open step, and give me the link when I need to click something.
Create the six Product Metrics customer lists for my Lightspeed shop in Google Ads and keep them filled. 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.
Create the six Product Metrics customer lists for my Lightspeed shop in Google Ads and keep them filled. 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 your Lightspeed shop recognises customers

To check a recent order, ask your assistant: “Are my last five Lightspeed orders from new or returning customers?”

You should see: whether your test order’s customer was recognised, as new or returning.

In Tracking → Configure consent, choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. A customer joins a list only when the visitor allowed both ad user data and ad personalisation. Leaving a list never needs consent: Product Metrics always removes a customer who no longer qualifies. See Consent.

The Configure consent step with the consent platform list open: Not configured, Shopify Customer Privacy, OneTrust, Cookiebot, Usercentrics and Osano.The Configure consent step with the consent platform list open: Not configured, Shopify Customer Privacy, OneTrust, Cookiebot, Usercentrics and Osano.
Configure consent: choose the banner your store shows visitors.

You should see: Configure consent names the banner your Lightspeed shop actually shows.

3. Accept the Customer Match terms

Google Ads only accepts customer lists once the account has accepted its Customer Match terms. You do this yourself in the Google Ads web interface.

You should see: creating the lists in the next step doesn’t fail with a Customer Match terms error.

4. Create the lists

Product Metrics creates the six lists (who joins each), or adopts matching ones it already manages, and tags each with its Google Ads customer type.

In Product Metrics, select Tracking → Google Ads → Customer lists → Create 6 customer lists.

You should see: all six lists created. If some lists exist already, the button reads Create 2 missing customer lists or Set up 1 customer list.

5. Use the lists in your campaigns

In Google Ads, the lists appear with your other audience lists as Product Metrics - [list] - [your store]. For example:

  • Exclude All customers from a campaign that should only find new customers.
  • Use Lapsed customers to win back customers who haven’t ordered in six months.
  • Tell Performance Max who your High-value customers are.

Customers join with their next paid order after the lists exist; the lists fill up from there.

You should see: the lists show members in Google Ads.

Troubleshooting

Creating the lists fails with a Customer Match terms error

Accept the Customer Match terms in the Google Ads web interface, then create the lists again.

FAQ

Are my existing Lightspeed customers added to the lists?

No. Customers join with their next paid order after the lists exist, and the lists fill up from there.

Which Lightspeed API key permissions do the lists need?

The same key that connects the shop: Read on Content, Products, Customers and Orders, and Read and Write on Settings and Tracking. The customer details sent to Google, hashed, come from the Lightspeed order and need Read on Customers.

How is a returning Lightspeed customer recognised?

By the customer on the Lightspeed order, else its email address, else its phone number. Each connected Lightspeed shop is counted on its own.

OneTrust, Cookiebot, Usercentrics or Osano. A customer joins a list only when the visitor allowed both ad user data and ad personalisation.

Where next

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