How can I optimize my ChatGPT Ads campaigns using Eulerian's Conversions API (CAPI) connector?
How can I optimize my ChatGPT Ads campaigns using Eulerian's Conversions API (CAPI) connector?
Solution
Marketing Mix Modeling
Attribution
Analytics
Activation
Module
Manage & Analyze
To plan
Activation
Datamining
Privacy Center
Problem
Ad blockers, browser restrictions on cookies and consent requirements reduce the number of conversions that a browser pixel can measure. Fewer measured conversions means fewer signals for ChatGPT Ads, and less accurate reporting. How can you send complete and reliable conversion data to ChatGPT Ads?
Objective
Setting up the OpenAI Conversions API (CAPI) to send your conversion events to ChatGPT Ads server-side will allow you to:
Improve measurement. Conversions sent server-side are less affected by loading errors, connectivity issues and ad blockers than browser pixels, so more conversions reach ChatGPT Ads.
Optimize your campaigns. More complete conversion data gives ChatGPT Ads more signals to optimize the delivery of your ads.
How Eulerian can help you
Comprehensive collection of navigation data, conversions, and advertising interactions
Native CAPI connector
Difficulty
Simple
Intermediate
Advanced
How to do it?
How to implement CAPI with Eulerian?
1. Retrieve your Conversions API key and Pixel ID from OpenAI
The connector needs two values provided by OpenAI:
your Conversions API key;
your Pixel ID.
Retrieve them from your ChatGPT Ads account. If you can't find them, contact your OpenAI representative.
Settings related to user consent: select “custom vendor”, enter the name of the OpenAI vendor as declared in your CMP (consent management platform), and select the purposes defined for this vendor by your CMP.
Call type – inbound traffic: select “site-centric”.
Call type – internal promotion: not applicable.
token: your OpenAI Conversions API key (step 1).
pixel_id: your OpenAI Pixel ID (step 1).
action_source (optional): where your conversions took place: web, mobile_app, offline, physical_store, email, phone_call or other. If left empty, it is set automatically for each event: mobile_app for app installs and iOS / Android devices, web otherwise.
Click on “Next”.
The hashed email address is sent by default by the CAPI connector, without any specific configuration.
3. Set the connector trigger rules
Specify the pages on which server calls will be made. The event sent to OpenAI depends on the type of call:
Sale: order_created
Lead (quote): lead_created
Cart: items_added
App install: app_installed
Other pages: page_viewed
For example: the only mandatory clause to send 100% of your sales is: “Make a sale” → “Yes”.
Click on “Confirm” to save the connector configuration.
4. Additional settings (optional)
On the settings screen, in the “Partner connector attributes” box, you can activate, deactivate, archive or schedule the activation of the connector.
In the “Partner settings” box, you will find your Conversions API key, your Pixel ID and your action source, but also:
type (optional): name of a custom event. When it is filled in, the event is sent to OpenAI as a custom event with this name, instead of the automatic event type described in step 3.
email_remap (optional): where the email address of your users is stored, for example when it is sent to Eulerian through a CRM synchronization. It replaces the email collected by Eulerian. An email in clear text is hashed in SHA-256 by Eulerian; an already hashed value is sent as is.
You can also send custom parameters through the “Custom parameters” box.
Custom parameters are only sent with custom events, that is when the type setting is filled in.
What information is sent to OpenAI?
The event type (or the custom event name), the action source, the event time and the URL of the page
The event ID: the sale or lead reference for sales and leads, an ID based on the Eulerian session for the other events
For sales and leads: the conversion amount (weighted by your attribution model if the connector uses one) and the currency
For sales: the products (reference, name, quantity, unit price and currency)
The OpenAI click reference oppref: taken from the click ID of the lever preceding the conversion if its publisher name contains "openai" or "chatgpt", otherwise from the oppref parameter of the landing page URL, if available
The OpenAI __obref first-party cookie, if available
The user's IP address and browser user agent
The user's CRM ID, hashed in SHA-256, if the user is logged in
The user's hashed email (email collected by Eulerian, or the field set in email_remap), if available
The user's hashed phone number, if available
The custom parameters, for custom events only
Only the events of users who gave consent for the OpenAI vendor are sent.