Pixel Manager Pro for WooCommerce premium v1.64.0

* New: Added the `pmw_facebook_pixel_identifiers` filter for tracking multiple Facebook (Meta) pixels at the same time; every browser event is sent to all configured pixels
* New: Added a check that detects active Meta Event Setup Tool rules on the Facebook pixel and warns in the opportunities and the debug info, because those point-and-click rules fire additional events without deduplication and mostly without values, which inflates event counts and corrupts purchase values in Meta
* New: Added an “Ask Pixie” chat icon next to most settings, from the pixel IDs and API tokens to the consent and order configuration options, that opens the AI assistant with a ready-to-send question about that setting
* New: Added Criteo as a new tracking pixel (Pro, beta), loading the Criteo OneTag and sending the full shopping journey to Criteo for retargeting and audience building: homepage views, product listing views, product views, add to cart, basket views, and purchases with order ID and product details; an optional advanced matching setting sends the hashed email of logged-in customers and purchasers to improve match rates
* New: Added Nextdoor as a new tracking pixel (Pro, beta), loading the Nextdoor Universal Pixel and sending the standardized conversion events Nextdoor uses for attribution and campaign optimization: page views, product views, add to cart, checkout initiation, searches, and purchases with order ID, order value, and product details; an optional advanced matching setting sends the hashed email of logged-in customers and purchasers to improve match rates
* New: Added the Nextdoor Conversion API (Pro, beta): with a Conversion API token set, all Nextdoor events are also sent server-side, including purchases triggered by WooCommerce order hooks, with shared event IDs so Nextdoor deduplicates the browser pixel and the server events; the Nextdoor click ID (ndclid) is captured on the landing page and attached for attribution, a test event code setting marks events as test events, and the events are routed through the server-side proxy when SweetCode Cloud is connected
* New: Additional Facebook pixels added through the `pmw_facebook_pixel_identifiers` filter can carry their own Conversion API token, so server-side events, including purchases and subscription lifecycle events, are sent to every pixel, both when sending directly and through the server-side proxy (Pro)
* New: The OpenAI (ChatGPT) Conversions API now includes the ChatGPT click reference (the oppref URL parameter): it is captured on the landing page, preserved through checkout, and attached to all Conversions API events, including the purchase and subscription events, so OpenAI can attribute conversions to the originating ChatGPT interaction (Pro)
* New: Added Hyros as a new tracking pixel (Pro, beta) in the Attribution category, loading the Hyros Universal Script consent-aware and cache-safe on every page, so the tracking script no longer has to be pasted into the theme header; just enter the product hash from Hyros, or paste the whole Universal Script snippet and the Pixel Manager extracts it; the shopping funnel milestones (add to cart, checkout start, purchase) are added to the visitor journey as Hyros action tags, and an optional application tag setting separates the shop traffic from other funnels on the same Hyros account
* Tweak: The Facebook (Meta) pixel now detects when another script on the site has defined window.fbq before the Pixel Manager loaded it and logs a clear warning in the browser console, because such a script prevents Meta’s standard bootstrap from loading fbevents.js and the browser pixel silently stops tracking
* Tweak: The Pixel Manager now detects when Meta restricts events for a Facebook (Meta) pixel because of its business category (e.g. health and wellness) and reports the restricted event names in the browser console and in the debug info, because Meta silently drops those events in the browser and on the Conversion API while page views keep working, which looks like a tracking failure even though it is enforced by Meta; a business category review can be requested in the Meta Events Manager
* Tweak: API tokens are now masked in the log; with request logging enabled, credentials that travel in the request URL (Meta and Snapchat access tokens, the GA4 Measurement Protocol API secret) or in an authorization header used to end up in clear text in the WooCommerce log, which is a file that gets shared with support and third parties; only the last four characters of a credential are shown now, and unknown URL parameters are masked by default
* Tweak: The “PMW pixels not fired” counter above the WooCommerce order list no longer loads every matching order into memory just to count it; the number now comes from a counting query and is cached for a few minutes, which noticeably speeds up the order list on shops with many orders
* Tweak: The order value calculation no longer looks up the brand and the categories of the same product more than once per request, which reduces the number of database queries on shop, category, cart, and order pages, most visibly on pages that list many products
* Tweak: The notification count next to the Pixel Manager entry in the WooCommerce menu is now cached instead of being recalculated on every single admin page load; calculating it meant loading all opportunity checks, one of which aggregates the tracking accuracy statistics, so every admin page in the shop paid for it
* Tweak: The notification script and stylesheet are now only loaded on the admin pages that can actually display a Pixel Manager notification (the WordPress dashboard and the Pixel Manager settings), instead of on every admin page
* Tweak: The tracking accuracy database maintenance (creating the table after an update and scheduling the one-time backfill) no longer runs on storefront and checkout requests; until the backfill had finished, every single page view asked the Action Scheduler whether the backfill was already queued, which is a database query on the critical path; the maintenance now runs on admin, cron, and WP-CLI requests only
* Tweak: The tracking accuracy statistics no longer re-check whether their database table exists on every read and write within the same request, which removes several redundant queries from the purchase path
* Tweak: The product identifier setting now refers to the “Google for WooCommerce” plugin under its current name instead of “Google Listings & Ads”, with the former name kept as a hint so the option is still recognizable; the plugin was renamed by WooCommerce a while ago, and the old name made it hard to tell which of the two plugins the gla_ option belongs to
* Tweak: Orders are now saved only once during checkout instead of once per active server-side integration; with several server-side integrations enabled (for example the Meta Conversion API, the GA4 Measurement Protocol, and the TikTok Events API), storing the tracking identifiers on the order triggered a separate full order write for each of them, which slowed down the checkout on busy shops (Pro)
* Tweak: The lifetime value recalculation control now shows what will actually happen: the first click schedules the run for 2:00 AM so it stays out of your busiest hours, and while it is scheduled you can start it immediately instead or stop it again; the button previously said it would recalculate right away while it only ever scheduled an overnight run (Pro)
* Fix: Corrected broken or outdated documentation links in the settings (SweetCode Cloud, LinkedIn, Reddit, LTV recalculation) and added the missing documentation link to the “Disable tracking for user roles” setting
* Fix: The add to cart event for WooCommerce Product Bundles now reports the value of the bundle as configured by the shopper, instead of the static minimum bundle price, which is 0 for bundles where all items are optional or for bundled subscriptions without an up-front fee
* Fix: The add to cart event for WooCommerce Product Bundles now reads the quantity from the bundle’s own quantity field; before, it could pick up the quantity of the first bundled item
* Fix: The customer lifetime value is now resolved per email address; when more than one email address was looked up during the same request, every address after the first one received the order history of the first one, which reported the wrong lifetime value
* Fix: The OpenAI (ChatGPT) settings (pixel ID, advanced matching, and the Conversions API token) are now part of the Abilities API settings catalog; before, AI agents could not discover or configure the OpenAI pixel (Pro)
* Fix: Removing the GA4 Measurement Protocol API secret and adding it back later no longer sends the purchases of the orders that were paid in the meantime a second time; while the API secret is empty the purchase is sent from the browser instead, which is now recorded on the order so the Measurement Protocol skips it when that order later moves to another paid status, for example from processing to completed; before, those orders were counted twice in GA4, with the duplicate landing on the date of the status change and without a traffic source (Pro)
* Fix: Removed the “Automatic LTV recalculation” setting, which had no effect; the background detection it described was switched off some time ago because it caused serious performance problems on large shops, so the setting promised something that never happened; the lifetime value of a customer is still updated automatically after a refund or a cancellation, and a full recalculation across all customers is started from the recalculation control in the shop settings, which is the right moment to run it after changing the order value logic or a value filter in your theme (Pro)