Skip to content
ChatGPT Ads

Lightspeed customer data for ChatGPT Ads (OpenAI Conversions API)

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 on the property in Product Metrics, with Pro (Full Signal Tracking).
  • A Lightspeed eCom (C-Series) API key and secret from your back office, and a workspace admin who can approve Cloudflare once.
  • Access to ChatGPT Ads Manager → Conversions, to copy your Pixel ID and create a Conversions API key.

Set it up with AI

Connect your assistant

First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.

In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:

https://www.productmetrics.io/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Paste the prompt into your assistant.

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.
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.
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.
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. For ChatGPT Ads, 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.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.
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, and the gateway says Gateway setup complete; the app says OpenAI accepted the test event.

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.

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 dataFromSent to ChatGPT Ads as
Email addressThe Lightspeed orderemails_sha256
Phone numberThe Lightspeed orderphone_numbers_sha256: digits with country code, no +
First and last nameThe Lightspeed orderfirst_names_sha256, last_names_sha256: lowercase, no spaces or punctuation
Customer IDYour shop’s customer IDexternal_ids_sha256
Postal code, countryThe Lightspeed orderpostal_codes, countries, unhashed as ChatGPT Ads asks
IP address, user agentThe visitor’s browserip_address, user_agent, unhashed
Browser referenceThe __obref cookieobref, unmodified
Ad clickThe __oppref cookieoppref, 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).

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.

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

Developers: do the same with the CLI or the API.