How Do You Track Conversions on ChatGPT Ads?

You track conversions on ChatGPT Ads by running two methods together inside OpenAI's Ads Manager: a browser-based Pixel and a server-side Conversions API, deduplicated by a shared event identifier so the same action isn't counted twice. OpenAI documents both methods on its own developer site, and they shipped alongside the self-serve Ads Manager it opened to advertisers in 2026.

The ChatGPT Pixel

The Pixel is a snippet of website code, similar in concept to Meta's or Reddit's browser pixels, that fires when a visitor who clicked a ChatGPT ad completes an action on your site. It gives the fastest path to visibility inside Ads Manager, since it requires no backend development, but it depends on the visitor's browser actually loading and executing the script.

The Conversions API

The Conversions API (CAPI) sends the same event data from your own server directly to OpenAI's ad systems, instead of relying on the browser to fire it. That makes it the more reliable half of the pair, since it isn't affected by ad blockers, cookie restrictions, or a visitor closing the tab before a browser-side pixel finishes firing. Third-party integrations from Shopify apps and mobile measurement partners have already built CAPI connections on top of this server-side method, which is a sign OpenAI's documentation treats it as the production-grade path rather than an experimental add-on.

Why Running Both Requires Deduplication

When the Pixel and the Conversions API both report the same purchase or lead, OpenAI needs a way to recognize it as one event, not two. That's standard practice across every platform that offers this pixel-plus-API pattern — Meta, TikTok, and Reddit all require the same thing — and it means your implementation needs a consistent event ID or matching key passed through both the Pixel call and the CAPI call for the same user action.

View-Through Conversions Use a Fixed Window

Beyond click-driven conversions, ChatGPT Ads also counts view-through conversions — actions a user takes after seeing an ad without clicking it — on a fixed one-day attribution window, according to reporting on the platform's measurement updates. That's narrower than the 7-day or 28-day view-through windows common on platforms like Meta, so don't expect view-through numbers from ChatGPT Ads to behave like they do elsewhere.

Setting It Up

• Generate your Pixel inside Ads Manager. Create a web-type conversion source and install the resulting Pixel code on your site, either directly or through a tag manager.
• Create a Conversions API connection for the same events. Set up server-side calls, or use an existing partner integration if your store or CRM already supports one, so the same purchase or lead event flows through both paths.
• Pass a shared identifier on every event. Make sure both the Pixel call and the CAPI call for a given action carry the same matching key, so OpenAI's systems can deduplicate correctly.
• Check reported conversions against your own backend numbers before scaling spend. Since this is a new measurement system, treat your first few weeks of reported conversions as a verification period, not a number to optimize against blindly.

Bottom Line

Set up the Pixel first for quick visibility, then add the Conversions API as a server-side layer over the same conversion events rather than a separate tracking plan, and don't scale spend until you've confirmed deduplication is working and your reported conversions roughly match what your own backend records.

Sources: OpenAI Developer Platform, "Conversion Tracking" documentation (developers.openai.com/ads/conversion-tracking); PPC Land, "ChatGPT Ads Gains View-Through Conversions With a Fixed 1-Day Window"; Aimerce and WeltPixel 2026 integration guides on Conversions API setup for ChatGPT Ads.