OpenAI Ads tracking for Elementor Forms
Turn a successful Elementor form submission into an OpenAI Ads lead_created event, with consent and a shared event ID when you also send the Conversions API.
Last updated: 3 September 2026. Written by PixelBridge team.
Successful Elementor form submissions should become OpenAI Ads conversion events only after the form confirms that the submission was accepted. The typical event is lead_created. Fire it once, attach an event ID if a server event will also be sent, and wait for measurement consent.
What this integration is for
Elementor Forms are often the conversion on a landing page: a quote request, a demo request, a newsletter plus contact details, or a content download. OpenAI Ads measurement needs that success state as a conversion, not a page view of the page that happens to contain the form.
PixelBridge is an independent WordPress plugin. It is not an official Elementor or OpenAI product. The Elementor Forms connector is listed because it is a first-wave target, not because it is live.
Elementor's own builder and form settings are documented by Elementor. Use those docs for form fields, actions after submit and spam protection. This page only covers how a confirmed submission should map to OpenAI Ads measurement.
When a form submission is a conversion
A conversion is a confirmed lead, not a button click. Elementor can show inline success text, redirect to a thank-you page, or run an action after submit. The measurement event should wait for the same success condition Elementor uses to treat the submission as stored or sent.
Do not fire a lead event when:
- The form widget renders
- A field receives focus
- The submit button is clicked
- Validation fails
- A spam or required-field error is returned
- An AJAX request starts but has not succeeded
If the form redirects to a thank-you page, measure the submission success, not merely that the thank-you URL loaded. Other traffic can open that URL. If you also send page_viewed on the thank-you page, keep that as a page view. The lead event still belongs to the form success.
See conversion events for the difference between page views, leads and purchases.
Planned event mapping
The intended mapping is:
| Elementor state | OpenAI Ads event | Notes |
|---|---|---|
| Form submitted and accepted | lead_created | Default for contact, quote and enquiry forms |
| Newsletter-only signup, if you treat it as a registration | registration_completed | Only if the account or list signup is confirmed |
| Booking form that creates an appointment | appointment_scheduled | Only after the appointment exists |
Most Elementor Forms on marketing sites should use lead_created. Do not create a custom event name unless official OpenAI Ads documentation says you need one. Confirm current event names in the OpenAI Measurement Pixel documentation.
If several forms exist on one site, each successful form can still send lead_created. Distinguish them later with form name or form ID in diagnostics, not by firing extra events on page load.
Browser events
A planned browser event should run after Elementor's success callback, once the pixel is initialized. Popup forms, slide-in forms and forms inside Elementor popups are still forms. The trigger is submission success, not the popup opening.
Watch for these Elementor-specific issues:
- Multiple forms on one page: each success should send one event for that submission.
- Cached landing pages: the pixel and consent state still need to be current.
- Redirect after submit: the browser context can change before a poorly timed script runs. The integration should bind to the success hook, not to the destination page alone.
- Single-page layouts: scrolling to a form is not a conversion.
Until the integration ships, custom JavaScript is a fallback, not the supported path. If you test manually, still wait for the success state. See OpenAI Ads Pixel for WordPress.
Server-side events
A browser event can miss a conversion when the visitor closes the tab, a content blocker removes the pixel, or the success message is rendered without a full page load. A Conversions API event can still record the lead after WordPress has the submission.
The planned model is to send the server event from the Elementor form success path in PHP, with the same event name and a shared event ID. Do not send a server lead when the form failed validation.
The Conversions API can send the same lead from WordPress after the form succeeds. See Conversions API.
Deduplication and consent
If both layers fire, they must share an event ID. One submission is one lead.
Consent applies to both layers. If measurement consent is required and has not been granted, do not load the pixel and do not send the server event. PixelBridge does not replace an Elementor popup used as a cookie banner. See consent.
Planned setup
When the integration is released, the intended setup is:
- Install and activate PixelBridge from WordPress.org.
- Enter the OpenAI Ads Pixel ID.
- Enable the Elementor Forms integration.
- Choose which forms should send
lead_created. - Keep consent rules on.
- Submit a test form and confirm the event appears once in diagnostics.
Troubleshooting
- Submit the form until Elementor shows its success state.
- Confirm you are not looking at a validation error styled like success.
- Grant measurement consent.
- Confirm one event, not one event per keystroke or per AJAX retry.
- If a thank-you redirect is used, confirm the lead fired on success rather than on every visit to that URL.
- Use troubleshooting if the pixel itself never loaded.