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

# Lightspeed customer data for ChatGPT Ads (OpenAI Conversions API) (/docs/tracking/enhanced-conversions/lightspeed-openai)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1953 · 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), [Lightspeed enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/lightspeed-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)

> Send hashed customer data from Lightspeed orders with each ChatGPT Ads event through the OpenAI Conversions API, so ChatGPT Ads can match conversions to people.

With the **OpenAI Conversions API**, every event Product Metrics sends to your ChatGPT Ads pixel carries the shopper's **customer data from the Lightspeed order**, hashed with **SHA-256**, and **browser references**, so ChatGPT Ads can match the conversion to the person who saw or clicked the ad. There is no separate switch: once ChatGPT Ads is connected, each event the visitor consented to includes it.

## Prerequisites

* **[Editor or admin](/docs/using/team#1-choose-a-role)** on the property in Product Metrics, 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 ChatGPT Ads Manager → Conversions**, to copy your Pixel ID and create a Conversions API key.

## 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:** "Check that Product Metrics sends customer data with my ChatGPT Ads events from my Lightspeed shop. 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:** "Check that Product Metrics sends customer data with my ChatGPT Ads events from my Lightspeed shop. 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. Connect your shop and ChatGPT Ads

Connect your shop with [Lightspeed](/docs/platforms/lightspeed). For [ChatGPT Ads](/docs/channels/openai), copy your **Pixel ID** in Ads Manager → **Conversions** and create a Conversions API key, then add both under **Tracking → OpenAI Conversions API → Connect OpenAI**.



![The Add OpenAI destination form with Pixel ID, Conversions API key and the Send events to OpenAI switch, then the saved OpenAI Conversions API destination showing Active, the key Accepted by OpenAI and Sending On.](/docs/_assets/12b7f9404eb89a50f8e9b3cf2d8a9f079571fe77837c0fd77099cf9d8ef774f9)

*Figure: Add OpenAI destination: paste the Pixel ID and Conversions API key, keep Send events to OpenAI on.*

**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**; the app says **OpenAI accepted the test event**.

### 2. Set your consent banner

On Lightspeed, Product Metrics reads consent from the banner chosen under **Tracking → Configure consent** (OneTrust, Cookiebot, Usercentrics or Osano).

ChatGPT Ads has no consent mode: an event is only sent with marketing consent (ad user data), and the ChatGPT Ads click and browser references also need ad storage consent. Without ad personalisation consent, the event is sent marked as opted out. See [Consent](/docs/using/consent#chatgpt-ads).

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

### 3. Check an order

Place a test order with all cookies accepted, then open **Tracking → OpenAI Conversions API**.

**You should see:** your ChatGPT Ads pixel connected and delivering events, and your paid test order listed.

There is no report of the hashed fields themselves: ChatGPT Ads receives them only inside each event. Delivery errors show in the app under **OpenAI reported a problem**.

## Fields sent

Where each field comes from on Lightspeed:

| Customer data          | From                    | Sent to ChatGPT Ads as                                                         |
| ---------------------- | ----------------------- | ------------------------------------------------------------------------------ |
| Email address          | The Lightspeed order    | `emails_sha256`                                                                |
| Phone number           | The Lightspeed order    | `phone_numbers_sha256`: digits with country code, no `+`                       |
| First and last name    | The Lightspeed order    | `first_names_sha256`, `last_names_sha256`: lowercase, no spaces or punctuation |
| Customer ID            | Your shop's customer ID | `external_ids_sha256`                                                          |
| Postal code, country   | The Lightspeed order    | `postal_codes`, `countries`, unhashed as ChatGPT Ads asks                      |
| IP address, user agent | The visitor's browser   | `ip_address`, `user_agent`, unhashed                                           |
| Browser reference      | The `__obref` cookie    | `obref`, unmodified                                                            |
| Ad click               | The `__oppref` cookie   | `oppref`, unmodified                                                           |

Raw email addresses, phone numbers, names and customer IDs never leave Product Metrics. A postal code with characters ChatGPT Ads doesn't accept is left out rather than failing the event.

## Troubleshooting

### Orders are missing in ChatGPT Ads

Check that **Tracking → Configure consent** names the banner your store actually shows ([step 2](#2-set-your-consent-banner)).

## FAQ

### Can I keep the OpenAI Pixel on my site?

Yes. OpenAI deduplicates on Pixel ID, event name and event ID, and keeps the first event it receives.

### Which consent does ChatGPT Ads need on Lightspeed?

ChatGPT Ads has no consent mode: an event is only sent with marketing consent (ad user data), and the click and browser references also need ad storage. Without ad personalisation consent, the event is sent marked as opted out. On Lightspeed, Product Metrics reads it from the banner you choose: OneTrust, Cookiebot, Usercentrics or Osano.

### Can ChatGPT Ads bid on new or returning customers?

Not yet: ChatGPT Ads has no new or returning customer conversions. POAS and LTV bidding work through the OpenAI Conversions API.

### Are past orders and refunds sent to ChatGPT Ads?

No. OpenAI accepts events up to 7 days old, so historical orders aren't imported, and later refunds and cancellations don't revise events already sent.

## Where next

* [Lightspeed](/docs/platforms/lightspeed): the full shop setup
* [ChatGPT Ads (OpenAI)](/docs/channels/openai): every event, consent, limits and troubleshooting
* [Server-side conversion tracking on Lightspeed for ChatGPT Ads](/docs/tracking/server-side/lightspeed-openai)
* [Customer data on every channel](/docs/features/enhanced-conversions): the same customer data as Enhanced Conversions for Google Ads and the Meta Conversions API
* [Consent](/docs/concepts/consent)
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-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/test-openai).
