OpenAI opened its self-serve Ads Manager in beta on May 5, 2026. Five weeks later, on June 11, it added product feed campaigns. advertisers upload a catalog, and Ads Manager generates sponsored placements from the product data itself.
That second launch changed what “setting up OpenAI Ads on Shopify” means. The channel now runs on four inputs, not one:
- Conversion data: a pixel plus server-side Conversions API delivery, so OpenAI’s bidder learns from real purchases instead of the fraction a browser pixel survives with.
- A product feed: a structured catalog delivered over SFTP, formatted to OpenAI’s spec, kept current as prices and stock change.
- Performance data: net revenue, ROAS and CPA per campaign and per product, reconciled against real orders.
- Audiences: hashed customer lists pushed to Ads Manager for targeting and exclusion.
Almost every Shopify app in this category covers one of the four. That is the most useful thing to know before you install anything, and it is the axis this comparison is built on.
Disclosure: Orichi builds one of the apps in this comparison. We have written the criteria so they apply to every app equally, including ours and there is a section below on when you should not pick ours. Judge the criteria first, then judge whether we meet them.
If you want to know the criteria in detail: What to Look For in an OpenAI Ads App for Shopify
This isn’t a feature-by-feature checklist. Checklists make most apps in this category look interchangeable, because most list similar bullet points on their App Store pages. What actually separates them is coverage. how much of the four-input list above each app handles on its own, versus how much it leaves for you to solve with a second install. That’s the axis every section below is built on.
![]()
Six Things That Separate a Full Setup From a Partial One
If you haven’t installed the pixel yet, how to set up the OpenAI Ads pixel on Shopify walks through the OpenAI-side steps, the Ads Manager account, the Pixel ID, business verification. The six criteria below are what separates an app that checks that one box from one that covers the channel.
1. Server-side delivery, not just a browser pixel
ChatGPT traffic routes through in-app browsers on iOS and Android, through Safari’s Intelligent Tracking Prevention, and past whatever ad blocker the user has installed. A browser-only pixel loses a meaningful share of purchases before OpenAI’s bidder ever sees them. Server-side delivery through the Conversions API isn’t optional hardening, it’s the baseline for the algorithm to learn from real orders instead of the fraction a client-side script survives to report.
2. Deduplication via shared event ID
When both the browser pixel and the server-side Conversions API report the same purchase, OpenAI needs one signal, not two. The app has to send the same event ID on both the client event and the server event so OpenAI’s system can collapse them into a single conversion. Skip this, and a sale gets counted twice: revenue looks inflated, ROAS looks better than it is, and the bidder optimizes toward numbers that aren’t real.
3. oppref capture
OpenAI’s browser pixel captures the oppref attribution identifier automatically, the ChatGPT-ads equivalent of a gclid or fbclid. The Conversions API does not do this for you: OpenAI’s own developer documentation says plainly that capturing oppref is the advertiser’s job, not the API’s. An app has to read the oppref value from the landing page URL, store it in a first-party cookie so it survives to the point of purchase, and attach it to every server-side event that follows.
An app that forwards events server-side without carrying oppref will still deliver the event successfully, OpenAI accepts it, and it shows up in reporting. What it won’t do is tie back to a click. That failure mode is quiet: nothing errors, no event gets rejected, the dashboard just fills up with conversions OpenAI can’t attribute to a specific ad or campaign. For a merchant deciding which campaigns are actually working, that’s the difference between a ROAS number you can act on and one you can’t.
4. Feed coverage
OpenAI’s product feed campaigns pull from a structured catalog uploaded over SFTP, in OpenAI’s own feed spec not a generic CSV export. That means a non-empty description field for every item, prices formatted the way the spec expects, and eligibility flags set correctly so a product isn’t silently excluded from feed-based ads. An app that only handles the pixel leaves this step undone, which means installing a second app just to get the catalog side working, the exact gap OpenAI’s June 11 feed launch created for anyone whose tracking app stopped at conversions.
5. Hashing and privacy
Any customer data sent to OpenAI for audience matching, email, external ID needs to be lowercased, trimmed, and hashed with SHA-256 before it leaves the store; OpenAI’s matching endpoint doesn’t take plaintext. The app also needs to respect Shopify’s Customer Privacy API, so a customer who has opted out of marketing tracking doesn’t have their data forwarded regardless.
6. Visible delivery status
Before spending real budget on a new channel, a merchant needs to see, not assume that events are actually reaching OpenAI: which ones fired, whether they were accepted, and how tracked conversions compare to real Shopify orders. An app that only shows a green checkmark right after setup, with no ongoing visibility after that, is asking the merchant to trust a black box once the money starts moving.
OAI-AdsBotis OpenAI’s dedicated ads crawler a separate bot fromGPTBot,OAI-SearchBot, andChatGPT-User. It reviews ad landing pages for policy compliance before an ad is eligible to serve. Arobots.txtrule written to blockGPTBotfor training-data reasons can end up blockingOAI-AdsBottoo if it isn’t scoped carefully and that strips a product page of ad eligibility before the pixel ever gets a chance to fire.
Four Groups of Apps
Map these back to the four inputs and the split becomes obvious. Pixel-only apps handle conversion data and stop there. Feed-only apps handle the catalog and assume tracking is already solved elsewhere. Multi-channel platforms handle conversion data and performance reporting, built to span more than one ad platform at once rather than just OpenAI. Only the last group is built to cover all four from a single install.
Feature comparison (checked against App Store listings on 10.2026)
Features change often. Check each app’s listing before you install.
| Feature | Orichi | Reach Pixel | Count | Xpay | Neural Matrix | Omega |
|---|---|---|---|---|---|---|
| Pixel + CAPI with dedup | Yes | Yes | Yes | Yes | Yes | Yes |
| Event Match Quality score | Yes | Yes | Paid | Yes | Yes | No |
| Broken-tracking alerts | Yes | No | Paid | Paid | No | Yes |
| Delivery log with OpenAI response | Yes | No | Yes | No | Yes | No |
| Reconciliation with real orders | Yes | Yes | No | Yes | No | No |
| Revenue net of refunds | Yes | No | Paid | No | No | No |
| Campaign & product ROAS | Yes | Paid | No | Paid | Paid | Yes |
| Product feed sync | Yes | Separate app | Paid | No | Yes | No |
| Per-country feeds | Yes | No | No | No | No | No |
| Hashed audiences from segments | Yes | No | No | No | No | No |
If you install from the first group, you will be back in the App Store within a week looking for something from the second. That is not a knock on those apps, several are well built, it is a scoping decision they made. Just know it before you install.
If You Already Track Other Channels Server-Side
If OpenAI Ads is your fourth or fifth channel rather than your first move into paid social, a single-purpose pixel app might be the wrong layer to add. Platforms like Aimerce, WeltPixel, Elevar, and Triple Whale already handle server-side tracking and reporting across Meta, Google, TikTok, and other channels, for most of them, OpenAI Ads is one more connector inside a system that already exists, not a new one to stand up.
If you already run a multi-channel server-side tracking app, add OpenAI Ads inside it. Do not stack a second pixel app on top, you will double-fire events and spend a week debugging attribution that was never broken.
Which One Fits Your Store
None of the four groups above is the wrong choice in every situation. The right one depends on what you’re already running and how much of the remaining setup you’re willing to own yourself.
Pick a pixel-only app if: you run a lead-gen or service business with no product catalog. There’s no feed to sync, so tracking is the whole job, a feed-capable app would just add complexity you won’t use.
Pick a feed-only app if: you already have server-side tracking working elsewhere and just need the catalog side connected, without duplicating conversion tracking you’ve already built.
Pick a multi-channel platform if: OpenAI Ads is your fourth or fifth channel and you need one source of truth alongside Meta, Google, and TikTok, not a fifth dashboard to check separately.
Pick Orichi if: you want all four layers in one app, and you don’t want to pay for a large platform’s pricing tier while the channel is still in beta. Additionally, if you want to install multiple OpenAI Pixels properly with 30 seconds, don’t hesitant to Install Orichi OpenAI Ads Pixel & Feed
New update: a live health panel has already launched in the Orichi dashboard!
FAQ
Is OpenAI Ads the same as ChatGPT Ads?
They’re the same product under two names. OpenAI Ads Manager, at ads.openai.com, is the platform; “ChatGPT Ads” describes where those ads appear, inside ChatGPT conversations. Merchants and app listings use both terms interchangeably.
Who is Orichi?
Long before launching their dedicated app for OpenAI Ads, OrichiCommerce had already established itself as a Shopify tracking powerhouse, renowned for their multi-pixel solutions across Orichi Facebook Pixel, Orichi TikTok Pixel, and so on. Backed by a high-performance server infrastructure, advanced event deduplication algorithms, and battle-tested technology to bypass iOS 14+ restrictions and ad-blockers, OrichiCommerce seamlessly ported their elite, conversion-focused CAPI framework directly into their OpenAI Ads integration
Do I need OpenAI Ads access before installing a pixel app?
Yes. You need an OpenAI Ads Manager account with a Pixel ID and a Conversions API key before any Shopify app has something to connect to. Sign up at ads.openai.com and complete business verification first, then install the app and enter those credentials.
Can I install the pixel if OpenAI Ads is not live in my market yet?
Yes, installing the pixel doesn’t depend on your market being live. ChatGPT ads rolled out to the US first, then Canada, Australia, and New Zealand, followed by the UK, Mexico, Brazil, Japan, and South Korea. Installing early means conversion data is already flowing the day your market goes live, instead of losing the first weeks to setup.
What events does OpenAI Ads track?
The Conversions API supports standard commerce events, page views, product views, add-to-carts, checkouts started, and purchases, plus custom events you define yourself. Each event type has a matching data shape, so check OpenAI’s supported-events reference before sending anything custom.
Do I need Shopify Plus?
No. The Conversions API, product feeds, and the pixel all work on any Shopify plan; none of it is gated behind Plus. The customer-privacy consent tools these apps rely on to respect opt-outs are available on every plan too.
What is oppref and why does it matter?
oppref is OpenAI’s click identifier, the equivalent of Google’s gclid or Meta’s fbclid. The browser pixel captures it automatically; the Conversions API does not, so a server-side-only setup has to capture and forward it itself, or conversions arrive with no click for OpenAI to attribute them to.