Short answer
The Conversions API sends conversion events from your server to OpenAI. Send events promptly after a confirmed action (the quality check looks for receipt within one hour), include the oppref click reference when you have it, the same event ID used by the Pixel, hashed customer identifiers where eligible, and the real client IP and user agent.
What to include
| Field | Why |
|---|---|
| Event name (standard) | Matches the campaign event |
| Event ID | Deduplication with the Pixel |
| Event time | Keep the original time on retries |
| oppref | Links the event to the ad click |
| Hashed email or phone | Better matching |
| Client IP and user agent | Additional matching for server events |
Where the key is
Data source credentials (Pixel ID and Conversions API key) are in the Conversions section of Ads Manager. Standard API keys are created under Settings > General > API Keys.
Questions
Can we send offline conversions?
Partners such as LiveRamp offer separate online and offline conversion feeds; OpenAI's own article focuses on standard events.
Facts checked against the sources below on 12 October 2026. Platforms change quickly: if something here no longer matches what you see, tell us and we will update it.
