Skip to content

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

Remove other copies of the pixel. If the ChatGPT Ads pixel is already pasted into the theme header, a header-scripts plugin or a Google Tag Manager container, remove it before going live. A second copy fires its own events without the plugin's event IDs, so OpenAI cannot recognise them as the same purchase and your conversions can be counted twice.
1

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

A Pixel ID for your ChatGPT Ads account, copied somewhere you can paste it from.

Common issue

Using a different Pixel ID on the browser and the server. Both paths must use the same one, or browser and server events cannot be matched.
2

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

A Conversions API key, stored only where you keep passwords.

Common issue

Pasting the key into a theme file, page builder or tag manager. The key must never appear in page source.
3

Step 3 of 7

Install the plugin

  1. 1Download the plugin ZIP from your purchase confirmation, or from the download page with your licence key.
  2. 2In WordPress, go to Plugins → Add New → Upload Plugin, choose the ZIP and install it.
  3. 3Activate the plugin.

Expected

Pixel for ChatGPT Ads appears in your Plugins list as active.
4

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

The Licence tab shows the licence as active, with your plan and remaining activations.

Common issue

Activating on a staging copy first. Staging uses its own activation, so only test there if your plan has one to spare.
5

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.

  1. 1OpenAI Pixel ID — from step 1.
  2. 2Conversions API key — from step 2.
  3. 3Browser and server-side tracking switches — leave both on.

Expected

Both credentials saved, browser and server-side tracking on.

Check this

If your store uses a full-page cache, purge it after saving so visitors are not served a copy of the page from before the pixel was configured.
6

Step 6 of 7

Verify browser events

  1. 1Open the store in a private window and accept marketing cookies if a banner appears.
  2. 2Open your browser's developer tools and go to the Network tab.
  3. 3Filter requests by openai. You should see the Measurement Pixel script load from an openai.com host.
  4. 4View a product, add it to the cart and go to checkout, watching new requests appear.

Expected

Requests to an openai.com host as you view a product, add it to the cart and reach checkout.

Common issue

No requests at all — usually browser tracking is off, the Pixel ID is missing, consent has not been granted, or a cached page is being served.
7

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.

What the delivery state of an order means
Delivery stateWhat it meansWhat to do
AcceptedOpenAI accepted the purchase.Nothing. Tracking works.
PendingQueued or waiting for another attempt.Check back shortly.
Not sentThe purchase was not sent — usually no marketing consent for that order.Open the order to see the reason.
FailedThe 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.

  1. 1Find your test order by its number.
  2. 2The event ID is the one shared by the browser and server purchase.

Expected

The order shows Accepted in Diagnostics.

Check this

An order still awaiting payment has not been sent yet — the purchase is sent when WooCommerce marks it paid.

Troubleshooting

Common mistakes

Most installation problems are one of these five.

Common ChatGPT Ads pixel installation mistakes on WooCommerce
SymptomLikely causeFix
Conversions look doubledThe pixel is also installed in the theme or a tag manager.Remove the other copy.
Failed with HTTP 401The Conversions API key was rejected.Paste a valid key, then re-send from Diagnostics.
Stays Pending, retryingThe server cannot reach the API.Check outbound HTTPS, firewall and proxy rules.
No browser eventsConsent not granted, tracking off, or a stale cached page.Grant consent, check settings, purge the cache.
Orders marked Not sentNo 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.