Your product feed,ready for ChatGPT Ads

ChatGPT Ads does not accept XML. The OpenAI specification wants a tabular file, TSV, CSV or JSONL, with different column names and a few fields that simply do not exist in Google Merchant or Meta feeds. This converter does exactly that translation, without you having to rebuild the feed in your shop. The spec is public, you will find it in the OpenAI product feed documentation.

Your Google Merchant Center feed in XML, either RSS 2.0 or Atom. And your Meta Commerce Manager catalogue feed in CSV or XML. The only condition is that the URL is public, meaning it opens without a password.

The feed Google Ads uses for Shopping lives in Google Merchant Center, not in Google Ads. Go to merchants.google.com, pick the account, then open Products → Feeds from the left menu (the newer interface calls it Data sources). Open your primary feed and look at how it is fed: if it says 'Scheduled fetch', the file URL is right there in the source settings, and that is the one to paste here. If the feed was uploaded by hand or comes through the Content API, there is no URL to copy. In that case take the feed straight from your shop platform: almost every Google Shopping module for WooCommerce, PrestaShop, Magento or Shopify publishes a feed link in its settings.

In Meta Commerce Manager, not in Ads Manager. Go to business.facebook.com/commerce, pick the catalogue your ads use, then open Catalog → Data sources from the left menu. Select the catalogue source: if it is a scheduled feed or data feed, the file URL is in its settings, usually next to the refresh schedule. If the products were uploaded by hand or come from the pixel, there is no URL. Here too the answer is your shop feed: Facebook catalogue modules for WooCommerce, PrestaShop or Shopify give you a public link, in CSV or XML, which is exactly what we need.

No, the tool is free. Convert as many feeds as you like, with no account, no email and no card. There is no paid version of this page and no surprise at the end.

We do not store the information in your product feed. The feed is read in memory, converted and forgotten, without ever reaching a database of ours. The resulting file lives for 24 hours at a secret URL, so you have time to download it, and is then deleted automatically. Our log keeps the shop domain, the conversion figures and the IP address the request came from, which we keep only so we can stop abuse. That is all.

Under a minute for ordinary feeds: a 3,300-product catalogue converts in a few seconds. The limit is 64 MB per feed.

It maps the columns to the names OpenAI expects, adds the required fields missing from Google and Meta feeds, the seller name among them, validates GTIN codes against the GS1 check digit, trims titles to 150 and descriptions to 5,000 characters, and drops products without the minimum fields. At the end you get a report of everything that changed. The rules are the ones in the OpenAI specification.

Because products missing required fields are rejected by the OpenAI specification. Most often it is the description, the image or the price. The report after the conversion tells you how many and why, so you can fix them in your shop.

Not here: this page does one full conversion on demand. A feed kept up to date in real time, on every price or stock change, and feeds built on product segments need a custom implementation by a DWF specialist, on your own shop. That is how you can run ChatGPT campaigns only on products with at least a 25% commercial margin, for instance, or only on products from one category that are in stock and priced above 200 RON. Write to us and we will set it up.