OpenAI Ads
SyncBeacon has a built and shipped connector that sends store orders to OpenAI Ads from the server. This page separates what is implemented from what OpenAI has or hasn't approved, so you can decide with accurate information.
Works with
Shopify · WooCommerce · Shopware
Connects to
OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads · TikTok (upcoming) · GA4 (coming soon)
Built for modern ecommerce
Simple to set up · EU-hosted · GDPR-ready · Secure event processing
Conversion events we support
PageView · ViewContent · Search · AddToCart · InitiateCheckout · AddPaymentInfo · Purchase
Also supported
OrderCancelled · Lead · CompleteRegistration
Last updated:
Let's start with the part most pages skip. SyncBeacon has implemented a connector for OpenAI Ads and it is shipped in the product. That is a statement about our code. It is not a statement about OpenAI's approval. SyncBeacon is not an approved OpenAI Ads API partner, we don't claim to be an official OpenAI partner, and we don't claim a marketplace listing.
| Status | What we can say |
|---|---|
| Connector built and shipped | Yes. You can connect it in Integrations. |
| Sends server-side conversion events | Yes, from your store's order data |
| Approved OpenAI Ads API partner | No |
| Official OpenAI partner or marketplace listing | Not claimed |
Availability of ChatGPT Ads itself, and who can run them, is decided by OpenAI and can change. Check OpenAI's own documentation for your market.
Any new ad channel starts with thin data, and ChatGPT Ads is no exception. Budget decisions made on a handful of conversions are fragile, so getting purchase events into the platform early matters more than polishing dashboards later. We wrote about the channel in OpenAI Ads for ecommerce, and a measurement follow-up is in measuring ChatGPT Ads conversions.
Browser tags are the weak point here too: blockers and consent banners can stop a client-side tag before it reports. Server-side delivery, explained in our server-side tracking guide, sends the order from the relay once the store has it.
For OpenAI Ads measurement, the connector sends conversion events such as order created, checkout started and items added, with these fields:
| Field | Sent | Notes |
|---|---|---|
| Yes | SHA-256 hashed, and only when consent allows | |
| Click reference (oppref) | Yes | Captured from the landing URL by the SyncBeacon script |
| IP address and user agent | Yes | When present on the event |
| Amounts and line items | Yes | From the order |
| Phone number | No | Not sent |
| City, ZIP or country | No | Not claimed; store orders don't reliably carry them to this connector |
That means matching leans on the click reference and the hashed email. Orders that come from a visitor who never clicked an ad and who has not consented to email matching give OpenAI very little to connect to. The tracker remembers the click reference between the visit and the order, so a purchase confirmed later by the store can still be tied to the click.
ChatGPT Ads conversion tracking is connected with an API key, not a browser login. Unlike Meta and Google, there is no sign-in-and-approve screen, so you paste a key.
Connect your store
Shopify, WooCommerce or Shopware.
Add your OpenAI Ads API key
In Integrations, paste the key from your OpenAI Ads account. SyncBeacon can create the pixel and the conversions key for you.
Keep the tracker script live
The script is what captures the oppref click reference on landing pages.
Check delivery
Place a test order from an ad click and check the delivery status on the Conversions page.
The connector works with the three launch sources. Shopify orders arrive from order webhooks after an OAuth install. WooCommerce orders arrive through the free plugin, which registers signed webhooks. Shopware orders are read through the Admin API with an integration key, about every two minutes. In all three cases the click reference comes from the SyncBeacon script on your storefront, so the script has to be live on the pages your ads point to.
Browser events beyond purchases depend on the theme or storefront app, so check what actually fires on your own store instead of assuming every event is present.
Because the channel is new, the order of operations matters more than the tooling. A rollout that works for most stores looks like this:
SyncBeacon's part is delivery. How OpenAI Ads attributes, reports and optimises on those events is up to OpenAI, and we can't speak for it. If you want a cross-channel view of the same orders, the ecommerce conversion tracking overview shows how the destinations fit together.
The same relay also feeds Meta, Google Ads, Pinterest, Snapchat and X. Read how consent is handled on the Consent Mode v2 page, and see pricing for what each plan includes.
Supported today
Stores: Shopify · WooCommerce · Shopware
Ad platforms: OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads
FAQ
No. The OpenAI Ads connector is implemented and shipped, but SyncBeacon is not an approved OpenAI Ads API partner and we don't claim an official partnership or marketplace listing.
It means reporting purchases and other store events back to the ad platform so campaigns can be measured and optimised. SyncBeacon does this server-side from your store's order data.
Conversion events with amounts and line items, a hashed email when consent allows, the oppref click reference, and IP address and user agent when present. Phone numbers aren't sent.
With an OpenAI Ads API key pasted into Integrations. It isn't a browser OAuth login. SyncBeacon can create the pixel and the conversions key from that key.
Shopify, WooCommerce and Shopware. Purchases come from the store's order data, and the click reference comes from the SyncBeacon script on your storefront.
Get started in minutes. No developer required for Shopify, WooCommerce, or Shopware setup.
Solutions
Compare
Learn