TL;DR
OpenAI Ads went from a US test in February 2026 to roughly 40 markets by late August: self-serve access runs in the US, UK, Canada, Australia, New Zealand, Japan, South Korea, Mexico and Brazil, and 31 European markets opened on August 24, 2026 through OpenAI's sales team and partners [3]. The platform shipped with the two things a performance channel needs on day one, CPC bidding and conversion measurement through a pixel plus a Conversions API [1], and added conversion-optimized (oCPC) campaigns in July [4]. WeltPixel Conversion Tracking supports OpenAI Ads as one of its nine integrations, wired the same way as our Meta, TikTok and Google Ads channels: the purchase confirmed server-side from Shopify's order webhook, so the event your bidding depends on does not depend on the buyer's browser. If you have OpenAI Ads access, connecting your store takes a Pixel ID and an API key. This post covers what the integration sends, how to set it up, and what to check before your first campaign.
Key Takeaways
- OpenAI Ads is in beta: US advertisers can register at ads.openai.com, and rollout is gradual [1][2]. You need platform access before there is anything to track.
- OpenAI launched CPC bidding alongside CPM [1]. CPC campaigns are judged, and eventually optimized, on what happens after the click, which is exactly the data conversion tracking supplies.
- The WeltPixel integration sends five events: page views, product views, add to cart, checkout started, and purchases (as
order_created). - Purchases go out server-side from Shopify's order webhook, not just from the browser, so blocked or abandoned browser sessions still report the sale.
- Setup needs two values from ads.openai.com: a Pixel ID from a Web data source, and a Conversions API key. The key starts with
sk-svc-and is shown only once, so store it when you create it. - OpenAI Ads works with multi-pixel and per-Market routing on the Plus plan, the same as every other channel in the app.
What OpenAI Ads is, and where it stands right now
OpenAI started selling ads in ChatGPT through managed partnerships, opened a self-serve Ads Manager in early May 2026 [1], and has expanded fast since. The platform lives at ads.openai.com [2]. OpenAI Ads is the product name; most merchants just say ChatGPT ads, since that is where the ads run. A July 2026 update added conversion-optimized campaigns, average daily budgets and intraday pacing [4], and on August 24, 2026 the platform opened in 31 European markets, where ads run without personalization and are bought through OpenAI's sales team and partners rather than self-serve [3].
Three measurement details matter for merchants. Measurement shipped with the platform rather than being bolted on later: OpenAI supports pixel-based tracking and a Conversions API, and its reporting counts actions like purchases after someone interacts with an ad [1]. Reporting is aggregate only, with no access to user conversations or personal data [1], conversions appear in reports within 24 to 48 hours, and view-through conversions sit in a separate 1-day column that does not feed CPA [5]. And conversion tracking has to be live before campaign creation to unlock oCPC bidding [4], which makes the setup below a prerequisite rather than a nice-to-have.
That second detail is the reason this integration exists. A channel that bills per click and reports per conversion is only as useful as the conversion data you feed it. If nothing tells OpenAI a purchase happened, your campaigns report clicks and nothing else, and you are back to judging a paid channel on traffic volume.
What the integration sends
WeltPixel Conversion Tracking maps Shopify's events to OpenAI Ads' event taxonomy:
| Shopify event | OpenAI Ads event |
|---|---|
| Page view | page_viewed |
| Product view | contents_viewed |
| Add to cart | items_added |
| Checkout started | checkout_started |
| Purchase | order_created |
The page view fires from the browser pixel and again from the server, carrying a shared event ID so OpenAI counts the pair once. Everything else, product views, add to carts, checkout starts, and the purchase, is delivered server-side through the Conversions API. When Shopify records the order, the order webhook sends order_created with the identifiers OpenAI matches on: its own click and browser references captured during the session and bridged through checkout, plus a SHA-256 hashed email and customer ID, country, city, zip, IP and user agent. That is the same architecture we use for Meta, TikTok and Google Ads, and it exists for the same reason. The purchase is the event your bidding and reporting depend on, and it is also the event most likely to be lost browser-side, to ad blockers, iOS privacy features, or a buyer who closes the tab on the thank-you page.
You can also limit which events are sent per pixel from the app's settings if you only want a subset.
How to set it up
You need two values from OpenAI, then a paste into the app. The full walkthrough with screenshots lives in our documentation; here is the short version.
1. Get your Pixel ID. In ads.openai.com, open Tools, then Conversions, and create a Data Source with type Web. The data source's Pixel ID is the first value you need.
2. Create a Conversions API key. In the same Conversions area, open Conversion keys and create a new key. It starts with sk-svc- and OpenAI shows it exactly once, so copy it before closing the dialog. If you lose it, you create a new key rather than recovering the old one.
3. Connect the app. In WeltPixel Conversion Tracking, open the OpenAI Ads integration, paste the Pixel ID and the API key, and save. The app validates the pair against OpenAI the moment you save, so a typo fails at setup instead of silently in week three. There is no separate test-events mode for OpenAI the way Meta has one; the save-time validation is the check. Events start flowing on the next storefront activity; purchases appear in your OpenAI data source as order_created.
If you run multiple pixels or sell across Shopify Markets, OpenAI Ads behaves like every other channel in the app: on Plus you can add multiple OpenAI pixels and assign each one to the Markets it should fire for.
Which plan includes it
OpenAI Ads is part of the Plus plan at $39/month, which covers every integration in the app: GA4, Meta, TikTok, Google Ads, Reddit, OpenAI Ads, Pinterest, Snapchat, and Klaviyo, with unlimited orders. The free plan covers GA4 tracking only, up to 100 storefront orders a month.
FAQ
Is OpenAI Ads the same as ChatGPT ads?
Yes. OpenAI Ads is the official name of the ad platform (it lives at ads.openai.com), and the ads themselves run inside ChatGPT, so most people call them ChatGPT ads. Whichever name you use, the tracking setup is the same: a Pixel ID plus a Conversions API key from your OpenAI Ads account.
Do I need OpenAI Ads access before setting this up?
Yes. The integration sends events to a data source inside your OpenAI Ads account, so the account comes first. Self-serve access covers the US, UK, Canada, Australia, New Zealand, Japan, South Korea, Mexico and Brazil at ads.openai.com [2]; the 31 European markets that opened in August 2026 buy through OpenAI's sales team and partners for now [3].
Which events does the integration send to OpenAI Ads?
Five: page_viewed, contents_viewed, items_added, checkout_started, and order_created. Purchases are sent server-side from Shopify's order webhook as well as measured from the storefront.
I lost my Conversions API key. Can I see it again?
No. OpenAI shows the key once, at creation. Create a new key in the Conversion keys section and update it in the app.
Does OpenAI Ads work with multi-pixel and per-Market routing?
Yes, on the Plus plan. You can run multiple OpenAI Ads pixels and assign each to specific Shopify Markets, the same as every other channel in the app.
Sources
- https://www.searchenginejournal.com/openai-launches-self-serve-ads-manager-for-chatgpt/573971/ (May 5, 2026)
- https://ads.openai.com/ (accessed 2026-08-27)
- https://searchengineland.com/chatgpt-ads-are-expanding-to-31-european-countries-485468 (August 19, 2026)
- https://openai.com/index/new-ways-to-buy-chatgpt-ads/ (July 24, 2026)
- https://help.openai.com/en/articles/20001409-conversion-measurement (accessed 2026-08-27)