CHATGPT ADS TRACKING SETUP

ChatGPT Ads Conversion Tracking: 4 Easy Setup Steps

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.

ChatGPT Ads Conversion Tracking Setup: What Is Included

Everything needed to send clean events to OpenAI, set up around how your site actually works.

PIXEL

Measurement Pixel

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.

API

Conversions API

Server events sent to OpenAI with your Pixel ID and a separate Conversions API key, kept on the server and never in page code.

MAP

Event mapping

Your actions mapped to OpenAI's supported events or a custom event, with amounts sent as whole numbers in the currency's minor unit.

DEDUP

Deduplication

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.

HASH

User-data hashing

Customer fields hashed before sending, and kept within OpenAI's limit of three values per list.

CONSENT

Consent handling

Pixel consent controls set before it starts, and server events that follow the same choice on your side.

And more, as your setup needs it:Image tag where neededoppref capturePayload validationCustom eventsMinor-unit amountsWritten summary

Built for sales that close later

Many leads close in a CRM days after the ad click. These parts decide whether those sales can be reported.

CRM

Sales from your CRM

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.

TIME

The 7 day window

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.

CONSENT

Server-side consent

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.

TEST

Payload review before launch

Events are checked with OpenAI's validation-only mode before they go live, so errors show up without saving test data.

Why not just the Pixel alone?

The Pixel is a good start. It cannot see everything that happens after the click.

The Pixel alone

  • events fire only in the visitor's browser
  • it stops sending when consent is denied
  • app events such as installs and opens are not supported
  • sales confirmed later in a CRM are not seen

Pixel plus Conversions API

  • server events for confirmed orders and CRM stages
  • oppref stored and sent back with the event
  • shared event IDs keep counts clean
  • OpenAI's own campaign docs call the Conversions API a more reliable tracking source than the pixel alone

How we work together

Async from start to finish. You always know what happens next, in writing.

STEP 01

Request a quote

Send a short description of your site and tools.

STEP 02

Written scope

What will be set up, in writing, before anything starts. Access details are arranged after an order is placed.

STEP 03

Build and test

Pixel and Conversions API set up and checked against your real conversion actions.

STEP 04

Written summary

A plain summary of what was set up and how each event is mapped.

What to send with your quote request

Information only. Nothing else is needed to start.

Website platform

What your site is built on.

CRM or form tool

Where leads and sales are recorded.

Your conversions

Which actions count as a conversion for you.

Ad account status

Whether the Pixel and Conversions API are enabled on your ad account.

A good fit if

  • you run or are preparing ChatGPT Ads
  • leads or sales happen in a website, CRM, chat or booking tool
  • you want events mapped and deduplicated properly
  • sales that close later need to be reported back

Not included

  • running or managing your ads
  • campaign, budget or creative advice
  • promises about results or ad delivery
  • checking if ChatGPT Ads is available in your country, see OpenAI's official availability list
Already have a setup that shows missing or duplicate conversions? Get it reviewed in a written ChatGPT Ads tracking audit before changing anything.

Frequently asked questions

Short answers, taken from OpenAI's documentation.

What is ChatGPT Ads conversion tracking?

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.

Do I need both the Measurement Pixel and the Conversions API?

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.

What is oppref, and why must my server store it?

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.

How does deduplication work between the Pixel and the Conversions API?

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.

Can I track refunds or subscription renewals?

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.

How old can a server event be when I send it?

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.

Does consent affect ChatGPT Ads tracking?

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.

Which event should a conversion-optimized campaign use?

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.

Request a quote

Describe your setup in a few lines. You get a written scope and a quote, with no calls.

Or write to contact@alfahadhridoy.com

Request a quote