ChatGPT Ads Conversion Tracking
Set up a web pixel or a server-side Conversions API key and get chatgpt ads conversion tracking that ties every ChatGPT ad click to what happens next — a signup, a trial, a purchase — so campaigns can bid on outcomes instead of clicks alone.
Conversion Event Sources
A web pixel measures from the browser; a Conversions API key sends events straight from your server. ChatGPT Ads has no endpoint to list either back, so pixel IDs and a key’s secret are shown once, at creation — pixels already in use appear below, taken from the events built on them.
- ChatGPT ads pixel or Conversions API — measure from the browser or send events server-side; use either, or both, per campaign.
- Define conversion events — name, event type, attribution window and which sources feed it, all in one place.
- See what’s used where — every conversion event shows which campaigns are currently bidding on it, so retiring one you still rely on does not quietly break bidding.
- Bid on outcomes, not clicks — once a conversion event exists, a
conversions-bidding campaign requires exactly one, and ad groups target it directly instead of optimizing for CTR alone. - Only pixel sources come back later — a pixel used in an event setting is recoverable through that setting; an API key is not, because ChatGPT Ads has no endpoint to read either back.
Conversion Event Settings
Existing source chips are deduplicated from the sources embedded in your event settings, so the same pixel or key does not show twice. The table itself lists each setting’s name, standard or custom event name, attribution window, source, the campaigns using it, and whether it is archived — enough to audit what is defined, not enough to confirm it is firing.
- Treat it as inventory, not proof — a setting existing does not mean the pixel is installed, the server is calling, or events are arriving; verify delivery separately before assigning it to a conversions-bidding campaign.
- Choose the event closest to the real outcome — and keep a custom event’s name identical between the implementation and the setting, or the two never match up.
- Pick the attribution window deliberately — it changes which conversions can be credited to ad exposure, but this screen has no comparative performance data to infer a good one from.
Conversion Credential Security
Both the pixel ID and the Conversions API secret exist in exactly one response each. There is no list of previously created pixels or keys, because the upstream ChatGPT Ads API has no read endpoint for either — only the pixel comes back indirectly, through the event settings built on it.
- To create an event setting — enter a name of at least three characters, pick a standard or custom event, choose exactly one source, set a 1-90 day attribution window, and add the custom event name if applicable.
- Creation refreshes the table immediately — and the same event list is what the campaign-creation dialog reads from when conversions bidding is selected.
- A connected ChatGPT Ads account is required — without one, this page shows the connection flow instead of the setup surface.
Conversion Revenue Attribution
A conversion event tells you a click became a signup. Revenue Attribution follows it further — connecting Stripe or Shopify so the exact campaign and ad group get credit for the trial, order or MRR it produced.
- One attribution model — paid ChatGPT clicks and organic AI citations, measured the same way.
- Revenue by campaign — know which ad group is actually worth the daily budget.
- Prove ROI, not just conversions — report spend against MRR, the number that actually gets a budget renewed.
measurement sources, one integration each
A pixel for browser-side events, a Conversions API key for server-side — set up once, reused across every campaign in the workspace.
See the ChatGPT Ads ManagerReady to know which ChatGPT ad actually converts?
Free check · 7-day trial · card required