Openpixly installs the official ChatGPT Ads Measurement Pixel on every\npage and sends the standard conversion events for you:<\/p>\n\n
page_viewed<\/code> on every page.<\/li>\ncontents_viewed<\/code> on WooCommerce product pages.<\/li>\nitems_added<\/code> on add to cart (classic, AJAX and block\/Store API carts).<\/li>\ncheckout_started<\/code> on the checkout page.<\/li>\norder_created<\/code> on the order-received page, and again from the server\nthrough the Conversions API with the same event ID so OpenAI deduplicates it.<\/li>\nregistration_completed<\/code> when a user or customer registers.<\/li>\n<\/ul>\n\nAmounts are sent as integers in the currency's ISO 4217 minor unit, customer\nidentifiers are normalized and SHA-256 hashed on the server before they reach\nthe browser, and a <noscript><\/code> image tag covers visitors without JavaScript.<\/p>\n\nMeta (Facebook & Instagram) pixel<\/h4>\n\n
Enable the Meta provider and enter your Pixel ID to send the same events to\nMeta: PageView<\/code>, ViewContent<\/code>, AddToCart<\/code>, InitiateCheckout<\/code>, Purchase<\/code>\nand CompleteRegistration<\/code>, with content_ids<\/code> \/ contents<\/code> that match the\nMeta catalog feed. Advanced matching data is normalized and SHA-256 hashed on\nthe server. With a Conversions API access token, Purchase<\/code> is also sent from\nthe server with the same event ID, the _fbp<\/code> \/ _fbc<\/code> cookies captured at\ncheckout, and the customer's IP address and user agent, so Meta deduplicates\nbrowser and server events. Each provider has its own \"Track WooCommerce\nevents\" switch.<\/p>\n\nConsent<\/h4>\n\n
Choose \"Require consent first\" to initialize the pixel with consent set to\n false. Grant consent from your cookie banner with window.openPixel.grantConsent()<\/code>;\nthe WP Consent API \"marketing\" category is detected automatically.<\/p>\n\nConversions API<\/h4>\n\n
Enable it and paste the API key from the Conversions tab of Ads Manager (for\nMeta: the access token from Events Manager). Orders are delivered\nasynchronously with retries and logged under WooCommerce > Status > Logs\n(source: openpixly). The OpenAI \"Send test event\" button validates your\ncredentials without recording anything; the Meta one sends the event with\nyour test event code so it only shows under Events Manager > Test events.<\/p>\n\n
Product feed for ChatGPT Ads<\/h4>\n\n
The Product feed tab builds a catalog file from your WooCommerce products in\nthe OpenAI product feed format (or the Google-compatible profile) as CSV, TSV\nor JSONL: one row per simple product or variation, with group_id and\nvariant_dict for variants, prices as \"79.99 USD\", availability, images,\nbrand, category, GTIN\/MPN and is_ads_eligible. The file is rebuilt on a\nschedule and served at a private tokenized URL you can hand to OpenAI, or\ndownloaded for upload to the SFTP location shown in Ads Manager > Feeds.<\/p>\n\n
Meta catalog feed<\/h4>\n\n
Switch on \"Also build a Meta catalog feed\" and the same build writes a second\nCSV in Meta's catalog format (id, title, description, availability, condition,\nprice, link, image_link, brand, sale_price, item_group_id, ...), served at its\nown private URL. Paste it in Commerce Manager > Catalog > Data sources > Data\nfeed > Scheduled feed. Item ids equal the pixel's content_ids, which is what\nAdvantage+ catalog ads need.<\/p>\n\n
Extensible<\/h4>\n\n
The plugin is a small pixel manager: integrations emit normalized events on\na bus and each provider maps them to its own API. Additional providers\n(Google Ads, TikTok, ...) can be registered with the\n openpixel_pixel_providers filter.<\/p>\n\n
External services<\/h3>\n\n
This plugin is an integration with OpenAI's ChatGPT Ads measurement services and, optionally, Meta's (Facebook & Instagram) measurement services. Openpixly is developed by Unbelievable Digital and is not affiliated with or endorsed by OpenAI or Meta. Nothing is loaded or sent to a service until a site administrator enables that provider and enters its Pixel ID.<\/p>\n\n
OpenAI Measurement Pixel (browser SDK)<\/strong> \u2014 https:\/\/bzrcdn.openai.com\/sdk\/oaiq.min.js and https:\/\/bzrcdn.openai.com\/pixel-config\/ \u2014 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<\/code>, __obref<\/code>) 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.<\/p>\n\nOpenAI image tag (no-JavaScript fallback)<\/strong> \u2014 https:\/\/bzr.openai.com\/v1\/sdk\/events \u2014 when enabled, a 1x1 image records a page view for visitors without JavaScript. It carries only the Pixel ID and event name.<\/p>\n\nOpenAI Conversions API (server-to-server)<\/strong> \u2014 https:\/\/bzr.openai.com\/v1\/events \u2014 only when enabled with your Conversions API key. 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<\/code> set, which OpenAI validates but does not store.<\/p>\n\nThe product feed feature does not contact OpenAI or Meta by itself; it generates files on your server that you choose to give to them.<\/p>\n\n
Service provider: OpenAI, L.L.C. Terms of use: https:\/\/openai.com\/policies\/terms-of-use\/ \u2014 Privacy policy: https:\/\/openai.com\/policies\/privacy-policy\/ \u2014 ChatGPT Ads developer documentation: https:\/\/developers.openai.com\/ads<\/p>\n\n
Meta Pixel (browser SDK)<\/strong> \u2014 https:\/\/connect.facebook.net\/en_US\/fbevents.js \u2014 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<\/code>, _fbc<\/code>) 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.<\/p>\n\nMeta image tag (no-JavaScript fallback)<\/strong> \u2014 https:\/\/www.facebook.com\/tr \u2014 when enabled, a 1x1 image records a PageView for visitors without JavaScript. It carries only the Pixel ID and event name.<\/p>\n\nMeta Conversions API (server-to-server)<\/strong> \u2014 https:\/\/graph.facebook.com\/ \u2014 only when enabled with your access token. 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<\/code> \/ _fbc<\/code> 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.<\/p>\n\nService provider: Meta Platforms, Inc. \/ Meta Platforms Ireland Ltd. Meta Business Tools terms: https:\/\/www.facebook.com\/legal\/terms\/businesstools \u2014 Privacy policy: https:\/\/www.facebook.com\/privacy\/policy\/ \u2014 Developer documentation: https:\/\/developers.facebook.com\/docs\/meta-pixel<\/p>\n\n
Consent.<\/strong> 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)<\/code> \/ fbq(\"consent\", \"revoke\")<\/code>) and only measures after your cookie banner calls window.openPixel.grantConsent()<\/code> 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.<\/p>\n\n\n\n- Upload the
openpixly<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n- Activate the plugin through the \"Plugins\" screen in WordPress.<\/li>\n
- Go to Settings > Pixel Manager, enter the Pixel ID of the provider(s) you use and enable them.<\/li>\n<\/ol>\n\n\n
\nWhere do I find my Pixel ID and Conversions API key?<\/h3><\/dt>\nIn ChatGPT Ads Manager, Conversions tab. For Meta: Events Manager > Data sources (Pixel \/ dataset ID) and the dataset's Settings > Conversions API > Generate access token.<\/p><\/dd>\n
My site uses a Content Security Policy.<\/h3><\/dt>\nAllow script-src https:\/\/bzrcdn.openai.com<\/code>, connect-src https:\/\/bzr.openai.com https:\/\/bzrcdn.openai.com<\/code>\nand img-src https:\/\/bzr.openai.com<\/code>. For the Meta pixel add script-src https:\/\/connect.facebook.net<\/code> and connect-src<\/code> \/ img-src https:\/\/www.facebook.com<\/code>. Use the openpixel_script_nonce<\/code> filter to add your nonce to the inline snippets.<\/p><\/dd>\nDoes it work with WooCommerce HPOS?<\/h3><\/dt>\nYes. The plugin only uses the WooCommerce CRUD order API and declares HPOS compatibility.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.3.0<\/h4>\n\n\n- New: Meta (Facebook & Instagram) Pixel provider: PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, CompleteRegistration and custom events, hashed advanced matching, consent mode, noscript fallback.<\/li>\n
- New: Meta Conversions API: server-side Purchase with the same event ID as the browser event,
_fbp<\/code> \/ _fbc<\/code> captured at checkout, async delivery with retries, test event code support.<\/li>\n- 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.<\/li>\n
- Each provider's \"Track WooCommerce events\" switch now only affects that provider.<\/li>\n
- Fix: the browser de-duplication of replayed events is now per provider, so two pixels sharing an event ID both receive it.<\/li>\n<\/ul>\n\n
1.2.1<\/h4>\n\n\n- 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.<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Renamed to Openpixly (slug openpixly). Not affiliated with OpenAI.<\/li>\n
- Readme: external services, data sent and consent documented.<\/li>\n
- 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.<\/li>\n
- Fix: Conversions API deliveries failed with \"no callbacks are registered\" when run from Action Scheduler.<\/li>\n
- page_viewed on the order-received page now reports \"order-received\" instead of the Checkout page.<\/li>\n
- No duplicate contents_viewed after a classic add-to-cart reload.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Native Measurement Pixel loader, page_viewed, consent mode, debug mode, noscript image tag.<\/li>\n
- WooCommerce events: contents_viewed, items_added, checkout_started, order_created, registration_completed.<\/li>\n
- Advanced matching with server-side normalization and SHA-256 hashing.<\/li>\n
- Conversions API: server-side order_created with deduplication, async delivery, retries, logging, validate-only test.<\/li>\n
- Provider-agnostic event bus for future Meta\/Google providers.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n<\/ul>","raw_excerpt":"Conversion pixel manager for WooCommerce: OpenAI (ChatGPT Ads) and Meta pixels, their Conversions APIs, and product feeds for both catalogs.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/365441","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=365441"}],"author":[{"embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/zgrkaralar"}],"wp:attachment":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=365441"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=365441"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=365441"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=365441"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=365441"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=365441"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}