OpenAI Ads Conversions API

Datafly Signal delivers conversion events to OpenAI Ads (ChatGPT Ads) server-to-server using the Conversions API. This feeds OpenAI’s conversion-optimised campaign objective and provides reliable measurement that is not affected by ad blockers or browser tracking prevention.

Prerequisites

Before configuring OpenAI Ads in Signal, you need an OpenAI Ads account with an active Pixel and a Conversions API key.

Step 1: Create an OpenAI Ads account

If you don’t already have one, sign up at ads.openai.com and complete the advertiser onboarding for the ChatGPT Ads Manager.

Step 2: Create or find your Pixel

1. In ChatGPT Ads Manager, open the Conversions tab.
2. If you already have a Pixel, note its Pixel ID (used as the pid parameter).
3. To create a new Pixel, follow the Set up conversions flow and note the Pixel ID it generates.

Step 3: Generate a Conversions API key

1. Still in the Conversions tab, generate a Conversions API key.
2. Copy the key immediately and store it securely — it grants write access to your pixel’s conversions.

Configure in Signal

Configuration fields

Management UI setup

API Endpoint

POST https://bzr.openai.com/v1/events?pid={pixel_id}
Authorization: Bearer {api_key}
Content-Type: application/json

Events are sent as a JSON array under the events key. OpenAI accepts up to 1,000 events per request. timestamp_ms must be within the last 7 days and no more than 10 minutes in the future.

Identity Signals

OpenAI matches server events to ad exposure using the signals below. The more you provide, the better the match rate and conversion optimisation.

Automatic signals

These are sent automatically by Signal — no configuration needed:

User-provided signals (hashed)

When a user is identified via datafly.identify() with traits, these fields are SHA-256 hashed before sending to OpenAI:

How to send user data

Call datafly.identify() when a user logs in, registers, or submits a form:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  phone: "+44 7700 900123"
});

Signal normalises and hashes these fields automatically before delivery.

Event Mapping

Default preset

To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD",
  products: [
    { product_id: "SKU-A", product_name: "Widget", quantity: 2 },
    { product_id: "SKU-B", product_name: "Gadget", quantity: 1 }
  ]
});

OpenAI Ads payload sent by Signal:

{
  "events": [
    {
      "id": "evt_abc123def456",
      "type": "order_created",
      "timestamp_ms": 1717660800000,
      "action_source": "web",
      "source_url": "https://example.com/checkout/confirmation",
      "opt_out": false,
      "user": {
        "email": "a1b2c3...",
        "external_id": "anon_98f2...",
        "ip_address": "203.0.113.50",
        "user_agent": "Mozilla/5.0 ..."
      },
      "data": {
        "type": "contents",
        "amount": 129.99,
        "currency": "USD",
        "order_id": "ORD-001",
        "contents": [
          { "id": "SKU-A", "name": "Widget", "quantity": 2 },
          { "id": "SKU-B", "name": "Gadget", "quantity": 1 }
        ]
      }
    }
  ]
}

Consent

Signal maps your canonical marketing consent state to the per-event opt_out flag. When marketing consent is granted, opt_out is false; when it is denied or absent, opt_out is true, which excludes the event from user-level personalisation.

Testing your integration

Deduplication

If you run both Signal server-side delivery and the OpenAI JavaScript pixel during a migration period, deduplicate to prevent double-counting:

1. Use the same value for the Conversions API id and the pixel event_id.
2. Send both with the same Pixel ID.
3. For custom events, use the same custom_event_name on both sides.

Signal includes a unique id with every event. OpenAI deduplicates events that share the same id and type.

Troubleshooting