FeedAgentX – ChatGPT Ads Product Feed & Pixel for WooCommerce

Description

Everything a WooCommerce store needs for ChatGPT Ads: a free pixel that measures the sales your ads bring in, and a product feed OpenAI accepts.

New and free: the ChatGPT Ads Pixel

Turn on OpenAI’s Measurement Pixel and Conversions API in two minutes, without code. It works on its own: no FeedAgentX account is needed.

• The whole shopping journey. Page views, product views, add to cart, checkout and purchases, with prices and products. Works with classic and block themes, including the block checkout.
• Purchases from your server too. Paid orders are also sent through OpenAI’s Conversions API, in the background and retried if OpenAI cannot be reached, so ad blockers and closed tabs do not hide sales.
• Every sale counted once. The browser and your server share one event ID per order, so OpenAI never double counts.
• Better matching without raw data. Email, phone (with its country code) and name are normalized and hashed with SHA-256 on your server before anything is sent.
• Consent-aware. Follows cookie banners that support the WP Consent API, or waits for your own banner. Without consent, OpenAI’s script is not loaded and no purchase is sent.
• Test it from WordPress. Send a validate-only test purchase, and see every server delivery with its result.
• Lines up with your product feed. Products are reported with the same IDs as the FeedAgentX feed.

OpenAI uses these events to report conversions and return on ad spend, and to run campaigns that optimize for purchases.

The ChatGPT Ads product feed

FeedAgentX turns your WooCommerce catalog into a ChatGPT Ads product feed. It checks your products against OpenAI’s product feed format, gives you a hosted feed URL for OpenAI Ads Manager and, on paid plans, sends price and availability updates through the Ads API.

ChatGPT Ads can be built straight from a product catalog. Before one of your products can appear in a product ad, Ads Manager needs a feed in OpenAI’s format and a successful import. FeedAgentX Connect is the WordPress side of that setup: it links your store to FeedAgentX, where you review the catalog, fix problems and publish the feed.

Made for one channel: ChatGPT Ads

• OpenAI’s feed format, field by field. Titles, descriptions, prices, availability, images, brands, identifiers and variants are mapped to the columns Ads Manager expects.
• Catch problems before the import. Missing required fields, invalid GTINs, non-public product or image URLs and variant issues show up in FeedAgentX before OpenAI rejects a row.
• A hosted feed for OpenAI Ads Manager. One private URL with its own username and password, fetched on the schedule you set in Ads Manager. You can also download the CSV.
• Price and stock updates. After the first import, paid plans can send supported title, price and availability changes for existing items through the OpenAI Ads API.
• Variable products included. Each WooCommerce variation becomes its own feed row, as OpenAI’s format requires.
• Your store stays in charge. FeedAgentX reads your catalog with a revocable token. It does not edit products and never reads customer or order data.

How it works

The pixel:

1. In OpenAI Ads Manager, open the Conversions tab, create a pixel and a Conversions API key.
2. In WordPress, open FeedAgentX → ChatGPT Ads Pixel, paste both and save.
3. Send a test purchase from the same screen. That’s it: purchases are measured from then on.

The product feed:

1. Install this plugin and copy the API token from FeedAgentX → Product Feed.
2. Create a free FeedAgentX account, add your store URL and token, and wait for the first catalog sync.
3. Review validation issues and choose which products go to ChatGPT Ads.
4. Create the hosted feed and add it in OpenAI Ads Manager, then check the first import.
5. Optionally connect the Ads API for price and availability updates.

Plans

The ChatGPT Ads Pixel is free and needs no account. For the product feed, the Free plan covers 1 store and up to 25 products with a hosted feed, and needs no card. Paid plans raise the product limit, add stores on Growth and Pro, include Ads API updates and start with a 14-day free trial. See plans and limits.

What FeedAgentX does not do

FeedAgentX does not create campaigns, change bids, process orders or payments, or enable checkout inside ChatGPT. OpenAI controls account access, supported markets, catalog processing, product eligibility and ad approval. No placement, impressions or sales are guaranteed.

FeedAgentX is an independent service. It is not an official OpenAI or WooCommerce product.

Guides

• Documentation: installing the plugin, the ChatGPT Ads Pixel, the hosted feed, checking an import, API updates and what each error means.
• Set up the ChatGPT Ads Pixel
• ChatGPT Ads for WooCommerce stores: the complete guide
• ChatGPT product feed specification: every field explained
• OpenAI Ads Manager product feeds: setup and upload history

External services

This plugin can use two external services: FeedAgentX.com for the product feed, and OpenAI for the ChatGPT Ads Pixel. Each is off until you set it up.

1. FeedAgentX.com (product feed)

This part connects your WooCommerce store to FeedAgentX.com, a third-party SaaS platform operated by FeedAgentX. For the feed, the plugin does not make outbound calls; instead it exposes a token-protected catalog API that the FeedAgentX.com service pulls from after you connect your store. The token also permits sync acknowledgments; it cannot change settings in WordPress.

What data is shared with FeedAgentX.com:

• Product catalog data: titles, descriptions, prices, stock levels, SKUs, brands, categories, image URLs, product attributes, and variant data.
• Store details used in the feed: site name, home URL, site timezone, store currency, store and target countries, and the privacy policy, terms and return policy links with return acceptance and deadline.
• Catalog defaults and totals: search, checkout and Ads eligibility defaults, product and pending-change totals. Which products are advertised is decided in FeedAgentX.
• Plugin and platform metadata: plugin version, schema version, WordPress / WooCommerce / PHP versions, and when the API token was created (never the token itself).
• No customer records, order data or payment details are read or transmitted to FeedAgentX.com.

When data is shared:

• Only after a site administrator copies the API token from FeedAgentX → Product Feed and pastes it into a connected workspace at FeedAgentX.com.
• Every request must include a valid Bearer token. Rotating the token on the Product Feed page replaces it immediately; requests with the old token stop working.

Service provider:

• FeedAgentX.com — Privacy Policy: https://www.feedagentx.com/privacy/
• FeedAgentX.com — Terms of Service: https://www.feedagentx.com/terms/

2. OpenAI (ChatGPT Ads Pixel)

Nothing is sent to OpenAI until a site administrator turns on the pixel and enters a Pixel ID under FeedAgentX → ChatGPT Ads Pixel. Where consent is required (a WP Consent API banner, or the “Wait for consent” setting), nothing is loaded or sent for a visitor who has not given marketing consent. None of this data goes to FeedAgentX.

• In the visitor’s browser: the plugin loads OpenAI’s Measurement Pixel from https://bzrcdn.openai.com/sdk/oaiq.min.js, which sends events to OpenAI: the page address, product views, items added to the cart, checkout starts and purchases, with product IDs, names, quantities, prices, currency and order value. OpenAI’s script sets two first-party cookies, __oppref (ad click reference, up to 30 days) and __obref (browser reference, up to 365 days). On the order confirmation page, if customer matching is on, it also receives SHA-256 hashes of the billing email, phone, first and last name and customer ID, and the billing city, region, postcode and country.
• From your server (Conversions API): only if you also turn on server purchases and save a Conversions API key. For each paid order placed through the storefront checkout, the plugin sends https://bzr.openai.com/v1/events the order’s event ID, payment time, checkout page URL, order value, currency and products, the customer’s IP address and browser user agent, the __oppref and __obref values stored at checkout, and, if customer matching is on, SHA-256 hashes of the billing email, phone, first and last name and customer ID with the billing city, region, postcode and country. Email, phone and name are never sent in plain text. Payment details are never read or sent.

• Test purchase: the admin “Send a test purchase” button sends one sample event with validate_only, which OpenAI checks without recording; it contains no customer data.

• OpenAI — Privacy Policy: https://openai.com/policies/privacy-policy/

• OpenAI — Terms of Use: https://openai.com/policies/terms-of-use/

Suggested wording for your own privacy policy is added to Settings → Privacy → Policy Guide.

Security and logs

• All endpoints require a Bearer token, compared in constant time and rotatable from the admin screen.
• Authenticated requests have a per-token rate limit (default 120/min); failed-auth requests have a per-IP limit (default 10/min) against brute force and log spam.
• The Conversions API key is stored in the WordPress database, shown only as its last four characters, and never logged. It can only send events to OpenAI.
• Server purchase history on the pixel screen keeps order numbers and outcomes only, no customer details.
• Diagnostic logs are written to wp-content/uploads/feedagentx-logs/ at INFO level and deleted after 14 days by default. They contain route names, error messages and migration events, plus the IP address of requests refused for a missing or invalid token or for exceeding the rate limit. Tokens are never logged.

• The log directory is protected by generated .htaccess (Apache) and web.config (IIS) files. On Nginx, add this inside your server block:

  location ~* /wp-content/uploads/feedagentx-logs/ {
  deny all;
  return 404;
  }