Guide
How to install the ChatGPT Ads pixel on WooCommerce
ChatGPT Ads measures WooCommerce sales through two OpenAI interfaces: the Measurement Pixel in the shopper's browser and the Conversions API on your server. Installing it means getting a Pixel ID and an API key from Ads Manager, then connecting them to WooCommerce so real product, cart and order events are sent. This guide does that with the Pixel for ChatGPT Ads plugin, and ends with how to check it works.
Updated
On this page
The short version: seven steps, about one settings screen of work
Before you start
Five things to have ready, and one thing to remove.
- WordPress with WooCommerce active, served over HTTPS.
- Admin access to WordPress, to upload and configure a plugin.
- Access to your ChatGPT Ads account in OpenAI Ads Manager.
- A Pixel for ChatGPT Ads licence key. You receive it at checkout; plans start at one site.
- A server that can make outbound HTTPS requests. Some hosts and firewalls block these; the server-side purchase needs them.
Check this
Step 1 of 7
Get your Pixel ID
The Pixel ID tells the Measurement Pixel which ChatGPT Ads account events belong to. OpenAI's documentation says to create a new Pixel ID in the conversions tab of Ads Manager
(Measurement Pixel documentation).
You need the Pixel ID for server-side tracking too: the Conversions API endpoint is addressed by it.
Expected
Common issue
Step 2 of 7
Get a Conversions API key
The Conversions API key authorises your server to send events. OpenAI provisions it in the same place: You can provision a Pixel ID and Conversions API key from the conversions tab in Ads Manager
(Conversions API documentation).
Treat the API key like a password
OpenAI is explicit that server events are sent from your server only
. The plugin stores the key for server-side use and does not print it into the page.
Expected
Common issue
Step 3 of 7
Install the plugin
- 1Download the plugin ZIP from your purchase confirmation, or from the download page with your licence key.
- 2In WordPress, go to
Plugins → Add New → Upload Plugin, choose the ZIP and install it. - 3Activate the plugin.
Expected
Step 4 of 7
Activate your licence
Open the plugin's Licence tab, paste your licence key and activate it. No events are sent until the licence is active.
Expected
Common issue
Step 5 of 7
Connect your credentials
On the plugin's Settings tab:
- Paste your Pixel ID into
OpenAI Pixel ID. - Paste your key into
Conversions API key. - Leave browser tracking on to send product views, add to cart, checkout starts and purchases from the page.
- Leave server-side tracking on to send each paid order through the Conversions API.
- If your consent banner implements the WordPress Consent API, turn on consent handling so the pixel waits for marketing consent.
The plugin's connection settings in WordPress.
- 1OpenAI Pixel ID — from step 1.
- 2Conversions API key — from step 2.
- 3Browser and server-side tracking switches — leave both on.
Expected
Check this
Step 6 of 7
Verify browser events
- 1Open the store in a private window and accept marketing cookies if a banner appears.
- 2Open your browser's developer tools and go to the Network tab.
- 3Filter requests by
openai. You should see the Measurement Pixel script load from an openai.com host. - 4View a product, add it to the cart and go to checkout, watching new requests appear.
Expected
Common issue
Step 7 of 7
Verify a paid order
Complete an order that reaches a paid status (a real low-value order, or a test gateway that marks orders as paid). Then open the plugin's Diagnostics tab and find the order.
| Delivery state | What it means | What to do |
|---|---|---|
| Accepted | OpenAI accepted the purchase. | Nothing. Tracking works. |
| Pending | Queued or waiting for another attempt. | Check back shortly. |
| Not sent | The purchase was not sent — usually no marketing consent for that order. | Open the order to see the reason. |
| Failed | The latest attempt did not complete. | Read the HTTP status, fix the cause, re-send if eligible. |
Diagnostics lists paid orders and what happened to each purchase event.
- 1Find your test order by its number.
- 2The event ID is the one shared by the browser and server purchase.
Expected
Check this
Troubleshooting
Common mistakes
Most installation problems are one of these five.
| Symptom | Likely cause | Fix |
|---|---|---|
| Conversions look doubled | The pixel is also installed in the theme or a tag manager. | Remove the other copy. |
| Failed with HTTP 401 | The Conversions API key was rejected. | Paste a valid key, then re-send from Diagnostics. |
| Stays Pending, retrying | The server cannot reach the API. | Check outbound HTTPS, firewall and proxy rules. |
| No browser events | Consent not granted, tracking off, or a stale cached page. | Grant consent, check settings, purge the cache. |
| Orders marked Not sent | No marketing consent recorded for those orders. | Expected behaviour with consent handling on. |
The troubleshooting section of the docs covers more cases.
Without a plugin
Installing it by hand instead
You can install the pixel without a plugin. On WooCommerce, the snippet is only the start.
OpenAI's instructions are to add its snippet to the <head> of every page where you want to capture conversions. After that:
- Each event — product view, add to cart, checkout, purchase — has to be coded with WooCommerce values.
- The purchase event should fire once per order, not once per order-received page load.
- A server-side purchase needs its own API client, triggered on the paid status.
- Browser and server purchases need the same event ID to be deduplicated.
- Failures need retries and somewhere to see them.
The OpenAI Conversions API guide for WooCommerce goes through the server-side half in detail.
Questions
Do I need both the Pixel ID and the API key?
The Pixel ID is needed for everything. The API key is needed for the server-side purchase. Browser tracking and server-side tracking can each be switched off, but running both gives the purchase a second path that does not depend on the browser.
Does the plugin need Google Tag Manager?
No. It loads the pixel and builds events from WooCommerce directly.
Will a theme change break tracking?
No template edits are involved, so switching themes does not remove the pixel. Heavily customised checkouts are worth re-testing with an order.
Does it work with HPOS?
Yes. WooCommerce High-Performance Order Storage and legacy order storage are both supported.
Ready to install it?
Pixel for ChatGPT Ads is an annual licence for 1, 5 or 25 sites, with the same functionality on every plan.
Related guides
- ChatGPT Pixel for WooCommerceWhat the plugin sends to ChatGPT Ads from a WooCommerce store, how it is set up, and what it does not do.
- OpenAI Conversions API for WooCommerceWhen and how a WooCommerce purchase is sent server-side, and what server-side tracking does not solve.
- ChatGPT Ads Pixel vs Conversions APIA side-by-side comparison of browser and server measurement for ChatGPT Ads, and why a store uses both.