Ad platforms

OpenAI Ads Conversions API

Send outcomes to OpenAI Ads Conversions API through the approval gate, matched by click id or hashed email and phone.

Built, not yet tested liveBuilt. Not yet tested against a live OpenAI Ads Conversions API account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

Conversions > Destinations > OpenAI Ads Conversions API: Pixel ID; Conversions API key (stored encrypted).
Then send a test event and check Conversions > Audit log.

What OrcLink reads

Nothing.

What OrcLink writes back

Conversions for the stages you set to relay (Outcomes > Stages), each with its click id and the hashed email and phone the platform matches on. Each batch waits for approval when approval is on (the default).
The browser user agent, when "send user agent" is on in the Compliance tab (never in strict consent mode).

Never stored

Raw email or phone: only hashes leave OrcLink.
Page paths, page titles, referrers and IP addresses: never sent to an ad platform.