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

# Lightspeed server-side tracking for Google Ads (/docs/tracking/server-side/lightspeed-google-ads)

<!-- agent-signals: reading_time_min: 10 · est_tokens: 4028 · updated: 2026-11-17 -->
Related: [Shopify server-side tracking for Google Ads](/docs/tracking/server-side/shopify-google-ads.md), [WooCommerce server-side tracking for Google Ads](/docs/tracking/server-side/woocommerce-google-ads.md), [Magento server-side tracking for Google Ads](/docs/tracking/server-side/magento-google-ads.md), [Shopware server-side tracking for Google Ads](/docs/tracking/server-side/shopware-google-ads.md), [Server-side tracking for Google Ads on any website with Cloudflare](/docs/tracking/server-side/cloudflare-google-ads.md), [Shopify server-side tracking with the Meta Conversions API](/docs/tracking/server-side/shopify-meta.md)

> 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](/docs/concepts/server-side-tracking), through Google's **Data Manager**. Nothing in the browser talks to Google, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block.



* **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:** Every paid order sent server-side to the eight **Product Metrics** conversion actions.

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

## 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](/docs/platforms/lightspeed).



1. **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.](/docs/_assets/0c05b9d4decc1de6535ef457c54dfe27804efbe9a7b5ca7c20d0a46bb3f8ff15)

2. **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.](/docs/_assets/8d91ee07b543eef0b937594ab6d687baf56be4cedec1b58cec69f9a34376b52d)

3. **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.](/docs/_assets/11453e2e2b52149b29209d41615ebfae944f3ad5954e9e11c06183e9cbd9e1a4)

4. **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.](/docs/_assets/6102e9bc56937e92684b3c198bcd8b98d1430bb9cc855791abe843bfb265eb29)

   *Example data.*

5. **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.](/docs/_assets/bad196dcafbc326d06548c2adc21db9d10b37fd1f653881f22abdf9be16fd627)

**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](/docs/channels/google-ads).



1. **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.](/docs/_assets/0d2be369dbe5104c735cd1c7373a8e7ff08264ebea02c129bd51097490f525e3)

   *Example data.*

2. **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.](/docs/_assets/0e327319a8a785046273763a2be1b6d2c546e1fa773c5ec87ee2c64687e06c9c)

   *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.](/docs/_assets/e7a64e8fb340c3708610b6de560704e9a8c3bbc87fbac246c364f0024392700d)

*Example data.*

**Connect through our manager account instead**

Use this when you can't sign in with a Google account that can see your Google Ads. Product Metrics' manager account invites your Google Ads account, with access to that one account only.

1. **Choose the manager account.** On the **Connect** step, select **Use our manager account**.

   ![The Connect step of onboarding with the Use our manager account link, for when you can't sign in with the Google account that sees your Google Ads.](/docs/_assets/4795c769c1dc46b2348ec5796a84155e4bb0f4d0de7212fffd32ca30801c7727)

2. **Name the workspace.** Enter a name for the workspace the invite belongs to, then select **Continue**.

   ![The workspace name field of the manager account route, with the Continue button.](/docs/_assets/4fa654128e9a60d95e2ae0545925409921419a320e8b5f14f87d092342f2b85e)

3. **Enter your customer ID.** Enter your Google Ads customer ID and select **Send invite**.

   ![The Use our manager account form on the Connect step: enter the account's customer ID and send the invite, the account owner accepts it in Google Ads under Admin → Access and security → Managers, and Product Metrics checks access every 2 minutes. A Google Ads customer ID field, a Check access link, Connect with Google instead, and the Send invite button.](/docs/_assets/eaee093b9a33fc6b0e91382fb830909287363dcdfbdccd09a822b1be7a2fb4c1)

4. **Accept the invite in Google Ads.** In Google Ads, open **Admin → Access and security → Managers** and accept the invite. Product Metrics checks access every few minutes and starts the analysis once it has access.

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

### 2. Choose your consent banner

In Product Metrics, open **Tracking → Configure consent** and choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. See [Consent](/docs/concepts/consent).



1. **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.](/docs/_assets/09a584afb1797a0439b68310c4d6085412eafebba1524c019f42a90f3ed4ea37)

2. **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.](/docs/_assets/b385237058280a34dca53f7f1e42704faa9a8aee59024bd5baafc2211e201e7e)

3. **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.](/docs/_assets/f0a8d61eaa086657ce840c85899df48d5f3a7a52fb6c552710f93b1482b90e72)

**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](/docs/using/conversion-actions).



1. **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.](/docs/_assets/816fdc81f1068f5d013a17d0d26166a0834cc61c69943d0c05d5171b557e0652)

Then [add your additional costs](/docs/using/costs), so the profit actions carry profit.



1. **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.](/docs/_assets/9aa53f961b1d7a0f43c3ebdccb7dfda4cb044d52cf5c7d4cd3b10fc95a7083fb)

**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](/docs/using/check-tracking).

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

**Claude Code or Codex:** "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 by** | A 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 from**        | Your Lightspeed eCom orders                                                                                                                 |
| **Sent**                           | When Lightspeed marks the order paid (a pay-on-pickup order when it is paid)                                                                |
| **Delivered**                      | Server-side, through Google's Data Manager, to the eight **Product Metrics** conversion actions                                             |
| **Refunds and cancellations**      | Lightspeed reports order, invoice and return changes; credit notes become refunds and the Google Ads conversion is adjusted                 |
| **Consent read from**              | OneTrust, Cookiebot, Usercentrics or Osano                                                                                                  |

## Troubleshooting

| Problem                              | Fix                                                                                                                                                                                             |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Orders are missing in Google Ads** | Check 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](/docs/concepts/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



* [Lightspeed](/docs/platforms/lightspeed): the full platform setup
* [Google Ads](/docs/channels/google-ads): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for Lightspeed in Meta](/docs/tracking/server-side/lightspeed-meta): the same shop, the other channel
* [Enhanced conversions for Lightspeed in Google Ads](/docs/tracking/enhanced-conversions/lightspeed-google-ads): add hashed customer data
* [Server-side conversion tracking](/docs/features/ad-blocker-proof-tracking): every platform and channel

On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [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-conversion-actions).
