Documentation
Conversion events
Track page views and meaningful WordPress actions as conversion events, then verify that each event is sent once.
Last updated: 2026-09-03. Written by PixelBridge team.
PixelBridge maps WordPress actions to conversion events so OpenAI Ads measurement can connect page views, leads, appointments, registrations and purchases with advertising activity. Only enable events that represent a real customer action.
Event types
| Event | Typical WordPress trigger | Notes |
|---|---|---|
page_viewed | Public page load | Usually the first event after the pixel loads |
lead_created | Successful form submission | Use after the form is confirmed, not on page load |
appointment_scheduled | Booking confirmation | Fire after the appointment exists |
registration_completed | Account or membership signup | Fire after the account is created |
purchase | WooCommerce order | Planned. Not released yet |
Event names and required fields can change. Confirm the current list in official OpenAI Ads measurement documentation before you treat a name as final.
Page views
page_viewed should fire once per public page view after consent is granted. Do not fire it on every AJAX refresh.
Leads
A lead event should represent a completed enquiry, not a field focus or a button click. Supported form integrations will hook the plugin's success callback. Custom JavaScript is a fallback, not the default path.
Appointments
Appointment events should fire when a booking is confirmed. Calendar embeds often complete inside an iframe. Cal.com, Calendly, Amelia and Bookly are not connected yet.
Purchases
WooCommerce sends order_created after the order is confirmed. Include an order identifier and, where allowed, a conversion value. See the WooCommerce guide.
Deduplication
If the same conversion is sent from the browser and the Conversions API, both payloads need a shared event identifier. See Conversions API.