Questions about ChatGPT Ads tracking on WooCommerce

It is a WooCommerce plugin that implements conversion tracking for ChatGPT Ads. It loads the OpenAI Measurement Pixel in the browser and sends purchase events server-side through the OpenAI Conversions API, using data from your WooCommerce orders.

No. Installation is a normal WordPress plugin upload and activation. Configuration is one settings screen where you enter your OpenAI Pixel ID, your Conversions API key and your licence key.

There are no theme edits, no checkout template changes and no tag manager container to maintain. A developer is only useful if your store has heavy checkout customisation or a caching layer that needs adjusting.

No. Pixel for ChatGPT Ads is an independent product and is not affiliated with or endorsed by OpenAI. It integrates with OpenAI's advertising measurement interfaces; it is not built, reviewed or certified by OpenAI.

Product viewed (contents_viewed), added to cart (items_added) and checkout started (checkout_started) are sent from the browser. Purchase (order_created) is sent from the browser and server-side through the Conversions API.

Yes, for purchases. When a WooCommerce order reaches a paid status, order_created is sent from your server to the OpenAI Conversions API.

Product views, add to cart and checkout start are browser events only. The site does not claim server-side coverage for events that are not sent server-side.

The browser event and the server event for the same order are sent with the same event ID. The ID is derived from the WooCommerce order rather than generated on each page load, so a reloaded order-received page does not produce a second identifier.

Matching the identifiers is the plugin's job; resolving the two deliveries into one conversion happens on OpenAI's side.

Yes. Browser-side measurement is implemented with the OpenAI Measurement Pixel, configured with the Pixel ID you enter in the plugin settings.

Yes. Purchase events are sent server-to-server through the Conversions API using the API key stored in the plugin settings. The key is used server-side only and is not exposed to the browser.

WooCommerce is the platform it is built for. Events are assembled from WooCommerce products, carts, checkout and orders, not from generic URL rules, so purchase values and order identifiers come from the order itself.

Yes. The plugin is compatible with WooCommerce High-Performance Order Storage and with legacy post-based order storage.

New conversion tracking stops. The plugin stays installed and your settings are kept, but no new events are sent, and plugin updates and support end. Renewing restores all three.

Yes. A licence has a fixed number of activations rather than a permanent tie to one domain. Deactivate the licence on the site you are leaving to free the activation, then activate it on the new site.

Yes. Growth covers up to 5 activations and Agency covers up to 25. Each client store uses one activation, and the setup steps are the same on every store.

Through the standard WordPress updates screen, like any other plugin, for as long as the licence is active.

It supports the WordPress Consent API. If your consent plugin implements that API, browser events can stay blocked until marketing consent is granted, and the consent state recorded for an order is used for the server-side purchase event.

Consent tools that do not implement the WordPress Consent API are not detected automatically. Your compliance obligations depend on your store, configuration and jurisdiction.

The plugin runs on your WordPress site and sends conversion events from your store directly to OpenAI. Your order and visitor data is not sent to us.

The licence system exchanges only your licence key and site address in order to activate, check and deactivate a licence. What OpenAI receives is determined by the events you enable and your consent configuration.