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

# Lightspeed server-side tracking with the Meta Conversions API (/docs/tracking/server-side/lightspeed-meta)

<!-- agent-signals: reading_time_min: 9 · est_tokens: 3566 · 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), [Lightspeed server-side tracking for Google Ads](/docs/tracking/server-side/lightspeed-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)

> Send every purchase from your Lightspeed shop to Meta from the server through the Meta Conversions API, with Advanced Matching and the script served from your own domain.

Each purchase is confirmed from **your Lightspeed eCom orders** and sent to your Meta pixel [from the server](/docs/concepts/server-side-tracking), through the **Meta Conversions API**. Nothing in the browser talks to Meta, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block. Each event carries hashed customer data for [Advanced Matching](/docs/tracking/enhanced-conversions/lightspeed-meta).



* **Store:** [Lightspeed](/docs/platforms/lightspeed). An API key from Lightspeed, then a Cloudflare sign-in.
* **Channel:** [Meta](/docs/channels/meta). Your pixel ID and a Conversions API access token.
* **Result:** Every paid order sent to your pixel through the Meta Conversions API.

## 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).
* **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.
* **Access to your pixel in Meta Events Manager**, to copy its ID and generate a Conversions API access token.

## In the app

### 1. Connect Lightspeed and Meta

**Store:** add a Lightspeed API key in Product Metrics and sign in to Cloudflare for the gateway, then link the shop to your property. 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)

**Meta:** in Events Manager, copy your **Pixel or Dataset ID** and generate a Conversions API access token, then add both under **Tracking → Meta Conversions API → Connect Meta** and send a test event. See [Meta](/docs/channels/meta).



1. **Open Tracking.** Go to **Integrations → Tracking**. Under **Destinations**, select **Meta Conversions API**.

2. **Open the Meta panel.** The panel lists the events Product Metrics sends and what you need: a **Pixel or Dataset ID** and a Conversions API access token from Events Manager. Select **Connect Meta**.

   ![The Meta Conversions API panel, Not configured: Product Metrics sends AddToCart, InitiateCheckout and Purchase from the server to your Meta pixel, with hashed customer data when the shopper consented to marketing, plus revenue, profit, new and returning customer, and LTV events, which also need analytics consent. You need a Pixel or Dataset ID and a Conversions API access token from Events Manager. A Connect Meta button.](/docs/_assets/588444f715d3715f2be502402cee6218f721840965f4655380f205de3a834a9f)

3. **Add the Meta destination.** Choose the store, enter the **Pixel or Dataset ID** and the **Access token**, and optionally a **Test event code**. Keep **Send events to Meta** on and select **Add destination**.

   ![The Add Meta destination dialog for the example store Northwind Outfitters: empty Pixel or Dataset ID, Access token and Test event code (optional) fields, each with where to find it in Events Manager, the Send events to Meta switch on, and the Cancel and Add destination buttons.](/docs/_assets/a946724528c7a47f16adc5a3c1fd5e75b1f9b498c20142415a3e07e2cf4f656e)

   *Example data.*

4. **Create custom conversions in Meta.** In Events Manager, create a custom conversion for each Product Metrics event you want to measure, using the event names listed in the panel.

   ![The Set up custom conversions in Meta section of the Meta Conversions API panel: the steps in Events Manager, then a table of each conversion and its event: New customer revenue PMNewCustomer, New customer profit PMNewCustomerProfit, Returning customer revenue PMReturningCustomer, Returning customer profit PMReturningCustomerProfit and Order revenue PMOrderRevenue.](/docs/_assets/8d13436ae8d16e27fcb8fb31e6e842bead9c4d5d6afdb6dcd0b921af7e846079)

**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**; Events Manager shows the test event under **Test events**.

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



> **Warning:** Meta has no consent mode. Product Metrics sends an event only when the visitor allowed ad user data; the custom events also need analytics consent. A wrong banner here means nothing reaches Meta.

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

### 3. Create custom conversions

In Events Manager, create a custom conversion for each Product Metrics value you want to bid on, with the rule `pm_purpose` equals the purpose: `PMOrderRevenue` (`ORDER_REVENUE`) for revenue, `PMOrderProfit` (`ORDER_PROFIT`) for profit, every other event in [Meta events](/docs/concepts/conversion-actions-and-events#meta-events). Follow [Create custom conversions in Meta](/docs/using/conversion-actions#custom-conversions-in-meta) once a test order has reached Meta.

**You should see:** your custom conversions show in Events Manager.

### 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; in Events Manager, the order shows as `Purchase`, plus the Product Metrics custom events your visitor's consent allows. 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 Meta 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 Meta 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 the Meta Conversions API: `Purchase` plus the Product Metrics custom events                                            |
| **Refunds and cancellations**      | Sent events aren't revised. Meta refuses events more than 7 days old                                                                        |
| **Consent read from**              | OneTrust, Cookiebot, Usercentrics or Osano                                                                                                  |

## Troubleshooting

| Problem                                                  | Fix                                                                                                                             |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **The event isn't in Meta's custom conversion selector** | Meta lists an event only after it received it. Place a test order with all cookies accepted, then create the custom conversion. |

## FAQ

### Why does Lightspeed tracking for Meta use Cloudflare?

Lightspeed eCom has no app proxy, so a Cloudflare gateway on your shop's 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 Meta?

When Lightspeed marks it paid. Meta refuses events more than 7 days old, so an order paid later than that doesn't reach Meta.

### Can I keep the Meta pixel on my Lightspeed shop?

Yes. Meta counts an event once when the pixel and the Meta Conversions API send the same event name and event ID within 48 hours. `Purchase` uses the order transaction ID, so it deduplicates on its own.

### Do Lightspeed credit notes change the Meta event?

No. Sent Meta events aren't revised. Credit notes adjust the Google Ads conversion only.

## Where next



* [Lightspeed](/docs/platforms/lightspeed): the full platform setup
* [Meta](/docs/channels/meta): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for Lightspeed in Google Ads](/docs/tracking/server-side/lightspeed-google-ads): the same shop, the other channel
* [Meta Conversions API on Lightspeed](/docs/tracking/enhanced-conversions/lightspeed-meta): the customer data each event carries
* [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#destinations) or the [API](/docs/api/destinations/set-meta).
