ChatGPT Ads conversion tracking built from OpenAI's official documentation: the Measurement Pixel and the Conversions API set up together, with event mapping and deduplication so each conversion is counted once.
For advertisers running or preparing ChatGPT Ads, with leads or sales in a website, CRM, chat or booking tool. Everything handled in writing, no calls.
page_viewedlead_createdorder_createdIllustration only.
Everything needed to send clean events to OpenAI, set up around how your site actually works.
The oaiq script loads from OpenAI's CDN and events fire when you tell it to. Page views are manual, so each event is mapped to a real action on your site.
Server events sent to OpenAI with your Pixel ID and a separate Conversions API key, kept on the server and never in page code.
Your actions mapped to OpenAI's supported events or a custom event, with amounts sent as whole numbers in the currency's minor unit.
The same event ID on the browser and server side, so one conversion is not counted twice. OpenAI keeps the first matching event it receives.
Customer fields hashed before sending, and kept within OpenAI's limit of three values per list.
Pixel consent controls set before it starts, and server events that follow the same choice on your side.
Many leads close in a CRM days after the ad click. These parts decide whether those sales can be reported.
The oppref value arrives in the landing page URL. The Conversions API does not capture it for you, so it is stored with the lead and sent back unchanged when the sale closes.
A server event's timestamp must be within the last 7 days and no more than 10 minutes ahead. Sales events are sent as they happen, not in a late batch.
A denied choice stops the Pixel. Server events do not stop on their own, so the same choice is checked before a server event is sent.
Events are checked with OpenAI's validation-only mode before they go live, so errors show up without saving test data.
The Pixel is a good start. It cannot see everything that happens after the click.
Async from start to finish. You always know what happens next, in writing.
Send a short description of your site and tools.
What will be set up, in writing, before anything starts. Access details are arranged after an order is placed.
Pixel and Conversions API set up and checked against your real conversion actions.
A plain summary of what was set up and how each event is mapped.
Information only. Nothing else is needed to start.
What your site is built on.
Where leads and sales are recorded.
Which actions count as a conversion for you.
Whether the Pixel and Conversions API are enabled on your ad account.
Short answers, taken from OpenAI's documentation.
It is how actions that follow an ad click, such as a lead or an order, are reported back to OpenAI. Events are sent from your website with the Measurement Pixel and from your server with the Conversions API, so ChatGPT Ads can credit them to the ad.
You can use either, or both. The Pixel sends events from the browser, and the Conversions API sends events from your server, such as confirmed orders. App events such as installs and opens cannot come from the Pixel and must be sent from the server. When you use both, shared event IDs prevent duplicates. Which setup fits your site is decided in the written scope.
It is an ad click reference that arrives in the landing page URL. The Pixel captures it and keeps it in a cookie for 30 days. The Conversions API does not capture it automatically, so your server must store it with the lead and send it back unchanged on the server event.
OpenAI matches events on the Pixel ID, the event name and the event ID. For custom events, the custom event name replaces the event name in that key. The first matching event received is kept and later copies are ignored, so the same ID has to be used on both sides.
OpenAI's list of 13 event types has no refund event. The subscription event is described as a paid subscription starting, and no renewal event is listed. A custom event can record other actions, but OpenAI says custom events cannot be the goal of a conversion-optimized campaign.
The timestamp must be within the last 7 days and no more than 10 minutes in the future. A batch can hold up to 1,000 events, and if one event fails, the whole batch fails. Sales events should be sent as they happen.
Yes. The Pixel treats consent as granted unless you set it to false, so consent controls must be set before it starts. When consent is false, the Pixel sends no measurement events, and blocked events are not replayed later. Server events must follow the same choice on your side.
A conversion-optimized campaign needs exactly one standard event, chosen when the campaign is created. The goal cannot be changed afterwards, and custom events cannot be used as the goal. To optimize for a different event, a new campaign is needed, so the event is decided before launch.
Built on OpenAI's Measurement Pixel, Conversions API and supported events documentation. These tools are new, so each step follows the official documentation. The method comes from server-side tracking work on Meta, Google Ads and TikTok Conversions API setups, GA4, GTM and CRM webhooks.
Describe your setup in a few lines. You get a written scope and a quote, with no calls.
Or write to contact@alfahadhridoy.com