WooCommerce plugin

ChatGPT Pixel for WooCommerce

Pixel for ChatGPT Ads adds ChatGPT Ads conversion tracking to a WooCommerce store without a custom integration. It loads the OpenAI Measurement Pixel on your storefront, reports product views, add to cart, checkout starts and purchases from your real WooCommerce data, and also sends every paid order from your server through the OpenAI Conversions API.

See pricing Read the installation guide

From €79/year. Installs like any WordPress plugin.

In the browser

→ OpenAI Measurement Pixel

Product viewed
Added to cart
Checkout started
Purchase

same event ID

From your store

→ OpenAI Conversions API

WooCommerce marks the order paid
Purchase

Built specifically for WooCommerce
Browser + server purchase measurement
No Google Tag Manager required
WooCommerce HPOS support
Order-level delivery diagnostics

Measurement

What the plugin sends to ChatGPT Ads

Four moments of the WooCommerce buying journey, reported with the OpenAI event names ChatGPT Ads expects. The values come from the product, cart and order themselves, not from URL rules or a data layer you maintain.

01
Product viewed
A product page opens
contents_viewed
Browser
02
Added to cart
A product goes into the cart
items_added
Browser
03
Checkout started
The customer reaches checkout
checkout_started
Browser
04
Purchase
WooCommerce marks the order paid
order_created
Browser+ Server-side

Only the purchase has a server-side path. Product views, carts and checkout starts are browser events, so they depend on the visitor's browser loading the pixel. The comparison of the Pixel and the Conversions API explains why the purchase is the event worth sending twice.

Reliability

One purchase, two delivery paths, one conversion

The browser purchase and the server purchase for the same order carry the same event ID, so OpenAI can count them as one.

The plugin derives the event ID from the WooCommerce order rather than generating it on page load, so a reloaded order-received page does not create a second identifier.

OpenAI documents that for deduplication it uses your Pixel ID, event_name, and id and keeps the first event it receives for a matching key (OpenAI Conversions API documentation). Matching the IDs is the plugin's job; resolving the two deliveries into one conversion happens on OpenAI's side.

The server event is sent when WooCommerce moves the order to a paid status, not when a thank-you page loads. A customer who closes the tab straight after paying, or who pays by a delayed method, still produces a purchase event from your store.

Browser · Pixel

Purchase

Shared event ID derived from the WooCommerce order

Server · Conversions API

Purchase

Shared event ID derived from the WooCommerce order

One conversion

Same Pixel ID, event name and ID: OpenAI keeps the first and ignores the duplicate.

See what happens when an order is paid

Five steps from checkout to a counted conversion. Select a step to read what happens and where.

Step 1 · Customer

Customer pays

The customer completes checkout and WooCommerce creates the order. Nothing has been sent to ChatGPT Ads yet.

Step 2 · Browser

Browser sends the purchase

If the order-received page loads and the pixel is allowed to run, the browser sends order_created through the Measurement Pixel, with an event ID derived from the order.

Step 3 · WooCommerce

WooCommerce confirms payment

The server purchase is sent when WooCommerce marks the order as paid. The plugin records a delivery for that order at that point.

Step 4 · Server

Server sends the purchase

The plugin sends order_created from your server through the Conversions API, with the same event ID and the original purchase time. Temporary failures are retried, and the outcome appears in Diagnostics.

Step 5 · OpenAI

OpenAI matches the event ID

OpenAI deduplicates on Pixel ID, event name and event ID: it keeps the first purchase it receives and ignores the duplicate. If the browser event never arrived, the server event still counts.

Operations

When delivery fails, you can see it

Every paid order gets a delivery record in WordPress, so a broken integration never looks like a quiet week of sales.

Temporary failures — timeouts, rate limits, server errors — are retried automatically. Anything that still fails stays visible with its attempt count and HTTP status, and an eligible order can be re-sent manually once the cause is fixed.

Accepted: OpenAI accepted the purchase.
Pending: Queued or waiting for another delivery attempt.
Not sent: The purchase was not sent. Open the order to see why.
Failed: The latest delivery attempt did not complete.

Not sent usually means no marketing consent for that order. The troubleshooting table in the docs maps common HTTP statuses to their fix.

Pixel for ChatGPT Ads diagnostics screen in WordPress listing recent WooCommerce orders, the event ID sent for each, and whether WooCommerce recorded the order as paid — The diagnostics screen in WordPress. Orders shown are examples.
1Each tracked order is listed with the event ID that was sent for it.
2WC paid shows whether WooCommerce has recorded the order as paid — the trigger for the server-side purchase.

Setup

Setup takes one settings screen

No theme edits, no Google Tag Manager container and no checkout template changes.

Install
Upload the plugin ZIP in WordPress and activate it.
License
Activate your licence key on the Licence tab.
Connect
Paste your OpenAI Pixel ID and Conversions API key on the Settings tab. Both come from the conversions tab in OpenAI Ads Manager.
Check
Place or wait for a paid order, then check its delivery state in Diagnostics.

The step-by-step installation guide covers each field and how to verify the first events.

Pixel for ChatGPT Ads settings screen with fields for the OpenAI Pixel ID and Conversions API key, above the browser and server-side tracking switches — The connection settings. The API key is stored for server-side use and never printed into the page.

Control

Requirements

WordPress with WooCommerce active. The plugin is WooCommerce-only.
WooCommerce High-Performance Order Storage (HPOS) or legacy post-based order storage — both are supported.
The store served over HTTPS, with outbound HTTPS requests allowed.
A ChatGPT Ads account with a Pixel ID and a Conversions API key.
An active Pixel for ChatGPT Ads licence, which also delivers updates through WordPress.

What it does not do

Clear limits, so you know exactly what you are buying.

It does not send product views, carts or checkout starts server-side. Only the purchase has a server path.
It does not track forms, sign-ups, leads or other non-WooCommerce conversions, and does not work on WordPress sites without WooCommerce.
It does not guarantee attribution or recover every conversion. It sends accurate events; whether ChatGPT Ads attributes a sale to an ad is decided by OpenAI.
It does not create campaigns, product feeds or audiences.
It is not an OpenAI product. Pixel for ChatGPT Ads is an independent product and is not affiliated with or endorsed by OpenAI.

Alternatives

Other ways to add ChatGPT Ads tracking to WooCommerce

You can build this yourself. The question is how much you want to build and then maintain.

Build it yourself

1Theme or tag code for the pixel
2JavaScript for each WooCommerce event
3PHP hook that sends the paid order
4Event IDs shared by both paths
5Retry queue for failed requests
6Admin screen to see failures
7Maintenance as APIs and themes change

Pixel for ChatGPT Ads

1Install the plugin
2Paste Pixel ID and API key
3Check the next paid order

Events, the server-side purchase, shared IDs, retries and diagnostics are already built. Updates arrive through WordPress.

Whichever route you choose, check the same four things: which events are sent, whether the purchase has a server-side path, whether the two paths share event IDs, and whether you can see a failed delivery.

Approaches to ChatGPT Ads tracking on WooCommerce compared
	Pixel snippet only	Custom build	Pixel for ChatGPT Ads
Browser events	Only the events you code yourself	You write them	Four WooCommerce events
Server-side purchase	No	You build the API client	Yes, on paid status
Shared event IDs	No	You design them	Derived from the order
Retries	No	You build a queue	Automatic for temporary failures
Per-order visibility	No	You build admin tooling	Diagnostics tab
Ongoing upkeep	Theme changes	Yours	Plugin updates

Free and multi-platform plugins exist too. If you compare them, ask the four questions above; the Conversions API guide explains what a sound server-side implementation has to handle.

Pricing

Every plan has the same functionality. Plans differ only by how many sites the licence can be activated on.

Starter
1 site
€79 per year
Growth
Up to 5 sites
€199 per year
Agency
Up to 25 sites
€399 per year

Licences are annual and include plugin updates through the normal WordPress updates screen and email support. Compare plans and buy.

FAQ

Questions about the ChatGPT pixel on WooCommerce

More answers in the full FAQ and the plugin documentation.

Is this the official ChatGPT pixel?

It loads OpenAI's official Measurement Pixel, configured with your own Pixel ID. The plugin itself is independent and is not made or endorsed by OpenAI.

Do I still need to paste the pixel snippet into my theme?

No, and you should not. The plugin loads the pixel. A second copy in the theme or a tag manager fires without the plugin's event IDs and can double-count purchases.

Which purchase value is sent?

The value and currency of the WooCommerce order, with the original purchase time.

Which event names are used?

contents_viewed, items_added, checkout_started and order_created — OpenAI's standard event names.

Can I use it on client stores?

Yes. Growth covers up to 5 sites and Agency up to 25; each WordPress install uses one activation.

Add ChatGPT Ads tracking to your WooCommerce store

Install the plugin, paste two OpenAI credentials, and read the delivery state of your next paid order. Same functionality on every plan.