Openpixly – Conversion Tracking & Product Feed for OpenAI Ads

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 <noscript> 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.

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.