Oriva

Create a conversion event in ChatGPT Ads Manager

Published on by the Oriva team.

On ChatGPT Ads, unlike Meta and Google Ads, a send that succeeds (200, accepted) counts for nothing until a Conversion Event with the exact name Oriva sends exists in Ads Manager. This is not a guess: it is what we saw live on a real account on September 24, 2026. Every send succeeded, and nothing was counted on the ChatGPT Ads side.

On ChatGPT Ads, an accepted send counts for nothing without a Conversion Event of the exact name; once it is created, the sale is counted.

Create the pixel (if you haven't already)

In ChatGPT Ads Manager, open the Conversions tab: create or open your pixel. Its identifier (Pixel ID) and a Conversions API key are shown there. Both go in the Oriva destination form.

Create a conversion event for everything you track

  1. Still in the Conversions tab: click + Create.
  2. For a standard Oriva event (purchase, lead, subscribe, start_trial…), choose the matching OpenAI type.
  3. For everything else, including a custom Oriva event like custom:clic_partenaire, choose custom and type the exact, case-sensitive name Oriva sends, attached to the same pixel.

Without this step, nothing ever shows up, even when the delivery looks perfect in the Oriva delivery log.

Check that it works

The destination's “Test” button always sends with validate_only: OpenAI checks the key, the pixel and the format without recording anything. Once the destination is created, its Test mode does the same for real conversions: keep it on until your first real sales show up, correctly classified, in the Oriva delivery log.

Who doesn't need this guide?

You already have a conversion event created for every type of event Oriva sends.

To understand what Oriva sends and why the OpenAI pixel alone is not always enough, see tracking ChatGPT Ads conversions.

Start free trial

Sources