Pixel Manager Pro for WooCommerce icon

12 versions

Pixel Manager Pro for WooCommerce history.

Every release of Pixel Manager Pro for WooCommerce is archived here with its changelog, file size, and security scan result. Use the archive to roll back to a stable release or audit what changed between updates.

12 of 12 releases scanned clean
v1.64.0Latest
July 29, 20266.7 MBScanned
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
July 14, 20266.6 MBScanned
Other
  • Release date - 15.07.2026*
Added
  • Added GroundTruth as a new tracking pixel (Pro, beta), loading the GroundTruth Web Engagement Pixel for omnichannel ad attribution across mobile, desktop, CTV, and audio, and sending add to cart and purchase events with order values; just enter the GTID provided by your GroundTruth representative
  • Added Triple Whale as a new tracking pixel (Pro, beta) under a new Attribution category; a single toggle loads the Triple Pixel for visitor journey tracking (no pixel ID needed, the shop is identified by its domain), and an optional Orders API key syncs order records including refunds server-side to Triple Whale, which completes the attribution without connecting the store's REST API to Triple Whale
  • Added an Attribution pixel category, which appears as its own group in the settings and follows the statistics consent category for consent management
June 29, 20266.5 MBScanned
Other
  • Release date - 29.06.2026*
Added
  • Added Microsoft Clarity as a new tracking pixel (beta), loading the Clarity tag for heatmaps and session recordings and sending add to cart, begin checkout, and purchase events so you can analyze the full shopping experience; just enter your Clarity project ID
Improved
  • When you enable the Google Tag Gateway but your site is not served through a Cloudflare edge, the Pixel Manager now warns you once that the gateway is handled by your own server and adds load, so you can move it behind Cloudflare, keep it as-is, or turn it off
  • The confirmation that appears when you turn on a consent gate (Explicit Consent Mode, or Google TCF support) now offers only "Enable anyway" or "Cancel" and can no longer be closed by clicking beside it, pressing Escape, or a close icon, so this consequential choice is not dismissed by accident
  • Added a `pmw_product_price_for_datalayer` filter to override the per-product price used in the browser events
  • WooCommerce Product Bundles and Composite Products are now counted once at their full bundle price in purchase and cart events, instead of listing the bundle container alongside each of its child products
  • The first time you turn on server-side tracking by adding a Conversions API token, the Pixel Manager now lets you know it adds load to your server and offers to route it through SweetCode Cloud, keep it on your server, or turn it back off
  • Added a `pmw_conversion_adjustments_feed_row` filter that lets developers exclude or modify individual rows of the Google Ads conversion adjustments feed, for example to drop orders that did not originate from a Google Ads click such as marketplace imports (Amazon, eBay); the plugin re-applies its own validation afterwards so the feed stays within Google's spec
  • The server-side Google Analytics payload passed to the `pmw_server_event_payload_google_analytics` filters now exposes `events` as an array of event objects (`$payload['events'][0]['params']`) instead of a single event object, to match the Measurement Protocol format; update any custom callbacks that read the event parameters accordingly
Fixed
  • After you changed your Google tag or conversion ID, the old ID could keep being used for up to an hour because the cached tag ID was not cleared when you saved your settings; the cache is now cleared on save, so the new ID takes effect immediately
  • When Google Consent Mode was enabled without a cookie banner, Google Analytics and Google Ads could stop receiving data because the consent signal was applied a moment too late; the Pixel Manager now sets it before the Google tag loads, so your data flows in again
  • WooCommerce Product Bundles and Composite Products that are priced per item reported a price of 0 in the add to cart and view item events; the Pixel Manager now reports the real bundle price
  • Server-side Google Analytics 4 purchase and refund events were sent with the event wrapped as a single object instead of the array that Google's Measurement Protocol expects; they are now sent in the correct array format so Google Analytics records them reliably
April 13, 20266.4 MBScanned
Other
  • Release date - 14.04.2026*
Improved
  • Added `pmw_` prefix to all generated event IDs for easier debugging and source identification
  • Added `pmw_` prefix to purchase event IDs across all server-side conversion API integrations for consistent event identification
  • Removed client IP geolocation via external services and AJAX session storage for non-SSP setups, relying on WooCommerce native IP capture instead
Fixed
  • Fixed a PHP 8+ fatal error caused by calling count() on a null value in the Meta CAPI identifier collection
  • Fixed Termly CMP integration ignoring actual visitor consent choices and always granting full consent due to a hardcoded event payload
v1.58.8Unavailable
April 10, 20266.4 MBScanned
Other
  • Release date - 09.08.2026*
Improved
  • Added diagnostic consent decision logging that explains why consent categories were set to their values when the logger is active, including mode, CMP source, and region check details
  • Eliminated the REST API preflight test request by using optimistic-try with AJAX fallback, saving one HTTP round-trip per browser session
  • Added diagnostic logging for tracking cookie capture across the S2S identifier chain to investigate missing cookies in some purchase events
Fixed
  • Fixed WooCommerce HPOS compatibility not being declared for inactive remnant PMW plugin folders, causing false "incompatible" warnings on the plugins page
v1.58.5Unavailable
March 25, 20266.1 MBScanned
Other
  • Release date - 24.03.2026*
Improved
  • Updated PHPCS tooling (WPCS 3.3.0, woocommerce-sniffs 1.0.1) and resolved all coding standards violations
  • Added support for Google Ads conversion ID format (AW-) as a valid GA4 measurement ID
  • Improved tracking accuracy analysis performance and reliability
  • Added event-driven tracking accuracy table — per-order real-time writes replace the nightly batch analysis, with automatic 3-month backfill and graceful fallback to transients during transition
  • Added comprehensive Action Scheduler cleanup on plugin deactivation, preventing orphaned pending tasks for tracking accuracy, duplication prevention, HTTP logging, LTV calculation, and SSP sync
  • Fixed WP Rocket JS minification and combination breaking webpack chunk loading (ChunkLoadError) — PMW scripts are now always excluded from WP Rocket's minify and combine features, independent of compatibility mode
  • Removed Maximum Compatibility Mode setting — JS optimization exclusions (minify, combine, delay JS on critical pages) are now automatic for all supported performance plugins
  • Redesigned LTV recalculation for large shops — in-memory batch processing with time/memory safety valves, early termination, loop-safe continuation, and resilient retry counters that survive rescheduling
  • Renamed TikTok purchase event from CompletePayment to Purchase
  • Renamed SSP verification key to domain token across data layer and sync API for clearer naming
Fixed
  • Fixed Google Tag Gateway proxy returning 400 errors on some shops due to overly aggressive path sanitization
  • Fixed Google Tag Gateway proxy generating malformed conversion tracking URLs on some shops due to double-rewriting CCM paths
v1.58.4Unavailable
March 19, 20266.1 MBScanned

No changelog available for this version.

v1.58.0Unavailable
March 6, 20266.1 MBScanned
Other
  • Release date - 02.03.2026*
Added
  • Added multi-domain SSP support via `pmw_ssp_additional_domains` filter for WordPress installs serving multiple domains without multisite
  • Added unified IP exclusion filter (`pmw_ip_exclusion_list`) to block specific IPs and CIDR ranges from all tracking — browser pixels, browser-initiated S2S, server-side purchase events, and SSP proxy
  • Declared compatibility with WooCommerce Product Instance Caching (experimental feature in WooCommerce 10.5+)
  • Added SSP sync token domain validation to prevent token reuse across different shops
  • Added SSP disconnect notification to clean up server-side callback data
Improved
  • Added support for suppressed Google Ads and GA4 tags in the Google Tag Gateway Proxy
  • Improved S2S payload accuracy for Facebook, TikTok, Pinterest, and Reddit adapters
  • Removed the "Skip server-side events with no destination platforms" setting — empty events are now always skipped
Fixed
  • Fixed SSP daily sync not running while DNS routing or config status were still pending, preventing SSP from becoming active after initial setup
  • Fixed Pinterest search event using wrong field name for Conversions API
v1.57.0Unavailable
February 27, 20266.1 MBScanned
Other
  • Release date - 24.02.2026*
Added
  • Added SSP Purchase Proxy to offload purchase conversion events (S2S) through the SweetCode Cloud proxy
  • Added "Always Send Server-Side Events" setting to keep sending S2S events even when browser-side pixels are blocked
  • Implemented account created event tracking
  • Added Abilities API integration
Improved
  • Implement cross-tab session synchronization for improved data consistency
  • Added option to skip empty server-side events to reduce unnecessary S2S traffic
  • Added modern styling and impact indicators to opportunity cards
  • Bumped up WC version compatibility to 10.5
  • Enhanced GTG Proxy: Improved config resilience, reduced unnecessary health check requests, and added periodic config refresh
  • Implemented REST API for saving settings via AJAX; refactored admin tabs and enhance section rendering
  • Update styles for impact badges and add Google Automated Discounts and Customer Reviews opportunities
  • Improved consent revocation handling: S2S pixels now respect real-time consent status changes without requiring a page reload
Fixed
  • Resolved an issue where page_view events were sent server-to-server even when the "Track PageView events server-to-server" setting was disabled.
  • Fixed duplicate page_view S2S events being sent when consent was granted via the Consent API
v1.56.0Unavailable
February 14, 20266.0 MBScanned
Other
  • Release date - 02.02.2026*
Added
  • CrazyEgg pixel
Improved
  • Google Tag Gateway Proxy: Improved handling of config file

Why archive

Sometimes the latest release isn't the one you need. The archive lets you pin Pixel Manager Pro for WooCommerce to a known-good version, or roll back while a bug is investigated. Every release stays scanned and reachable.