ChatGPT Ads, server-side

Your conversions (purchases, leads, sign-ups, custom events), not every page view. Each one goes out under the standard type OpenAI expects: a purchase becomes order_created, a lead lead_created. For each one:

• the value and the currency, in the unit OpenAI asks for (in cents for the euro, with no decimals for the yen);
• an event identifier, the same as your OpenAI pixel's if you pass it to the pixel (see below);
• the oppref click ID. Oriva reads it from the landing URL, or from the OpenAI pixel cookie if the URL no longer carries it. OpenAI states that its Conversions API doesn't capture it on its own: the tool that sends has to pass it along;
• the email, the phone and your customer ID, irreversibly hashed (SHA-256) before they are stored, in the format OpenAI asks for;
• the visitor's IP address and browser. Oriva deletes them from its database after 90 days;
• the standard order details (reference, products, quantity). Never the commission paid to an affiliate.

You can. OpenAI deduplicates an event received from the browser and from the server when it carries the same Pixel ID, the same event name and the same identifier, and keeps the first one received. So give the same order reference to your pixel (event_id) and to Oriva. Without it, OpenAI counts the sale twice. Oriva's Health tab warns you when it sees the OpenAI pixel next to an active ChatGPT Ads destination.

Without the visitor's agreement for advertising, Oriva sends nothing to OpenAI, as with Meta, TikTok and Google Ads. By default, Oriva assumes the visitor has not agreed: you need to connect your cookie banner to Oriva, in one line.

Watch out for the OpenAI pixel if you install it too: by default, it assumes the visitor has agreed. You need to initialize it with consent set to “no”, then switch it to “yes” from your banner.

The “Test this destination” button asks OpenAI to validate the request without recording it: your key, your Pixel ID and the format are checked, nothing is counted. A destination's test mode does the same for your real sales, long enough to check that everything arrives.

You see it in the delivery log, with OpenAI's answer and a sentence that says what to do (for example: “key rejected, regenerate it in Ads Manager”). A temporary error or a rate limit is retried automatically. OpenAI refuses an event older than 7 days: Oriva marks it failed without sending it.

• a ChatGPT Ads Manager account;
• the Pixel ID and a Conversions API key, both created in the Conversions tab of Ads Manager;
• nothing else: no Google Tag Manager container, no server code to write.