How to set up ChatGPT Ads conversion tracking

This guide walks through installing OpenAI’s Measurement Pixel, sending conversion events, adding server events and checking that ChatGPT Ads conversions are recorded.

BeginnerAbout 45 minutes, plus developer time for server eventsReviewed October 2026

ChatGPT ads do have conversion tracking. OpenAI offers a browser-side Measurement Pixel and a server-side Conversions API, and you can use them together. Results report into Ads Manager as conversions, cost per acquisition and, for purchases, return on ad spend. Advertisers see aggregated results, never conversations.

Attribution is based on ad clicks. A conversion can be credited to a click within a window of 7, 14 or 30 days, with 30 as the default. OpenAI also describes a 1-day view-through window where it is available for your account.

Create a pixel ID in Ads Manager

Open the conversions section of Ads Manager and create a new Pixel ID. You will use the same ID for the browser pixel and for any server events.

If you plan to send server events, create a Conversions API key in the same area. That key stays on your server and never goes into browser code.

Add the pixel code to every page

Place OpenAI’s pixel snippet in the head section of every page where you want to measure events, near the top so early conversions aren’t lost. The snippet loads OpenAI’s SDK and initializes it with your pixel ID.

OpenAI’s documentation doesn’t list an official Shopify app or Google Tag Manager template. On those platforms, a developer can add the snippet as custom code, or you can send data through one of OpenAI’s measurement partners.

TipTurn on the pixel's debug option while testing, since it logs pixel activity to the browser console.

Send standard events

Fire events with the pixel’s measure call on the pages where actions happen. Standard events include page_viewed, contents_viewed, items_added, checkout_started, order_created, lead_created, registration_completed, appointment_scheduled, subscription_created and trial_started.

For purchases, send order_created with the amount and currency. Amounts use the currency’s smallest unit as whole numbers, so $89.00 is sent as 8900.

Handle consent and security settings

If your site needs consent before tracking, set the pixel’s consent to false before it initializes and switch it to true when the visitor agrees. While consent is false nothing is sent, and blocked events are not replayed later.

If your site enforces a Content Security Policy, add the OpenAI script and event domains listed in the developer documentation, or the pixel will be blocked.

Add the Conversions API for confirmed conversions

Server events come from your backend, for example when an order is confirmed or a CRM marks a lead. Each one is sent with your pixel ID and Conversions API key and needs an ID, event type, a timestamp within the last 7 days, and event data.

Customer identifiers such as email and phone must be normalized and SHA-256 hashed before sending. OpenAI also lists measurement partners including Fospha, Hightouch, LiveRamp, Triple Whale and WorkMagic.

Deduplicate browser and server events

If the same purchase is sent by both the pixel and your server, give both the same pixel ID, event name and event ID. OpenAI keeps the first event it receives and ignores the duplicate.

Use your order or transaction ID as the event ID. A value generated separately on each side defeats deduplication and inflates conversions.

Check that events are arriving

With debug on, complete a test action on your site and watch the browser console for pixel activity. You can also open the browser’s network panel and look for requests to OpenAI’s event endpoint.

For developers, OpenAI’s API offers a recent-events check that returns a sample from roughly the last 15 minutes. Attributed conversions appear in reporting after daily processing, so allow at least a day.

Pick the conversion event for your campaign

A Conversions campaign optimizes toward exactly one active standard event, chosen when you create the campaign. Custom events can be tracked but can’t be used for optimization.

The objective and that event can’t be changed later, so confirm the event fires reliably before you build the campaign around it.

Before you move on

  • The pixel loads on every page you want to measure
  • Purchase events carry the amount in the smallest currency unit
  • Consent settings match your site's requirements
  • Browser and server events share event IDs
  • Test events show up before you launch spend

Official resources

Ad platforms update their tools often. This guide was last reviewed against the official documentation above in October 2026. If your screen looks different, the official help pages have the latest steps.

At a glance

Level
Beginner
Time
About 45 minutes, plus developer time for server events
What you need
  • Access to Ads Manager Beta
  • Access to edit your site's head code, or a developer who can
  • A list of the actions you want to measure, such as purchases or leads
  • Your consent management setup, if your site uses one

Where DIY setups go wrong

The most common problems with self-built ChatGPT Ads setups, and what they cost.

Pixel on some pages only

OpenAI recommends the snippet on every page where you want to measure. Gaps break the path from click to conversion.

Mismatched event IDs

Without matching IDs across pixel and server, a conversion can count twice and the optimizer works from inflated numbers.

Wrong amount format

Amounts are sent as whole numbers in the currency's smallest unit. Sending 89 instead of 8900 under-reports that order's value a hundredfold.

Ignoring consent

Firing the pixel before consent where consent is required creates legal exposure, and events blocked by consent are not recovered later.

Judging conversions the same day

Conversion data updates through daily processing, so same-day reports are partial.

What this guide doesn't cover

A firing pixel is the minimum. Reliable measurement on a new platform means server events for confirmed sales, clean deduplication, consent handled correctly, and a realistic view of what ChatGPT ads add beyond customers who would have found you through search anyway.

OpenAI’s own documents describe view-through conversions in slightly different ways, which is a reminder to read the numbers carefully. ADM sets up tracking before spend and reconciles platform results against store and CRM data.

  • Conversions API with hashed customer data
  • Deduplication using order and lead IDs
  • Consent and Content Security Policy setup
  • Attribution window choices and view-through handling
  • Offline and CRM conversions
  • Reconciling platform data with Shopify, GA4 and your CRM

Common questions

Do ChatGPT ads have a pixel?

Yes. OpenAI offers a Measurement Pixel for the browser and a Conversions API for server events, and the two can be used together.

Is there a Shopify app for ChatGPT Ads tracking?

OpenAI's documentation doesn't list an official Shopify app or Google Tag Manager template. Third-party apps exist, so check what they send and who maintains them before installing one.

What attribution window does ChatGPT Ads use?

Click windows can be 7, 14 or 30 days, with 30 as the default. OpenAI also describes a 1-day view-through window where available.

How fast do conversions show up?

Clicks and impressions can show within minutes, but conversion data updates through daily processing. OpenAI says to allow at least one day.

Rather have it built right the first time?

If your business does $25,000+ a month in revenue, apply and Mitch will review your accounts personally. Earlier than that? An ad account audit gives you a senior-level fix list you can work through yourself.