OpenAI Ads launched with a pixel, a Conversions API, and the same attribution problem every platform has: it can see ad clicks but not what happens after. If your conversions happen in a CRM, a booking system, or a payment processor, OpenAI Ads is flying blind. ConversionLoop closes that loop by sending your actual conversion data back to OpenAI Ads server-side, using deterministic identifiers instead of third-party cookies.


The OpenAI Ads pixel fires in the browser. Every iOS user with default privacy settings, every Safari visitor, every person who clicks your ad on one device and converts on another — the pixel misses them. For B2B leads and SaaS trials, the conversion often happens days after the initial click, in an email flow or a sales call. The pixel has no visibility there at all. Server-side conversion tracking via the OpenAI Ads CAPI endpoint fixes this by sending conversion data directly from your server, not the visitor's browser.
Why the manual process breaks — and what changes when you automate it
ConversionLoop sits between your CRM or payment system and the OpenAI Ads CAPI endpoint. When a conversion happens — a lead created, a trial started, a deal closed — ConversionLoop formats and sends the event to OpenAI Ads automatically.
A visitor clicks your OpenAI ad. The oppref parameter is captured and stored against their email.
The visitor converts — fills out a form, starts a trial, or makes a purchase.
Your CRM, Stripe, or booking platform fires a webhook to ConversionLoop.
ConversionLoop matches the conversion to the original click using the stored identifier.
The event is sent to OpenAI Ads CAPI with hashed PII, conversion value, and event type.
OpenAI Ads registers the conversion and optimizes future bids toward high-converting audiences.
14-day free trial. No credit card. Setup takes 10 minutes.
Start free trialFollow these steps once. Everything after is automatic.
Lead CreatedForm submission or inbound contact. Send this for every qualified lead that enters your pipeline.
Trial StartedHigh-intent signal for SaaS. Ties ad clicks to free trial activations for top-of-funnel optimization.
Subscription CreatedPrimary revenue event. Pass the subscription value for ROAS-based bidding.
Deal Closed / WonOffline CRM conversion. Upload when a lead closes to attribute real revenue back to ad campaigns.
Appointment BookedService business conversion. Pass booking value for value-based bidding on high-LTV bookings.
Similar concept, different endpoint. OpenAI Ads has its own Conversions API at bzr.openai.com. ConversionLoop supports both natively — you can send the same conversion event to OpenAI Ads and Meta CAPI simultaneously from a single webhook.
OpenAI Ads uses the oppref parameter — a click identifier appended to your ad destination URLs. ConversionLoop's cl.js captures this on landing and stores it against the user's email so it can be matched at conversion time.
Yes. When a rep marks a deal as Closed Won in your CRM, your CRM fires a webhook to ConversionLoop, which uploads the conversion to OpenAI Ads. The attribution window is typically 30 days from the original click.
Yes, and it makes the pixel more effective. The pixel handles real-time browser events. ConversionLoop fills in the gaps: CRM conversions, cross-device events, and offline revenue that the pixel never sees. Both run in parallel.


Stop optimizing on guesswork. Every invoice, treatment, and booking — tracked and attributed automatically.
Start free — 14 days on usNo credit card required · 10-minute setup · Cancel anytime