Customer data for ChatGPT Ads (OpenAI Conversions API) on any website with Cloudflare
Send hashed customer data from your website's 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 email address your site passes to Product Metrics, hashed in the browser (a website order carries no customer record), 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.
Your domain on Cloudflare DNS and a Cloudflare sign-in.
Your Pixel ID and a Conversions API key from Ads Manager.
Hashed customer data and browser references on every ChatGPT Ads event.
Prerequisites
- Editor or admin on the property in Product Metrics, with Pro (Full Signal Tracking).
- Your website on Cloudflare Tracking: its domain on Cloudflare DNS with the record proxied (the orange cloud), a workspace admin who signs in to Cloudflare and approves Product Metrics (that is the whole setup), and the website linked to your property. See Any website (Cloudflare).
- Access to ChatGPT Ads Manager → Conversions, to copy your Pixel ID and create a Conversions API key.
In the app
1. Connect your website and ChatGPT Ads
Connect your website with Cloudflare Tracking. 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.
You should see: the gateway card says Gateway setup complete; the app says OpenAI accepted the test event.
2. Set your consent banner
On Cloudflare Tracking, 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 website 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 test order received.
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.
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/mcpClaude Code: run this in your terminal.
claude mcp add --transport http product-metrics https://www.productmetrics.io/mcpPaste the prompt into your assistant.
Check that Product Metrics sends customer data with my ChatGPT Ads events from my website (tracked with Cloudflare Tracking). 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 website (tracked with Cloudflare Tracking). 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 website (tracked with Cloudflare Tracking). 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 website (tracked with Cloudflare Tracking). 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.Fields sent
| Customer data | From | Sent to ChatGPT Ads as |
|---|---|---|
| Email address | The email your site passes to Product Metrics | emails_sha256 |
| 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
| Problem | Fix |
|---|---|
| Orders are missing in ChatGPT Ads | Check that Tracking → Configure consent names the banner your website 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.
Which consent does ChatGPT Ads need on my website?
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. Product Metrics reads it from the banner your website shows: 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. Product Metrics still tracks them in your profit and lifetime value.
Where next
The full website setup.
Every event, consent, limits and troubleshooting.
The same setup in ChatGPT Ads.
The same customer data as Enhanced Conversions for Google Ads and the Meta Conversions API.
What each consent choice lets through.
On the website: Full Signal Tracking, first-party cookie