Integrations / Advertising
OpenAI Ads
Server-side conversion delivery to OpenAI Ads (ChatGPT Ads) via the Conversions API (POST https://bzr.openai.com/v1/events?pid=<pixel_id>). Maps Signal events to OpenAI standard event types, sends SHA-256 hashed email/phone plus external_id, IP and user agent for matching, carries event id for pixel/CAPI deduplication, and honours marketing consent via opt_out.
Datafly Signal delivers first-party events to OpenAI Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload OpenAI Ads expects.
Why route OpenAI Ads through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions OpenAI Ads optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so OpenAI Ads receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what OpenAI Ads needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the OpenAI Ads rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
OpenAI Ads is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutgenerate_leadpagepurchasesign_upsubscription_startedtrial_startedview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the OpenAI Ads documentation.
Frequently asked questions
Does Datafly Signal integrate with OpenAI Ads?
Yes. Datafly Signal delivers first-party events to OpenAI Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload OpenAI Ads expects. The integration is included in every deployment at no additional cost.
How is server-side OpenAI Ads tracking different from the OpenAI Ads tag?
The OpenAI Ads tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to OpenAI Ads from your server, so delivery does not depend on browser conditions.
What personal data is sent to OpenAI Ads?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so OpenAI Ads receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to OpenAI Ads?
The blueprint ships with mappings for add_to_cart, begin_checkout, generate_lead, page, purchase, sign_up, subscription_started, trial_started, and more. Any event in your schema can be mapped to OpenAI Ads through pipeline configuration without a code change.
Do I need to keep the OpenAI Ads tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so OpenAI Ads deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move OpenAI Ads server-side?
See how Datafly Signal delivers first-party events to OpenAI Ads from infrastructure you control, with hashed identity and consent enforcement built in.