Title: Openpixly – Conversion Tracking & Product Feed for OpenAI Ads
Author: Özgür KARALAR
Published: September 10, 2026
Last modified: October 2, 2026
---
Search plugins
# Openpixly – Conversion Tracking & Product Feed for OpenAI Ads
By [Özgür KARALAR](https://profiles.wordpress.org/zgrkaralar/)
[Download](https://downloads.wordpress.org/plugin/openpixly.1.5.1.zip)
* [Details](https://vec.wordpress.org/plugins/openpixly/#description)
* [Reviews](https://vec.wordpress.org/plugins/openpixly/#reviews)
* [Installation](https://vec.wordpress.org/plugins/openpixly/#installation)
* [Development](https://vec.wordpress.org/plugins/openpixly/#developers)
[Support](https://wordpress.org/support/plugin/openpixly/)
## Description
Openpixly installs the official ChatGPT Ads Measurement Pixel on every
page and
sends the standard conversion events for you:
* `page_viewed` on every page.
* `contents_viewed` on WooCommerce product pages.
* `items_added` on add to cart (classic, AJAX and block/Store API carts).
* `checkout_started` on the checkout page.
* `order_created` on the order-received page, and again from the server
through
the Conversions API with the same event ID so OpenAI deduplicates it.
* `registration_completed` when a user or customer registers.
Amounts are sent as integers in the currency’s ISO 4217 minor unit, customer
identifiers
are normalized and SHA-256 hashed on the server before they reach the browser, and
a `` image tag covers visitors without JavaScript.
#### Meta (Facebook & Instagram) pixel
Enable the Meta provider and enter your Pixel ID to send the same events to
Meta:`
PageView`, `ViewContent`, `AddToCart`, `InitiateCheckout`, `Purchase` and `CompleteRegistration`,
with `content_ids` / `contents` that match the Meta catalog feed. Advanced matching
data is normalized and SHA-256 hashed on the server. With a Conversions API access
token, `Purchase` is also sent from the server with the same event ID, the `_fbp`/`
_fbc` cookies captured at checkout, and the customer’s IP address and user agent,
so Meta deduplicates browser and server events. Each provider has its own “Track
WooCommerce events” switch.
#### Google Ads & GA4
Enable the Google provider with a GA4 Measurement ID and/or a Google Ads
Conversion
ID. GA4 receives `page_view`, `view_item`, `add_to_cart`, begin_checkout, `purchase`(
with `transaction_id` and `items[]`), sign_up and `generate_lead`; Google Ads receives
a `conversion` for every event you give a conversion label. Enhanced conversions
data is hashed on the server. “Require consent first” uses Consent Mode v2 with
all four types denied until your banner grants them.
#### Lead forms
Contact Form 7, WPForms and Gravity Forms submissions become
lead_created / `Lead`/`
generate_lead` events on every enabled provider: fired in the browser straight from
the form’s AJAX response and sent from the server through the Conversions APIs with
the same event ID. Email, phone and name are read from the submitted fields (adjust
with the openpixel_lead_user filter).
#### Consent
Choose “Require consent first” to initialize the pixel with consent set to
false.
Grant consent from your cookie banner with `window.openPixel.grantConsent()`; the
WP Consent API “marketing” category is detected automatically, on the server (no
consent = false is printed once the category is allowed) and in the browser.
#### Conversions API
Orders, registrations and leads are sent from the server. Enable it and paste the
API key from the Conversions tab of Ads Manager (for
Meta: the access token from
Events Manager). Orders are delivered asynchronously with retries and logged under
WooCommerce > Status > Logs (source: openpixly). The OpenAI “Send test event” button
validates your credentials without recording anything; the Meta one sends the event
with your test event code so it only shows under Events Manager > Test events.
#### Product feed for ChatGPT Ads
The Product feed tab builds a catalog file from your WooCommerce products in
the
OpenAI product feed format (or the Google-compatible profile) as CSV, TSV or JSONL:
one row per simple product or variation, with group_id and variant_dict for variants,
prices as “79.99 USD”, availability, images, brand, category, GTIN/MPN and is_ads_eligible.
The file is rebuilt on a schedule and served at a private tokenized URL you can
hand to OpenAI, or downloaded for upload to the SFTP location shown in Ads Manager
> Feeds.
#### Meta catalog feed
Switch on “Also build a Meta catalog feed” and the same build writes a second
CSV
in Meta’s catalog format (id, title, description, availability, condition, price,
link, image_link, brand, sale_price, item_group_id, …), served at its own private
URL. Paste it in Commerce Manager > Catalog > Data sources > Data feed > Scheduled
feed. Item ids equal the pixel’s content_ids, which is what Advantage+ catalog ads
need.
#### Debugging
The Events tab records, for 24 hours after you enable it, every event the
plugin
tracks: the page or request that raised it, the exact payload each pixel received
and whether the Conversions API accepted it. Customer data is reduced to the names
of the fields present.
#### Extensible
The plugin is a small pixel manager: integrations emit normalized events on
a bus
and each provider maps them to its own API. Additional providers (Google Ads, TikTok,…)
can be registered with the openpixel_pixel_providers filter.
### External services
This plugin is an integration with OpenAI’s ChatGPT Ads measurement services and,
optionally, Meta’s (Facebook & Instagram) and Google’s (Google Ads, Google Analytics
4) measurement services. Openpixly is developed by Unbelievable Digital and is not
affiliated with or endorsed by OpenAI, Meta or Google. Nothing is loaded or sent
to a service until a site administrator enables that provider and enters its Pixel
ID.
**OpenAI Measurement Pixel (browser SDK)** — https://bzrcdn.openai.com/sdk/oaiq.
min.js and https://bzrcdn.openai.com/pixel-config/ — loaded on every front-end page
while the provider is enabled, to measure ad conversions. The SDK sends measurement
events to https://bzr.openai.com: page views (page id and title), product views,
add-to-cart, checkout and purchase events (WooCommerce product ids, names, quantities
and amounts), and registrations. The SDK reads and sets first-party cookies (`__oppref`,`
__obref`) for click attribution and may collect the visitor’s IP address and user
agent as part of the request. When “Send hashed customer data” is on, the plugin
also passes SHA-256 hashes of the logged-in user’s or the order’s billing email,
phone, first and last name, and the plain-text billing country, city, region and
postal code, to improve conversion matching. Raw email, phone or names are never
sent.
**OpenAI image tag (no-JavaScript fallback)** — https://bzr.openai.com/v1/sdk/events—
when enabled, a 1×1 image records a page view for visitors without JavaScript. It
carries only the Pixel ID and event name.
**OpenAI Conversions API (server-to-server)** — https://bzr.openai.com/v1/events—
only when enabled with your Conversions API key. When a user registers, the plugin
sends the hashed email and name, the user id (hashed), IP address, user agent and
attribution cookie values. When an order is paid, the plugin sends the order id,
total, currency and line items (product ids, names, quantities, amounts, variant
attributes), the SHA-256 hashed billing email, phone, first and last name, the billing
country, city, region and postal code, the customer’s IP address and user agent,
and the attribution cookie values captured at checkout. The admin “Send test event”
button sends a synthetic event with `validate_only` set, which OpenAI validates
but does not store.
**Google tag (Google Ads and Google Analytics 4)** — https://www.googletagmanager.
com/gtag/js — loaded on every front-end page while the Google provider is enabled,
to measure ad conversions and site analytics. The tag sends data to Google (www.
google-analytics.com, www.googleadservices.com, googleads.g.doubleclick.net, www.
google.com): page views, product views, add-to-cart, checkout, purchase, registration
and lead events (WooCommerce product ids, names, quantities and amounts, order ids),
and sets first-party cookies (`_ga`, `_gcl_*`). When “Send hashed customer data”
is on, the plugin also passes SHA-256 hashes of the logged-in user’s or the order’s
billing email, phone, first and last name, and the plain-text city, region, postal
code and country (enhanced conversions). Raw email, phone or names are never sent.
There is no server-to-server call to Google.
Service provider: Google LLC / Google Ireland Ltd. Terms: https://marketingplatform.
google.com/about/analytics/terms/us/ and https://ads.google.com/intl/en/home/terms/—
Privacy policy: https://policies.google.com/privacy — Developer documentation: https://
developers.google.com/tag-platform
The product feed feature does not contact OpenAI or Meta by itself; it generates
files on your server that you choose to give to them.
Service provider: OpenAI, L.L.C. Terms of use: https://openai.com/policies/terms-
of-use/ — Privacy policy: https://openai.com/policies/privacy-policy/ — ChatGPT
Ads developer documentation: https://developers.openai.com/ads
**Meta Pixel (browser SDK)** — https://connect.facebook.net/en_US/fbevents.js —
loaded on every front-end page while the Meta provider is enabled, to measure ad
conversions. The SDK sends events to https://www.facebook.com/tr: page views, product
views, add-to-cart, checkout and purchase events (WooCommerce product ids, names,
quantities and amounts), and registrations. The SDK reads and sets first-party cookies(`
_fbp`, `_fbc`) and may collect the visitor’s IP address and user agent as part of
the request. When “Send hashed customer data” is on, the plugin also passes SHA-
256 hashes of the logged-in user’s or the order’s billing email, phone, first and
last name, city, region, postal code, country and customer id (Meta advanced matching).
Raw values are never sent.
**Meta image tag (no-JavaScript fallback)** — https://www.facebook.com/tr — when
enabled, a 1×1 image records a PageView for visitors without JavaScript. It carries
only the Pixel ID and event name.
**Meta Conversions API (server-to-server)** — https://graph.facebook.com/ — only
when enabled with your access token. When a user registers, the plugin sends the
hashed email, name and user id, IP address, user agent and `_fbp` / `_fbc` values.
When an order is paid, the plugin sends the order id, total, currency and line items(
product ids, quantities, unit prices), the SHA-256 hashed billing email, phone,
first and last name, city, region, postal code, country and customer id, the customer’s
IP address and user agent, and the `_fbp` / `_fbc` cookie values captured at checkout.
The admin “Send test event” button sends a synthetic event carrying your test event
code, which Meta shows under Test events and does not count as a conversion.
Service provider: Meta Platforms, Inc. / Meta Platforms Ireland Ltd. Meta Business
Tools terms: https://www.facebook.com/legal/terms/businesstools — Privacy policy:
https://www.facebook.com/privacy/policy/ — Developer documentation: https://developers.
facebook.com/docs/meta-pixel
**Lead forms.** When Contact Form 7, WPForms or Gravity Forms is active, a form
submission is reported to the enabled providers as a lead event, with the SHA-256
hashed email, phone and name read from the submitted fields, over the same browser
and server channels described above.
**Consent.** Measurement is opt-in for the site owner (disabled until configured)
and administrators are excluded by default. To make it opt-in for visitors, choose“
Require consent first” on each provider: the pixel then starts with consent revoked(`
oaiq("consent", false)` / `fbq("consent", "revoke")`) and only measures after your
cookie banner calls `window.openPixel.grantConsent()` or the WP Consent API reports
the “marketing” category as allowed. Server-side Conversions API events are sent
for paid orders whenever that option is enabled; leave it off if your legal basis
requires browser consent for them too. Disclose the pixels you use in your site’s
privacy policy.
## Screenshots
[⌊Pixels tab: OpenAI, Meta and Google providers with their own IDs, consent mode,
hashed customer data and Conversions API settings.⌉⌊Pixels tab: OpenAI, Meta and
Google providers with their own IDs, consent mode, hashed customer data and Conversions
API settings.⌉[
Pixels tab: OpenAI, Meta and Google providers with their own IDs, consent mode,
hashed customer data and Conversions API settings.
[⌊Events tab: the debugger shows every tracked event, the exact payload each provider
received and the Conversions API result.⌉⌊Events tab: the debugger shows every tracked
event, the exact payload each provider received and the Conversions API result.⌉[
Events tab: the debugger shows every tracked event, the exact payload each provider
received and the Conversions API result.
[⌊Product feed tab: OpenAI product feed and Meta catalog feed with private URLs,
schedule and status.⌉⌊Product feed tab: OpenAI product feed and Meta catalog feed
with private URLs, schedule and status.⌉[
Product feed tab: OpenAI product feed and Meta catalog feed with private URLs, schedule
and status.
## Installation
1. Upload the `openpixly` folder to `/wp-content/plugins/`.
2. Activate the plugin through the “Plugins” screen in WordPress.
3. Go to Settings > Pixel Manager, enter the Pixel ID of the provider(s) you use and
enable them.
## FAQ
### Where do I find my Pixel ID and Conversions API key?
In ChatGPT Ads Manager, Conversions tab. For Meta: Events Manager > Data sources(
Pixel / dataset ID) and the dataset’s Settings > Conversions API > Generate access
token.
### My site uses a Content Security Policy.
Allow `script-src https://bzrcdn.openai.com`, `connect-src https://bzr.openai.com
https://bzrcdn.openai.com`
and `img-src https://bzr.openai.com`. For the Google
tag add `script-src https://www.googletagmanager.com` and `connect-src` / `img-src
https://www.google-analytics.com https://www.googleadservices.com https://googleads.
g.doubleclick.net https://www.google.com`. For the Meta pixel add `script-src https://
connect.facebook.net` and `connect-src` / `img-src https://www.facebook.com`. Use
the `openpixel_script_nonce` filter to add your nonce to the inline snippets.
### Does it work with WooCommerce HPOS?
Yes. The plugin only uses the WooCommerce CRUD order API and declares HPOS compatibility.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Openpixly – Conversion Tracking & Product Feed for OpenAI Ads” is open source software.
The following people have contributed to this plugin.
Contributors
* [ Özgür KARALAR ](https://profiles.wordpress.org/zgrkaralar/)
* [ unbelievabledigital ](https://profiles.wordpress.org/unbelievabledigital/)
[Translate “Openpixly – Conversion Tracking & Product Feed for OpenAI Ads” into your language.](https://translate.wordpress.org/projects/wp-plugins/openpixly)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/openpixly/), check
out the [SVN repository](https://plugins.svn.wordpress.org/openpixly/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/openpixly/) by [RSS](https://plugins.trac.wordpress.org/log/openpixly/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.5.1
* Events tab: the table no longer overflows on narrow screens; providers now explain
why an event was not sent (e.g. page_view is sent by the Google tag’s config).
* Screenshots on WordPress.org.
#### 1.5.0
* New: Google provider (Google tag): GA4 ecommerce events, Google Ads conversions
per event via conversion labels, enhanced conversions with server-side hashing,
Consent Mode v2.
* New: lead forms — Contact Form 7, WPForms and Gravity Forms submissions tracked
as leads on every provider, in the browser (from the AJAX response) and server-
side with the same event ID.
* Guests without a WooCommerce session now get a short-lived cookie so events raised
during a redirecting request (forms, registration) still reach the next page.
#### 1.4.0
* New: Events tab (Settings > Pixel Manager > Events): a debugger that records
the last 50 events for 24 hours with the request that raised them, each provider’s
payload and the Conversions API result, plus a summary of the consent configuration.
Customer data is not stored.
* New: registration_completed / CompleteRegistration is also sent from the server
through the Conversions API with the same event ID as the browser event, so sign-
ups on redirecting flows are no longer lost.
* New: `channel => 'both'` for custom events: browser event plus a server copy
whose IP, user agent, URL and attribution cookies are filled from the current
request.
* Fix: no page_view was built for /favicon.ico requests.
#### 1.3.1
* Fix: with “Require consent first” and the WP Consent API, consent granted on
an earlier page was lost on templates where openpixel.js loaded before wp-consent-
api.js, so no events fired (GitHub #1). The runtime now depends on the wp-consent-
api script, re-checks consent after the DOM and page load, and the server no
longer prints consent = false when the consent management plugin already reports“
marketing” as allowed.
#### 1.3.0
* New: Meta (Facebook & Instagram) Pixel provider: PageView, ViewContent, AddToCart,
InitiateCheckout, Purchase, CompleteRegistration and custom events, hashed advanced
matching, consent mode, noscript fallback.
* New: Meta Conversions API: server-side Purchase with the same event ID as the
browser event, `_fbp` / `_fbc` captured at checkout, async delivery with retries,
test event code support.
* New: Meta catalog feed (CSV) built alongside the OpenAI product feed, at its
own private URL, with ids that match the pixel’s content_ids.
* Each provider’s “Track WooCommerce events” switch now only affects that provider.
* Fix: the browser de-duplication of replayed events is now per provider, so two
pixels sharing an event ID both receive it.
#### 1.2.1
* Product feed URL is now a plain path (https://your-site/openpixly-feed//products.
csv) so it can be pasted into Ads Manager “Connect your feed via URL”, which
rejects query-string URLs. The old ?openpixel_feed= URL keeps working.
#### 1.2.0
* Renamed to Openpixly (slug openpixly). Not affiliated with OpenAI.
* Readme: external services, data sent and consent documented.
* Product feed: WooCommerce catalog export in the OpenAI product feed format or
Google-compatible profile (CSV/TSV/JSONL), variants with group_id/variant_dict,
scheduled rebuilds, private tokenized URL, download and URL rotation.
* Fix: Conversions API deliveries failed with “no callbacks are registered” when
run from Action Scheduler.
* page_viewed on the order-received page now reports “order-received” instead of
the Checkout page.
* No duplicate contents_viewed after a classic add-to-cart reload.
#### 1.1.0
* Native Measurement Pixel loader, page_viewed, consent mode, debug mode, noscript
image tag.
* WooCommerce events: contents_viewed, items_added, checkout_started, order_created,
registration_completed.
* Advanced matching with server-side normalization and SHA-256 hashing.
* Conversions API: server-side order_created with deduplication, async delivery,
retries, logging, validate-only test.
* Provider-agnostic event bus for future Meta/Google providers.
#### 1.0.0
* Initial release.
## Meta
* Version **1.5.1**
* Last updated **19 hours ago**
* Active installations **60+**
* WordPress version ** 5.8 or higher **
* Tested up to **7.1.2**
* PHP version ** 7.4 or higher **
* Language
* [English (US)](https://wordpress.org/plugins/openpixly/)
* Tags
* [chatgpt ads](https://vec.wordpress.org/plugins/tags/chatgpt-ads/)[conversion tracking](https://vec.wordpress.org/plugins/tags/conversion-tracking/)
[google ads](https://vec.wordpress.org/plugins/tags/google-ads/)[Meta Pixel](https://vec.wordpress.org/plugins/tags/meta-pixel/)
[openai](https://vec.wordpress.org/plugins/tags/openai/)
* [Advanced View](https://vec.wordpress.org/plugins/openpixly/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/openpixly/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/openpixly/reviews/)
## Contributors
* [ Özgür KARALAR ](https://profiles.wordpress.org/zgrkaralar/)
* [ unbelievabledigital ](https://profiles.wordpress.org/unbelievabledigital/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/openpixly/)