OpenAI Ads Conversions API Integration

ClickerVolt sends your conversions to OpenAI Ads through the OpenAI Conversions API. You add each OpenAI Ads Pixel with its Conversions API key, pick the pixel that should receive events, and ClickerVolt delivers server-side conversion events with hashed customer data for attribution, even when no OpenAI click ID is present.

Adding Your OpenAI Pixel

Unlike Google, Facebook and TikTok, OpenAI Ads does not use an OAuth connection. You add each pixel manually with credentials from OpenAI Ads Manager.

1. In OpenAI Ads Manager, open the Conversions tab and copy your Pixel ID and Conversions API key
2. In ClickerVolt, go to Settings → Integrations
3. Select the OpenAI Ads tab
4. Fill in the "Add OpenAI Ads Pixel" form
5. Click "Add OpenAI Ads Pixel"

The form has three fields:

• Conversions API Key: the key from Ads Manager. It is stored encrypted and never shown again
• Pixel ID: your OpenAI Ads pixel ID
• Pixel Name: a label to recognise this pixel, e.g. "Main Store Pixel"

You can add as many pixels as you need. Each one appears in the Integrations list with its Pixel ID, an on/off switch, an Edit button and a Delete button. Switching a pixel off pauses every delivery to it without deleting it. Edit lets you rename the pixel or rotate its key (leave the key blank to keep the current one). Deleting a pixel also stops all deliveries to it.

Choosing the Receiving Pixel

Once a pixel is added, tell ClickerVolt which pixel receives events for a link or target:

1. Open Tracking Setup → Ad Platforms
2. In the Default Integration tab, select OpenAI Ads
3. Choose the receiving pixel from the "OpenAI Ads Pixel" dropdown
4. Map your events in the Event Mapping table

Selecting a pixel is all it takes to start delivery; which events are sent is decided row by row in the Event Mapping table. Routing rules can send specific traffic segments to a different pixel: enable OpenAI Ads on the rule and choose a Pixel Override, or leave "Use Default Pixel" to inherit the Default Integration pixel. Rules are processed from top to bottom and the first matching rule wins.

If you change a pixel's Pixel ID in Settings, re-select the pixel in Tracking Setup so its event mappings pick up the new ID.

Event Mapping

Each ClickerVolt event can be sent to OpenAI as one of its standard events:

• order_created: the default for your main Conversion / Sale
• checkout_started, items_added, contents_viewed, page_viewed: funnel events
• lead_created, registration_completed, appointment_scheduled: lead events
• subscription_created, trial_started: plan enrollment events
• custom: a custom event name of your choice (letters, numbers, hyphens and underscores)

Set each row to On to send it, and optionally set a fixed Value that replaces the tracked revenue. Conversion values are sent in the currency's minor units (for example cents), so no rounding is lost. Make sure the matching conversion events exist in OpenAI Ads Manager.

Customer Matching Without a Click ID

Most ad platforms only accept conversions that carry their click ID. OpenAI Ads is different: ClickerVolt sends every matching signal it has, so conversions can be attributed even when the OpenAI click reference (oppref) is missing.

When a visitor arrives from an OpenAI ad, the oppref parameter is captured on the click, preserved across redirects, direct-tracked pages and funnel steps, and attached to the conversion. In addition, each event includes:

• PII (hashed with SHA-256): email, phone, first name, last name, external ID
• Geo: country, region, city, postal code
• Technical: IP address and user agent from the original click

All personally identifiable information (PII) is hashed before sending. Delayed conversions reuse the exact original click context while that click history is still retained, and each event carries a stable event ID so a retried delivery is not counted twice.

What This Integration Does Not Do

• It does not pull ad spend from OpenAI Ads or create pixels for you
• It does not send refund events to OpenAI Ads
• It does not deduplicate against the OpenAI browser pixel automatically. If you also run the browser pixel, use the same event ID, event type and Pixel ID on both sides
• OpenAI accepts events up to 7 days old; older conversions are not delivered

A successful delivery means OpenAI accepted the event, not that it was attributed to a campaign. Use OpenAI Ads reporting to verify attribution. If a delivery fails, the error is shown under the pixel in Settings → Integrations as its last sync error.