Documentation
Conversions API
Use the Conversions API when browser events are not enough, and share event IDs so the same conversion is not counted twice.
Last updated: 2026-09-03. Written by PixelBridge team.
The OpenAI Ads Conversions API provides a server-side method for sending supported conversion events to OpenAI's advertising measurement systems. PixelBridge is designed to send those events from WordPress and to coordinate them with browser events.
Why server-side measurement exists
Browser pixels can be blocked by consent choices, browsers, extensions or Content Security Policy rules. A server event can still record a supported conversion after WordPress has confirmed the action.
Server-side measurement is not a way to bypass consent. If measurement consent is required, the server event should follow the same permission.
Pixel vs Conversions API
| Layer | Strength | Limitation |
|---|---|---|
| Browser Pixel | Fast page-view and client context | Can be blocked in the browser |
| Conversions API | Runs after WordPress confirms an action | Needs credentials, event IDs and error handling |
Using both can be more resilient. It is not required for every site.
Event IDs
When the same conversion is sent twice, the two payloads should share one event ID. PixelBridge is designed to generate or reuse that ID so OpenAI Ads measurement can deduplicate the pair.
WordPress implementation
Typical server events come from:
- A confirmed form submission hook.
- A booking confirmation hook.
- A WooCommerce order status that means the purchase is real.
PixelBridge can send those server events. Use the same event ID as the browser event when both fire.
Debugging
Check diagnostics for connection status, then inspect the latest events. If a browser event succeeds and the server event fails, keep the failure visible instead of retrying blindly. See Troubleshooting and the Conversions API guide.