Growth marketer operator · San Jose, CA | ZuAI: 10K → 2M users at $0.02 CAC | $300k/mo ad spend managed
Ar.Bhavesh Pro
ChatGPT Ads

OpenAI Conversions API: server side tracking

send ChatGPT Ads conversions server side with the OpenAI Conversions API, pass oppref, and stop double counting with one shared event ID.

last updated 5 November 2026

the OpenAI Conversions API sends ChatGPT Ads conversion events from your server instead of the browser. it uses a Conversions API key from the Conversions section of Ads Manager, reports to the same Pixel ID as the pixel, and catches the events browsers lose: ad blockers, browser privacy changes and people who close the tab before the pixel fires. it is more work than the pixel, and it is the version worth pushing any serious advertiser toward, because browser side tracking loses more events every year.

Pixel, API or both

there are four ways to send conversions, all to the same Pixel ID, and you can run more than one:

  • the OpenAI pixel, the oaiq snippet in the browser. fastest to install. set up in the pixel chapter.
  • the Conversions API, server side, covered here.
  • the image tag, a no-JavaScript fallback for places that cannot run a script.
  • a measurement partner: Adjust, Airbridge, AppsFlyer, Branch, Kochava, Singular or Tenjin. you enter the Pixel ID and Conversions API key in the partner and it forwards events. for apps this is now the main route.

the setup worth having is the pixel and the API together: the pixel for speed and coverage, the API for the events browsers lose. the one risk is counting the same purchase twice, and that has a clean fix.

Setup, step by step

  1. create a Conversions API key in the Conversions section of Ads Manager, the same place your Pixel ID lives.
  2. send each server side conversion to that same Pixel ID, so both sources land in one place.
  3. keep the oppref value from the landing page URL with the sign-up or order record, so your server has it to send. include it in every Conversions API call where you have it. an event that does not carry oppref has to be matched on weaker signals.
  4. give every conversion one event ID, built from something stable such as your order ID, and send that same ID with the pixel event and with the API event.
  5. send a value with purchases, the same value the pixel sends.
  6. fire a real test conversion through both paths and confirm it shows up in Ads Manager once, not twice.

Deduplication is one shared ID

when the pixel and the API both report the same conversion with the same event ID, OpenAI keeps one and drops the other. that only works if the two IDs actually match. build the ID from something both sides already know, your order ID or sign-up ID, rather than generating a random number in the browser and another on the server. two different random numbers will never match, and every conversion gets counted twice.

double counting is worse than it sounds under the Conversions objective. delivery optimises toward the signals you send, so inflated conversions do not just flatter the dashboard, they teach the system the wrong thing about who converts.

Why server side tracking matters more for OpenAI ads

two reasons, both from how the platform works. first, the pixel depends on the browser, and the browser is where events go missing. second, the Conversions objective treats your signals as the truth: missing, wrong or delayed events degrade delivery, not just reporting. server side tracking is the part of the setup that keeps those signals arriving when the browser fails.

When the API and Ads Manager still disagree with your analytics

they will, and a difference does not by itself mean an error. attribution windows, time zones, consent and cookie conditions, deduplication rules and modelled conversions all differ between tools. what to do about that is in the measurement checklist.

the full tracking write-up, with sources from OpenAI’s own documentation, is in ChatGPT Ads tracking: OAIQ pixel and OpenAI Conversions API.

next in this playbook: choosing a ChatGPT Ads objective, once your events are arriving.

server side tracking is one leg of the ChatGPT Ads playbook. if you want a second pair of eyes on your Conversions API setup, the breakdown call is free. Let’s talk Growth.

this page is part of the ChatGPT Ads playbook.

next

More in this playbook

Want this run on your app?

the playbook is free and yours. if you would rather it was executed than read, tell me what you are working on.

answers go to a private google sheet and to my inbox, used only to reply and follow up. the newsletter is opt in and separate.

Want this run on your app?

the breakdown call is free. bring one real growth problem, leave with the fix.

Let's talk Growth