Skip to main content

The OpenAI Conversions API Program for Offline Conversions

LiveRamp's integration with OpenAI Conversions API allows you to send conversion data for attribution to understand how your ads in ChatGPT drive offline conversions. This integration will optimize for performance in OpenAI campaigns and help advertisers prove results, especially with view-through conversions where customers may not click an ad but still make real-life purchases.

Caution

The OpenAI Conversions API Program for Offline Conversions is in limited availability and is by invitation only. Contact your LiveRamp or OpenAI rep to find out about getting approved for this program.

Note

For retail media networks, LiveRamp recommends sending your conversions feed as a view in Connect. This method allows you to create brand- or SKU-specific conversions feed before distributing them to CAPI programs. To learn more, see "Getting Started with Conversions API Feed Distribution for Retail Media Networks".

This program is also available for online conversion events. See "LiveRamp's Online Conversions API Connectors" for more information.

Overview of Steps Involved

The following steps need to be performed to enable attribution analysis with OpenAI:

  1. Before your campaign starts, you send LiveRamp a sample conversion data file so we can test the integration with OpenAI.

  2. If you haven't yet, create a Pixel ID and Conversions API Key in OpenAI.

  3. You activate your campaign on OpenAI.

  4. You grant LiveRamp the ability to deliver data to your OpenAI Ads Manager Account by creating an OpenAI Conversions API destination account.

  5. You upload offline conversion data from the past 7 days with PII to LiveRamp.

  6. LiveRamp passes your conversion data file through OpenAI's Conversions API.

  7. You view the results within OpenAI Ads Manager UI.

Create Pixel ID and Conversions Key in OpenAI Ads Manager

To activate OpenAI's destination account in Connect, you need to provide a Pixel ID and Conversions API Key from OpenAI's Ads Manager. The Pixel ID is tied to a particular data source in Ads Manager, while the Conversions API key allows LiveRamp to send events to that particular data source.

Create a Pixel ID

If you haven't set up a data source yet, follow the instructions below:

  1. In OpenAI Ads Manager, select Conversions from the left navigation menu.

  2. Click Create and select "Data Source".

    oPENAI_CreatePixel.png

  3. Select Web as the data source type and enter a name.

  4. Click Create and copy the generated Pixel ID.

Create a Conversions Key

  1. In OpenAI Ads Manager, select Conversions from the left navigation menu.

  2. Use the Conversion keys dropdown and select "Create new key".

    oPENAI_CreateKey.png

  3. Enter a memorable name for the key.

  4. Click Create. Copy and store the one-time generated API Key immediately.

Activate an OpenAI Conversions API Destination Account

To distribute offline conversion data, you will need to activate an "OpenAI Conversions API PII Passthrough - Product Array" destination account in Connect.

Screenshot_2026-07-27_at_5_16_30_PM.png

Follow the general instructions in "Activate a New Destination Account", performing these additional steps:

  1. Remove the end date to leave the end date open-ended.

  2. Enter the conversion key from OpenAI's Ads Manager.

  3. Enter the Pixel ID associated with your preferred data source in OpenAI.

  4. In the Destination Account Name field, pick a unique and memorable name for this account. We'll suggest one for you but you can use any name you wish as long as it is less than 50 characters in length.

Format the File

This program utilizes the universal file format, which can be used across multiple Conversions API programs. For information on formatting guidelines, see "Using a Universal File for Multiple Conversions API Programs".

Using the Universal File Template

To make things easier for you, we've created a downloadable universal file template that you can use.

Note

The template contains formatting instructions in the second row of the file, along with info on whether a column is required and whether values are required, depending on which conversions programs you're using.

  1. Download the file template by clicking here.

  2. If desired, you can remove any non-required columns that aren't utilized by one of your conversions programs, but you can also leave those columns in the file and not populate them with values.

  3. Transfer your data into the template.

  4. After transferring your data into the file template, delete the second row with the formatting instructions.

  5. Save the file in one of our allowed file types (.csv, .tsv, .psv, or .txt).

  6. Upload the file to LiveRamp.

Once the file has been formatted correctly, upload the file to LiveRamp. See the “Upload the File” section below for more information.

Note

Once you set up the file format for an existing conversions program feed, try to keep the file format (such as the column headers or the column order) the same for all subsequent files. If you change the file format for an existing feed, create a support case before uploading the new file to ensure your existing feeds are not impacted. For more information, see "Changing the Format of an Existing File".

Send Conversion Data to LiveRamp

If you’re not currently using another LiveRamp Conversions API program (such as Bing or Yelp), we will need you to send us sample conversion data to set up the integration.

Caution

Most platforms require that at least 1,000 unique transaction events be uploaded over a 28-day period.

Conversion Data Guidelines

Each conversion data record must include at least one PII identifier (name and postal address, email, or phone) and the required conversion data:

  • Transaction category

  • Transaction timestamp

  • Transaction amount

  • Order ID

Conversion data should be uploaded within 7 days of the conversion.

Upload the File

Upload conversion data files using LiveRamp’s SFTP server or your SFTP server.

You can also have us pull files from an AWS S3 bucket or GCS bucket. See “Getting Your Data Into LiveRamp” for more information.

Caution

Files for this conversions program cannot be uploaded via Connect.

Note

For future uploads, you do not have to email LiveRamp to confirm that you have uploaded data assuming headers have not changed or additional columns have not been added.

Once the file is uploaded, information on file processing status can be viewed in LiveRamp Connect (see "Check File Processing Status" below for more information).

After OpenAI has ingested the conversion data, you will see your attribution report within OpenAI Ads Manager.

Check File Processing Status

You can check the status of the files you've uploaded on the Files page in Connect. See "Check the Status of an Uploaded File" for complete instructions.

Note

  • Once you've uploaded a file, it can take up to 20 minutes before it appears associated with the appropriate dataset(s) on the Files page. If the file does not appear after at least 20 minutes, create a support case.

  • Files for this program use our Measurement Enablement workflow, so the column headings that display on the Files page will look different from the ones that display for files that use our Activation workflow.

FAQs

At what cadence should I send my conversion data files?

Send conversion data files to LiveRamp daily or at the latest every 3 days. This is required in order to support OpenAI's 30-day attribution window.

What conversion data should I include in my conversion data file?

  • Include all traceable offline transactions in your delivery. Do not include online transaction data.

  • Avoid sending duplicate transactions (transactions already sent to LiveRamp). If you send daily files, only include transactions that occurred on that day. If you send weekly or monthly files, only send transactions that occurred since the previous file was sent.

  • Do not include transactions with a transaction date in the future.

In this section: