> ## Documentation Index
> Fetch the complete documentation index at: https://f82cc46-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://f82cc46-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://f82cc46-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://f82cc46-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Lightspeed Customer Match lists in Google Ads (/docs/tracking/customer-lists/lightspeed-google-ads)

<!-- agent-signals: reading_time_min: 6 · est_tokens: 2262 · updated: 2026-11-16 -->
Related: [Customer Match lists in Google Ads on any website with Cloudflare](/docs/tracking/customer-lists/cloudflare-google-ads.md), [Magento Customer Match lists in Google Ads](/docs/tracking/customer-lists/magento-google-ads.md), [Shopify Customer Match lists in Google Ads](/docs/tracking/customer-lists/shopify-google-ads.md), [Shopware Customer Match lists in Google Ads](/docs/tracking/customer-lists/shopware-google-ads.md), [WooCommerce Customer Match lists in Google Ads](/docs/tracking/customer-lists/woocommerce-google-ads.md)

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



* **Store:** [Lightspeed](/docs/platforms/lightspeed). An API key from Lightspeed, then a Cloudflare sign-in.
* **Channel:** [Google Ads](/docs/channels/google-ads). Your Google Ads account, connected with Continue with Google.
* **Result:** Six Customer Match lists in Google Ads, updated after every paid order.

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics, with Pro (Full Signal Tracking). Google Ads needs [Merchant Center](/docs/using/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](/docs/platforms/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](/docs/channels/google-ads).

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

### 2. Set consent

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](/docs/concepts/consent).



![The Configure consent step with the consent platform list open: Not configured, Shopify Customer Privacy, OneTrust, Cookiebot, Usercentrics and Osano.](/docs/_assets/eb2d6e767cb722a4f9fc28ca607791b9b73c69ea9e416f3e8d76cb286dec18d6)

*Figure: 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](/docs/features/customer-list#the-six-lists)), 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.

## Set it up with AI



Paste the prompt into your assistant.



First connect the Product Metrics MCP server ([https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp); see [Connect your assistant](/docs/mcp/connect)).

**Claude or ChatGPT:** "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."

**Claude Code or Codex:** "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."

## How it works on Lightspeed

|                          | On Lightspeed                                                                                                                                                                           |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Customer**             | The customer on the Lightspeed order, else its email address, else its phone number                                                                                                     |
| **Counted orders**       | Paid Lightspeed orders                                                                                                                                                                  |
| **History**              | Each connected Lightspeed shop is counted on its own. A guest who later orders with an account starts again under their account.                                                        |
| **Sent to Google**       | Hashed email and phone and, when all four are known, hashed first and last name with unhashed country and postcode, from the Lightspeed order (the API key needs Read on **Customers**) |
| **High-value threshold** | Profit when every order in the window has known costs, else revenue. Set once 50 customers ordered in the last 365 days; recalculated every 30 days                                     |

Each member stays on a list for 540 days. Everything is hashed with SHA-256 and sent through Google's Data Manager. A privacy request that deletes a customer's data removes them from every list.

## Troubleshooting

| Problem                                                        | Fix                                                                                           |
| -------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| **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.

### Which cookie banners work with Lightspeed customer lists?

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

## Where next



* [Customer lists](/docs/features/customer-list): every platform, and what each error means
* [Lightspeed](/docs/platforms/lightspeed): the full store setup
* [Google Ads](/docs/channels/google-ads): conversion actions, Enhanced Conversions and troubleshooting
* [LTV bidding on Lightspeed in Google Ads](/docs/bidding/ltv/lightspeed-google-ads): bid on the same customers' lifetime value
* [New and returning customers](/docs/concepts/new-and-returning-customers): how a customer is recognised

On the website: [repeat purchase rate](https://www.productmetrics.io/glossary/repeat-purchase-rate), [pricing](https://www.productmetrics.io/pricing), [Product Metrics for Lightspeed](https://www.productmetrics.io/platforms/lightspeed)

Developers: do the same with the [CLI](/docs/cli/commands#google-ads) or the [API](/docs/api/google-ads/create-customer-lists).
