Release v1.64.0
Pixel Manager Pro for WooCommerce v1.64.0
Latest versionWhat's new in v1.64.0
Pixel Manager Pro for WooCommerce v1.64.0 was released on . Transmit visitor tracking information, events, and conversions to Google Analytics, Google Ads, Facebook Ads, Microsoft Ads, and more with Pixel Manager Pro for WooCommerce. See the full changelog below and compare with the complete version history.
Release details
Released
6.7 MB
File available
Changelog
Other
- Release date - 29.07.2026*
Added
- 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
- 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
- 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
- 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
- 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
- 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
- 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)
- 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)
- 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
Improved
- 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
- 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
- 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
- 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
- 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, cat
Compatibility
- Requires WordPress
- 6.2
- Tested up to
- 7.0
- Requires PHP
- 7.3
Verified safe
Pixel Manager Pro for WooCommerce v1.64.0 scanned clean with no security threats detected.
View full scan report