Services ChatGPT ads for the UAE

ChatGPT ads product feed campaigns for UAE ecommerce

gptads.ae / updated 17 October 2026

Feed based ChatGPT ads for UAE and Saudi online stores. Feed build, automated refresh, product grouping by margin, templates and purchase tracking.

On this page
  1. Who this is for
  2. Why start here if you sell online
  3. Choosing how the feed is hosted
  4. What is included
  5. Deliverables
  6. How we work with your existing Google and Meta agency
  7. What you will see in the first report
  8. The first thirty days, week by week
  9. What we need from you
  10. What you own
  11. What we do not do
  12. Where to go deeper
  13. Quick answers

Who this is for

UAE and Saudi online stores on Shopify, Salla, Zid or a custom built platform that want their catalogue advertised on ChatGPT with image, price and stars shown per product, rather than building single ads by hand. It suits a store with an existing product feed used for Google or Meta that needs adapting, and a store with no feed at all that needs one built from scratch. It is not the right starting point if conversion tracking is not yet in place, since purchase events are what makes a feed campaign worth running. It also suits a store whose feed already works for Google Shopping or Meta but has never been checked against OpenAI's own specification and expiry rules, which are stricter about refresh cadence than either of those platforms.

Why start here if you sell online

OpenAI says ads created from product feeds have been among the strongest performing in its programme. Feed ads show image, title, stars, price, sale price and brand together, which is closer to what a shopper comparing options actually wants than a single static ad.

Choosing how the feed is hosted

Method Best suited to What it needs
Upload CSV or TXT Getting started, or occasional manual updates Someone to re-upload before the two week item expiry each time
Hosted URL A catalogue that already has a stable HTTPS export A stable URL your store or platform already generates
SFTP connection A technical team that can automate server to server uploads Engineering time to set up the automated transfer once

We default to a hosted URL or SFTP connection for any store with more than a handful of products, since OpenAI's items expire after two weeks and a manual re-upload cycle is the most common way a live feed quietly goes stale.

What is included

  • Your feed built or adapted to OpenAI's specification from Shopify, Salla, Zid or a custom store's product data.
  • Hosting on a URL or SFTP connection that refreshes on a schedule, so items never sit long enough to hit the two week expiry OpenAI applies to feed listings.
  • ads_metadata values added, such as margin tier and product line, so ad groups and budgets can follow profit rather than just category.
  • Campaign, ad groups, filters and template built, with product counts checked at each stage rather than assumed.
  • Purchase events wired through the Pixel and the Conversions API with matching event IDs, so the same sale is not counted twice.
  • Confirmation that OAI-SearchBot can reach both the feed and the product image URLs, since a blocked image host can silently stop feed processing.
  • Reporting by product and by margin tier once delivery data starts to appear in the Products tab.

Deliverables

Deliverable Format Typically ready
Feed built to specification Hosted URL or SFTP connection, refreshing automatically Week two
ads_metadata structure Margin tier and product line values added for ad group filtering Week two
Crawler access confirmation OAI-AdsBot and OAI-SearchBot confirmed against the feed and image host Week two
Campaign, ad groups and template Built, filtered and launched Week three
Purchase tracking Pixel and Conversions API wired through, tested on one real transaction Week three
Product and tier reporting First read once the Products tab starts populating Week four

How we work with your existing Google and Meta agency

A product feed for ChatGPT ads is a separate build from a Google Shopping or Meta catalogue feed, even when it starts from the same underlying product data, since OpenAI's specification, filters and ads_metadata structure are its own. We do not need to touch your Google or Meta feed to build this one, and we are glad to work from an export of your existing feed as a starting point rather than asking your team to prepare product data twice. Purchase tracking is the one area worth aligning across platforms: if a Google or Meta agency already has purchase events firing through a shared checkout, we extend that same event to also reach OpenAI's Conversions API rather than building a duplicate, disconnected pipeline.

What you will see in the first report

Before the feed campaign has meaningful delivery, the first report is a feed status note: whether the feed validated successfully, how many products are eligible and passing your filters, whether OAI-AdsBot and OAI-SearchBot can reach both the feed and the image host, and whether the first test purchase came through the Pixel and Conversions API correctly matched by event ID. The Products tab itself is a reporting view that only populates after real delivery, so early reports describe readiness rather than results. Once delivery starts, later reports move to product and margin tier performance, described against your own categories rather than raw platform totals alone.

The first thirty days, week by week

  1. Week one. Existing feed reviewed or a new one built against OpenAI's specification, hosting method chosen, and margin tiers agreed with you.
  2. Week two. Feed hosted with an automated refresh, ads_metadata added, and crawler access to the feed URL and image host confirmed for OAI-AdsBot and OAI-SearchBot.
  3. Week three. Campaign, ad groups, filters and template built and launched, with purchase tracking tested through one real transaction end to end.
  4. Week four. First delivery data reviewed by product and by tier once the Products tab starts populating, and underperforming segments identified for the next round of filters or budget changes.

What we need from you

Access to your store's product data or existing feed, a decision on how margin tiers should be defined, and someone on your engineering or hosting side who can allowlist OpenAI's crawlers if the current setup blocks them. Purchase tracking needs to already be live, or ready to build alongside the feed, since a feed campaign without it cannot report the number that actually matters. For Salla and Zid stores specifically, we also need admin access to the store dashboard to confirm which product fields map cleanly onto OpenAI's required feed columns.

What you own

The feed, its hosting, the ads_metadata structure and every campaign built from it sit inside your Ads Manager account and your own hosting or store platform. We do not hold the feed file or its schedule outside systems you control.

What we do not do

We do not launch a feed campaign without purchase tracking in place, since Order Created Sales and Order Created ROAS are only calculated from attributed order_created events, and nothing else feeds those two columns. We do not sell SEO services.

Where to go deeper

The full feed build method, including the specification and expiry rule, is in the product feed guide. Purchase event tracking through the Pixel and Conversions API is covered in the conversion tracking guide, and what to check if OpenAI's crawlers cannot reach your feed or image host is in the crawlers guide.

Quick answers

How is the fee set?

Pricing is on request. Your exact fee comes after a short call where we look at your accounts and tracking. We work with a minimum ad budget of AED 5,000 a month (SAR 5,000 in Saudi Arabia), paid by you directly to OpenAI and separate from our fee.

Who owns the account and data?

You do. The Ads Manager account, pixel, feeds and data sit under your company. We work as invited users.

Our catalogue changes daily. Is that a problem?

No, it is the reason to use a hosted feed URL or SFTP. Items expire after two weeks, so an automated refresh is required anyway, not an optional extra.

Do you work with Shopify, Salla and Zid?

Yes, and with a custom built store as well, as long as we can build or adapt a feed to OpenAI's specification from your product data.

Why does the Products tab in Ads Manager look empty right after launch?

It is a reporting view, not an inventory list. OpenAI says products only appear there once an active campaign has delivered and generated reporting data, and asks you to allow up to seven hours after delivery begins for product rows to appear for the first time.

Will OAI-SearchBot need access to our image host separately from the main site?

Yes. OpenAI recommends allowing OAI-SearchBot to crawl your product image URLs specifically, and a firewall or CDN blocking those images can stop feed processing even if the main site is fully accessible.

We already run Google Shopping or Meta catalogue ads. Can you reuse that feed?

Often as a starting point, yes, though it needs checking against OpenAI's own specification and its two week item expiry rule, which is stricter about refresh cadence than either of those platforms.

Does this replace our Google or Meta product feed agency?

No. It builds and manages the ChatGPT ads feed specifically, on its own hosting or SFTP connection. Your existing Google Shopping or Meta catalogue setup continues exactly as it is.

How many products can be in the feed?

OpenAI has not published a maximum catalogue size. What matters more in practice is that filters and ads_metadata values are structured well enough to group products into sensible ad groups rather than one undifferentiated catalogue.

What happens if a product goes out of stock?

Update its availability in the feed, and the next refresh reflects that. Since items expire after two weeks without a refresh regardless, we build on a hosted URL or SFTP connection rather than a manual upload, so stock and price stay current automatically.