> ## Documentation Index
> Fetch the complete documentation index at: https://996f455-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://996f455-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://996f455-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://996f455-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Lightspeed enhanced conversions for Google Ads (/docs/tracking/enhanced-conversions/lightspeed-google-ads)

<!-- agent-signals: reading_time_min: 6 · est_tokens: 2157 · updated: 2026-11-16 -->
Related: [Shopify enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/shopify-google-ads.md), [WooCommerce enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/woocommerce-google-ads.md), [Magento enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/magento-google-ads.md), [Shopware enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/shopware-google-ads.md), [Enhanced conversions for Google Ads on any website with Cloudflare](/docs/tracking/enhanced-conversions/cloudflare-google-ads.md), [Shopify Meta Conversions API Advanced Matching](/docs/tracking/enhanced-conversions/shopify-meta.md)

> 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](/docs/using/team#1-choose-a-role)** in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking). Google Ads needs [Merchant Center](/docs/using/merchant-center) connected.
* **[Server-side tracking for Lightspeed in Google Ads](/docs/tracking/server-side/lightspeed-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



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

**Claude Code or Codex:** "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](/docs/tracking/server-side/lightspeed-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](/docs/using/consent#what-each-choice-lets-through).

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



![Two states of the Enhanced conversions card. Action required: Customer data terms Not accepted, with Open Google Ads settings and Re-check. Ready: Customer data terms Accepted, Enhanced conversions for leads On and Data Manager acceptance Accepted.](/docs/_assets/44b559493dce7db7f50904681df1f46acb236187a6420626f9d882590dca734d)

*Figure: Tracking → Google Ads → Enhanced conversions: Action required until the account accepts Google's customer data terms.*

1. In Product Metrics, open **Tracking → Google Ads**. Under **Enhanced conversions**, look at **Customer data terms**.
2. If it reads **Not accepted**, select **Open Google Ads settings**. Under **Customer data terms**, choose **View terms** and agree.
3. 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.
4. Select **Re-check** in Product Metrics.



> **Note:** 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](#2-set-consent)).

## 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](/docs/platforms/lightspeed): the full platform setup
* [Server-side tracking for Lightspeed in Google Ads](/docs/tracking/server-side/lightspeed-google-ads): the step before this one
* [Meta Conversions API on Lightspeed](/docs/tracking/enhanced-conversions/lightspeed-meta): the same customer data, sent to Meta
* [Google Ads](/docs/channels/google-ads): the channel setup and troubleshooting
* [Enhanced Conversions](/docs/features/enhanced-conversions): every platform and channel
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [GCLID](https://www.productmetrics.io/glossary/gclid), [Product Metrics for Lightspeed](https://www.productmetrics.io/platforms/lightspeed)

Developers: do the same with the [CLI](/docs/cli/commands#stores-and-tracking) or the [API](/docs/api/stores-and-tracking/tracking-get-enhanced-conversions).
