ChatGPT Ads Integration

ChatGPT has become one of the largest consumer software surfaces in the world: OpenAI announced it passed 900 million weekly active users in February 2026, with usage reported to be approaching a billion weekly users by mid-2026. A structured, OpenAI-compatible product feed is the only mechanism that lets your catalog exist on that surface at all — without one, your products cannot appear in ChatGPT's shopping results, cannot be eligible for Instant Checkout, and cannot power product-based campaigns in Ads Manager.

OpenAI reuses the same base "Agentic Commerce" catalog schema across all three of those use cases — organic shopping discovery, checkout eligibility, and paid product-feed ads — distinguished mainly by a handful of eligibility flags on each item. That means one well-built, compliant feed does triple duty rather than requiring three separate integrations. Because eligibility (regions, tiers, merchant partners) is still expanding in stages, getting a compliant feed live now is largely about being positioned to be included as OpenAI widens access, rather than guaranteed exposure today.

It's easy to conflate three genuinely different OpenAI features that all rely on product data, so it's worth separating them clearly:

1. Shopping results in ChatGPT Search — an organic, algorithmically selected product carousel that can appear when a question shows shopping intent. OpenAI's Help Center is explicit that these results are "not ads, nor influenced by any OpenAI partnerships" and are selected independently by ChatGPT based on relevance to the user's query.
2. Instant Checkout — for select eligible items, lets a user complete a purchase inside the ChatGPT conversation instead of leaving for the merchant's site, using the Agentic Commerce Protocol (an open standard OpenAI built with payment partners such as Stripe). It's currently available to ChatGPT Pro, Plus and logged-in Free users in the US. OpenAI publicly acknowledged in March 2026 that the first version "did not offer the level of flexibility that we aspire to provide" and shifted toward letting merchants use their own checkout while OpenAI focuses on discovery. As of now it is enabled for Etsy and a short, named list of Shopify merchants (including Glossier, SKIMS and Spanx), with OpenAI saying more merchants are coming.
3. Product-feed ads in Ads Manager — paid, sponsored placements built dynamically from your catalog rather than manually built per product. This requires the catalog to carry an extra ads-eligibility flag and meet a minimum feed size, and it is the feature most directly meant by "ChatGPT Ads."

All three draw on the same underlying feed format, but only the third is advertising in the strict sense.

OpenAI's own developer documentation for its commerce program describes accepted files as UTF-8, delimited text (CSV or TSV), optionally gzip-compressed, alongside JSON; feeds intended to also serve Google Merchant Center should reuse GMC's canonical, lowercase, underscore-separated field names where they overlap. Onboarding follows a validate-then-scale pattern: an initial sample feed is checked for schema compliance before OpenAI approves recurring delivery of full "daily snapshot" catalogs to a secure SFTP endpoint issued during onboarding.

For paid product-feed ads specifically, the feed connection and SFTP credentials are created directly inside Ads Manager (Tools → Feeds → Create Feed), and OpenAI documents a required catalog size of at least 1,000 and no more than 2,000,000 products for that use case. The ads-specific schema is the same base product schema described above, plus one additional required flag: is_ads_eligible. Because none of this runs through a fully open, self-service portal yet — account approval and SFTP setup are still coordinated with OpenAI directly, or through its feed-partner ecosystem — exact turnaround times and support channels should be expected to keep evolving as the program matures.

OpenAI publishes a genuine field-level product schema for this program (developers.openai.com/commerce/specs). The table below covers the core fields most merchants need to get right first; the full specification also documents variant, fulfillment, returns, review and geo-targeting fields.

Because OpenAI still runs this as an approval-gated, SFTP-based onboarding rather than an open self-serve portal like a traditional merchant center, the practical path today looks like this:

1. Map your existing catalog — or your existing Google Shopping / GMC feed, since OpenAI designed its field names to be broadly compatible — to OpenAI's commerce schema inside Feedance.
2. Set the OpenAI-specific eligibility flags per product: is_eligible_search, is_eligible_checkout, and, if you plan to run paid product-feed ads, is_ads_eligible.
3. Generate a compliant CSV/TSV or JSON export and validate it against required-field and format constraints (unique item_id values, ISO currency and country codes, HTTPS URLs that resolve) before your first submission.
4. Deliver the file to the SFTP endpoint OpenAI issues after approval — the general commerce onboarding endpoint if your goal is shopping/checkout eligibility, or the endpoint generated inside Ads Manager's Feeds tool if the goal is product-feed ads.
5. Keep the feed refreshing on a recurring schedule from Feedance so price, stock and promotions submitted to OpenAI stay aligned with what's live on your storefront.

The account-level approval and initial SFTP handshake with OpenAI itself is a step every merchant currently coordinates directly with OpenAI (or through its feed-partner ecosystem) — Feedance's role is to make sure the export you hand over is complete, correctly formatted and kept current. Expect this process to get simpler as OpenAI's commerce program matures and access broadens.

OpenAI's own commerce documentation describes an initial sample feed used purely for validation, after which merchants move to recurring "daily snapshot" delivery of the full catalog. For paid product-feed ads specifically, Ads Manager processes a newly uploaded catalog in anywhere from a few minutes to a few hours depending on feed size. OpenAI has not published one single mandatory refresh interval that covers every feed use case; feed-management vendors working with the program generally recommend refreshing price- and stock-sensitive fields more often than once a day, since these fields directly affect Instant Checkout and ad eligibility — but that is vendor best-practice guidance, not a documented OpenAI requirement, and should be treated accordingly.

OpenAI has not published a formal, numbered error-code reference for this program the way some longer-established shopping platforms have. Feed-management vendors and early integrators working with OpenAI's commerce program do, however, consistently report the same handful of rejection causes, worth checking before every submission:

1. Missing one of the required base fields (item_id, title, price, availability, seller_name, return_policy, etc.).
2. Non-unique or unstable item_id values across successive feed submissions.
3. Price or availability in the feed not matching what's currently live on the merchant's own site.
4. Image, product or return-policy URLs that are not HTTPS or don't resolve with a 200 response.
5. Missing seller privacy-policy or terms-of-service URLs when is_eligible_checkout is set to true.
6. Incorrect ISO country codes (target_countries, store_country) or currency codes on price fields.

Treat this list as informed guidance from the feed-management community rather than an official OpenAI error catalog — none has been made public as of this writing.

These are general best practices for showing up well in AI-driven shopping surfaces, not OpenAI-documented requirements — but they align with how OpenAI describes its own ranking signals:

1. Keep price and stock in your feed exactly consistent with your live site; mismatches are one of the most commonly reported causes of rejected or suppressed items.
2. Write plain, factual titles and descriptions rather than marketing copy — OpenAI's spec explicitly favors accurate, descriptive text over promotional language.
3. Populate the optional-but-influential fields OpenAI's schema supports: reviews, star ratings, rich media (extra images, video, 3D models) and performance signals, all called out as improving ranking, relevance and user trust.
4. Maintain one clean, well-structured source feed that can be reused across GMC, Meta and OpenAI rather than maintaining parallel, drift-prone exports for each channel.
5. Set is_eligible_checkout and is_ads_eligible deliberately at the SKU level rather than blanket-enabling them, so only genuinely fulfillable, policy-compliant items are offered for in-chat purchase or ads.

Is "ChatGPT Ads" OpenAI's own name for this feature? Not exactly. OpenAI's own product is branded "Advertise in ChatGPT," run through OpenAI Ads Manager at ads.openai.com. "ChatGPT Ads" is the term most commonly used in press and marketing coverage for the same feature.

Does every merchant need a feed just to appear in ChatGPT's shopping answers? Yes — organic shopping results, Instant Checkout eligibility, and product-feed ads all draw on the same underlying product feed OpenAI ingests; there is no way to be represented without one.

Is Instant Checkout required to run ChatGPT Ads? No. They are separate features that happen to share a feed format. You can be eligible for ads (is_ads_eligible) without being eligible for Instant Checkout (is_eligible_checkout), and vice versa.

Is there a self-serve portal like Google Merchant Center? Not yet in the same open form. Ads Manager has a self-serve Feeds tool for generating SFTP credentials, but initial account approval and catalog onboarding are still coordinated with OpenAI directly or through its feed-partner ecosystem.

Which countries and ChatGPT plans currently see ads? As of now, ads only appear for logged-in adult users on the Free and ChatGPT Go tiers in the United States. Plus, Pro, Team, Business and Enterprise users see no ads.

Is there a minimum catalog size? For product-feed ad campaigns specifically, OpenAI's documentation requires a feed of at least 1,000 and no more than 2,000,000 products. No minimum has been documented for the organic shopping-results or Instant Checkout tracks.

Is any of this final? No — OpenAI has already revised Instant Checkout once (March 2026) and expanded Ads Manager access multiple times through 2026. Treat the mechanics on this page as the current state of a still-evolving program, not a fixed specification.