Pixel Manager for WooCommerce · Version history
Pixel Manager for WooCommerce changelog and version history
- Latest version
- 1.72.0
- Nov 4, 2026 (6 days ago)
- Releases
- 96
- since 2013
- In the last year
- 36
- about one every 10 days
- Tested up to
- WordPress 7.1.4
- PHP 7.3 or later
Releases each year
- 20131 release
- 20141 release
- 20152 releases
- 20162 releases
- 20171 release
- 20192 releases
- 20201 release
- 20215 releases
- 202217 releases
- 20238 releases
- 202412 releases
- 202516 releases
- 202628 releases
202628 releases
Pixel Manager for WooCommerce 1.72.0Latest
- Release date – 04.11.2026
- New: Each configured pixel now has an on/off switch that pauses it without losing its settings, stopping both browser and server-side tracking until it is resumed. Paused pixels are marked clearly on the Tracking Pixels tab, the Dashboard and the WordPress dashboard widget
- New: view_item_list now sends one event per product list with every item and its position, instead of one event per product, to GA4, Google Ads, Klaviyo, Mixpanel and Criteo. Related products and theme or page builder widgets such as WoodMart’s count as their own lists, and grouped events still go…
- Tweak: The payment gateway tracking accuracy report now warns when on-site gateways such as Stripe and WooPayments measure no orders at all. That points at a firewall or cache rule blocking the order confirmation beacon, or the Pixel Manager script not running on the order received page, not at a p…
- Tweak: The Google Tag Gateway proxy now logs requests without a valid tag ID, which crawlers send to the gateway URL, at debug level instead of as warnings, so they no longer flood the debug log
- Tweak: When a theme or plugin deregisters jQuery or wp-hooks, WordPress silently drops the Pixel Manager script and no pixel loads; the debug info and the Diagnostics tab now report it and name the missing script
- Tweak: The debug info now notes that a failing purchase confirmation page HTTP status was tested server side, since firewalls and bot protection often block such requests while buyers load the page fine
- Tweak: The tracking pixel search now also finds pixels by the names people know them under, so searching for ChatGPT shows the OpenAI pixel
- Tweak: Every user now gets the Nova settings interface, and the switch back to the Classic interface is gone from the Support page. If Nova runs into a problem on a site, the pmw_use_classic_admin_interface filter brings back the Classic interface
- Tweak: With the logger on (pmwloggeron), the order confirmation page now says when the order duplication prevention held back an already reported purchase, and names the nodedupe parameter that tests it again
- Tweak: The browser console now warns when the data layer is on a page but the Pixel Manager library did not start, for example because the server sends its script compressed without a Content-Encoding header
- Fix: WooAds no longer reports a missing TikTok pixel on shops where the Pixel Manager runs TikTok. The TikTok for WooCommerce pixel code is now hidden only on storefront requests, where its tracking stays off
- Fix: Reddit for WooCommerce no longer sends its base pixel, purchase and Conversions API events next to the Pixel Manager’s Reddit pixel, and Snapchat for WooCommerce is now switched off the same way when the Pixel Manager runs Snapchat
- Fix: When another plugin or a script optimizer keeps a WordPress core script such as wp-components from loading, the settings page now names the missing script and how to fix it, instead of crashing with a generic interface error
- Fix: The standalone Google Tag Gateway proxy now passes its health check when logging is set to info or debug. The check crashed, so the Google tag went through the slower WordPress handler instead
- Fix: When the standalone Google Tag Gateway proxy fails to serve the Google tag, it now loads through the WordPress handler before falling back to Google directly, and the visitor’s next pages skip the failed proxy instead of failing the same way
- Fix: The payment gateway tracking accuracy report now counts a gateway as active when it received orders in the last 30 days, so orders that a disabled legacy plugin still files under its ID, such as stripe_cc, no longer drop out of the active view and the weighted accuracy
- Fix: The payment gateway tracking accuracy report no longer shows a gateway above 100%. An order whose payment method changed after payment now moves its total to the new gateway, and two confirmations arriving at once, or an order placed before the Pixel Manager was active, no longer count as an e…
- Fix: The Environment card on the Diagnostics page now shows the same WordPress memory limit as the debug info, the higher of WP_MEMORY_LIMIT and the PHP memory_limit, instead of the WP_MEMORY_LIMIT constant alone
- Fix: Usercentrics Accept, Deny and Save choices now reach the Pixel Manager. With current Usercentrics versions, Meta and other marketing pixels stayed off on the page where the visitor accepted, and from the next page on they loaded even for visitors who had denied
- Fix: One rate-limited or failed request no longer moves the visitor’s whole session from the REST API to admin-ajax.php. Only a network error or a missing or blocked REST route does that now; anything else falls back for that request alone
- Fix: On shops that ask for consent first, pixels such as Meta that load when the visitor accepts the banner now receive the landing page view and product view of that page, once and with the original event IDs, so ad landing pages are tracked
- Fix: GA4 view_item_list and select_item events now send each product’s list position as the item index, which a field name mismatch had dropped. The index counts from 0, as GA4 expects, also on search results
- Fix: Pinterest product views are sent as PageVisit again instead of ViewContent, on the tag and the Conversions API. Pinterest requires PageVisit with a product ID for the Verified Merchant Program and catalog sales campaigns, and has flagged such tags as needing attention since 1.67.0
Pixel Manager for WooCommerce 1.71.0
- Release date – 20.10.2026
- Tweak: The tracking library loaded on every shop page is about 40% smaller, with IP and location lookups loading only on shops that use the IP exclusion list or region-based consent. Pixel code now downloads while the cookie banner check runs, so pixels start sooner
- Tweak: The Meta Purchase now carries the order number as order_id, which Events Manager listed as unavailable
- Tweak: Cookies the Pixel Manager writes in the browser now carry the Secure attribute on HTTPS pages, which PCI compliance scans check for
- Fix: The standalone Google Tag Gateway proxy no longer stops working a week after the last settings change, when it answered every request with a 503 and the Google tag loaded directly from Google instead
- Fix: The Google Tag Gateway service worker now registers with every gateway handler. The WordPress handler still logged a service worker scope error on every page after the 1.70.0 fix, and the standalone proxy answered the worker with a 400 error
- Fix: The standalone Google Tag Gateway proxy now works when WordPress core sits in its own subdirectory or the content folder is not named wp-content, as on Bedrock, instead of sending every request through the slower WordPress handler
- Fix: The standalone Google Tag Gateway proxy now sends empty POST requests with a length. Google refused them with a 411 error
- Fix: IP ranges in CIDR notation from the pmw_ip_exclusion_list filter now exclude the visitor in the browser too. A range broke the browser check, so only exact IPs stopped the browser pixels
- Fix: Pinterest checkout starts now carry each product’s category and brand, and over the Conversions API also its price, quantity and name, which Pinterest reported as missing
- Fix: Settings saved through the admin REST API are now checked against each setting’s type, and a save that names a whole group of settings validates every field inside it, Pro licensing included. A malformed save could store a list as the Google Tag Gateway path, which broke every shop page on PHP…
- Fix: Server-side requests to ad platforms and the debug report’s connection checks now always verify the TLS certificate. A crafted request header or a private server IP could switch the check off, and only sites set to the local environment type skip it
Pixel Manager for WooCommerce 1.70.0
- Release date – 13.10.2026
- New: With Explicit Consent Mode off, the Pixel Manager now applies the cookie banner’s own pre-decision state, so opt-in banners from Complianz, Cookiebot, CookieYes, OneTrust, iubenda, Usercentrics and others no longer let pixels fire before the visitor answers. For banners that load asynchronousl…
- New: The debug report lists the other active Google Analytics, Google Tag Manager and ad pixel plugins, so a second tracking setup shows up in the first support reply
- New: AI agents can now do everything the admin offers through the Abilities API, from backups, imports and logs to opportunities, SweetCode Cloud and the Google and Meta account connections, with exactly the access their user has in the admin, shop managers included. All abilities appear on the Wor…
- Tweak: The Meta Conversions API Gateway and Event Setup Tool checks run daily instead of weekly, and both cards say that Meta can keep reporting a removed setup for a while
- Tweak: A settings save that a security plugin or host firewall blocks before it reaches WordPress now says so and names the blocked request, instead of showing “API error 403”
- Tweak: A Nova page that hits an error no longer takes down the whole admin. Only that page is replaced by a request to contact support, with a button that copies the error details
- Tweak: With Explicit Consent Mode on, click IDs from the landing page URL are no longer stored in the browser before the visitor allows marketing. In every mode, declining or withdrawing marketing consent removes the stored click IDs
- Tweak: Updated Freemius SDK to the latest version
- Fix: The Google setup assistant now shows which permissions you allowed on Google’s consent screen and what stops working for the ones you declined. Reconnecting asks for the declined permissions again instead of silently reusing the earlier choice
- Fix: Google Ads conversions with cart data no longer deduct coupons twice. Item prices are now sent before coupons, as Google requires, because Google subtracts the order discount from the cart itself
- Fix: Beautiful and Responsive Cookie Consent’s built-in Pixel Manager integration no longer saves a permanent consent record that overrides the banner, which could keep a visitor who allowed marketing denied on every page. Visitors already affected are fixed on their next page view
- Fix: Cookiebot declines, Cookiefirst decisions and Usercentrics saved selections now reach the Pixel Manager, and unnamed Cookiefirst and Cookie Compliance categories count as denied
- Fix: A pixel that never loads, for example Meta behind an ad blocker, no longer suppresses the page view of every other pixel. The page view waits only when server-side page views are active, for at most three seconds, and never for a pixel the visitor has not consented to
- Fix: GA4 keeps tracking when the shop’s server cannot reach Google to check the tag ID, and an ID Google rejects gets an admin notice that explains the GT- alternative. Shops that also send GA4 through another tag, such as a GTM container, may now see page views double and should keep one sender
- Fix: Visitors recognised as bots or excluded by the IP exclusion list no longer load any browser pixel, so GA4’s automatic page view and the Google Ads remarketing hit no longer reach Google for them
- Fix: The Pixel Manager log no longer stays empty when WooCommerce logging is disabled or its level threshold is higher, and the Logger card says where the entries go
- Fix: A failed cart sync request no longer clears the stored cart, so the next page still has cart data for checkout events, and its error message says the request only reads the cart
- Fix: With the order subtotal value logic, a Stripe fee paid out in another currency than the order, for example AED on a EUR order, is converted to the order currency before it is deducted. It used to be subtracted as is, which under-reported conversion values and turned small orders into zero
- Fix: Turning off order de-duplication or turning on HTTP request logging through the Abilities API now arms the same timers as the admin interface, so de-duplication comes back on after 6 hours and logging switches off after 12 instead of staying that way
- Fix: The Google Tag Gateway service worker registers again. Since 1.69.1 the gateway dropped the header Google sends to allow it, so every page logged a service worker scope error in the browser console
- Fix: The server-load warnings for the Tag Gateway path and the first Conversions API token now appear when you leave the field, instead of interrupting your typing after the first character
- Fix: GA4 add_payment_info events include the selected payment method as payment_type again, on the classic checkout and the Checkout block, and switching payment methods within a second is no longer dropped as a duplicate
Pixel Manager for WooCommerce 1.69.1
- Release date – 22.09.2026
- Fix: A post title can no longer break out of the data layer script. WordPress keeps the entities of a closing script tag in a title saved by a Contributor, and the plugin decoded them right before writing the title into its inline script, so the markup after that tag ran on every view of the post.…
- Tweak: Every value the plugin prints into a script, an attribute or a link now goes through the escaping function that fits that exact position, so a value that a validation rule stops today stays harmless if that rule ever loosens. None of the corrected sites was exploitable
- Fix: The browser-to-server event endpoint refuses a purchase named inside a pixel’s own object. It only checked the wrapper’s event field, so an unauthenticated request could hand a fabricated purchase with any value straight to a merchant’s Conversions API. Every pixel object is now searched for a…
- Fix: A URL that merely carries an order key no longer turns the front page, an archive or a search result into the order confirmation. The plugin printed that order’s customer data into whatever page the key was appended to, and looked the key up however it was shaped. Confirmation pages are also s…
- Fix: The public rate limits count the connecting address first. The visitor address comes from proxy headers any client can set, so a rotating header used to hand out a fresh allowance per request and write a database row for each one. A real proxy still gets an allowance per visitor behind it
- Fix: The Google Tag Gateway proxy no longer forwards the visitor’s WordPress login and WooCommerce session cookies to Google’s servers, no longer follows an upstream redirect on the server, and relays only the response headers a browser needs, so a policy header from upstream cannot apply to the sh…
- Tweak: A settings import now runs every field through the same validator as the settings page, drops keys that are not settings, refuses a schema version the plugin does not know and, on a free tier, keeps the stored values of Pro-only settings. It used to check that a few keys exist and store the…
- Tweak: The products data layer cache is capped at 50 entries per page, an order key must look like one before it is looked up, click IDs from the landing URL are validated like those from cookies, the settings version can no longer be written as if it were a setting, log downloads are limited to th…
Pixel Manager for WooCommerce 1.69.0
- Release date – 21.09.2026
- Fix: A product a shopper adds while the plugin is reading the cart stays in the cart. WooCommerce serves the plugin’s requests with the whole session loaded and writes all of it back at the end, so a request that only reads could still put the older cart back and the added item vanished in front of…
- Fix: On shops that run iubenda, the visitor’s consent is read at last. iubenda names its cookie after the site ID by default, and the Pixel Manager knew only the older cookie policy ID name, so every category stayed denied and every marketing pixel blocked. It now also reads iubenda’s legacy cookie…
- Fix: An interface whose name carries no Interface_ prefix is now found by the plugin’s autoloader. Three of them, among them the pixel adapter contract every server-side pixel implements, were reachable only because four places required their file by hand, so any other code path that touched them e…
- Fix: A checkout started from the mini cart now carries the cart’s products, value and currency. The plugin left the cart empty while it re-read it from the server, and a checkout click is sent the moment it happens, so the event went out hollow on product and category pages
- Fix: An add to cart or add to wishlist event that reaches the Facebook pixel without product data no longer disappears. The adapter read the missing product and threw, so the event was lost from the browser pixel and the Conversions API alike. Meta needs the product on both events, so a productless…
- Fix: The Diagnostics accuracy trend no longer crashes the admin interface when a custom date is typed rather than picked. A date field reports itself as empty for as long as a typed entry is incomplete, and that empty value reached the report’s date arithmetic while the page was being drawn, so the…
- Fix: A blocked Google tag no longer fills the shop’s error tracking with stackless noise. When a content blocker kept the tag from loading, every Google Ads and Google Analytics event raised a promise rejection that carried no message at all, so the recorded entries named neither a cause nor a sour…
- Fix: The Google Tag Gateway health check can no longer be answered from a cache. It carried no cache headers at all, and a shop was found serving it from its CDN with a 30 day lifetime, so the check reported the gateway healthy by replaying the last time it had been
- Tweak: The Tag Gateway measurement path field now recommends an unguessable path instead of suggesting /metrics. That is Google’s own example, so a great many shops share one predictable path, which is what makes a blocker rule worth writing against all of them at once
- For the changelog of earlier versions, please refer to the changelog in the /changelog-archive/ folder of the plugin or the full changelog on https://sweetcode.com/docs/pmw/changelog/free
Pixel Manager for WooCommerce 1.68.0
Pixel Manager for WooCommerce 1.67.0
Pixel Manager for WooCommerce 1.66.0
Pixel Manager for WooCommerce 1.65.1
Pixel Manager for WooCommerce 1.65.0
Pixel Manager for WooCommerce 1.64.0
Pixel Manager for WooCommerce 1.63.0
Pixel Manager for WooCommerce 1.61.0
Pixel Manager for WooCommerce 1.60.0
Pixel Manager for WooCommerce 1.59.2
Pixel Manager for WooCommerce 1.59.0
Pixel Manager for WooCommerce 1.58.10
Pixel Manager for WooCommerce 1.58.9
Pixel Manager for WooCommerce 1.58.8
Pixel Manager for WooCommerce 1.58.7
Pixel Manager for WooCommerce 1.58.5
Pixel Manager for WooCommerce 1.58.4
Pixel Manager for WooCommerce 1.58.1
Pixel Manager for WooCommerce 1.58.0
Pixel Manager for WooCommerce 1.57.0
Pixel Manager for WooCommerce 1.56.0
Pixel Manager for WooCommerce 1.55.1
Pixel Manager for WooCommerce 1.55.0
202516 releases
Pixel Manager for WooCommerce 1.54.1
Pixel Manager for WooCommerce 1.54.0
Pixel Manager for WooCommerce 1.53.0
Pixel Manager for WooCommerce 1.52.1
Pixel Manager for WooCommerce 1.52.0
Pixel Manager for WooCommerce 1.51.1
Pixel Manager for WooCommerce 1.51.0
Pixel Manager for WooCommerce 1.50.0
Pixel Manager for WooCommerce 1.49.3
Pixel Manager for WooCommerce 1.49.2
Pixel Manager for WooCommerce 1.49.1
Pixel Manager for WooCommerce 1.49.0
Pixel Manager for WooCommerce 1.48.0
Pixel Manager for WooCommerce 1.47.0
Pixel Manager for WooCommerce 1.46.1
Pixel Manager for WooCommerce 1.46.0
202412 releases
Pixel Manager for WooCommerce 1.45.0
Pixel Manager for WooCommerce 1.44.2
Pixel Manager for WooCommerce 1.44.1
Pixel Manager for WooCommerce 1.44.0
Pixel Manager for WooCommerce 1.43.5
Pixel Manager for WooCommerce 1.42.8
Pixel Manager for WooCommerce 1.41.1
Pixel Manager for WooCommerce 1.40.1
Pixel Manager for WooCommerce 1.39.0
Pixel Manager for WooCommerce 1.38.0
Pixel Manager for WooCommerce 1.37.1
Pixel Manager for WooCommerce 1.36.0
20238 releases
Pixel Manager for WooCommerce 1.35.0
Pixel Manager for WooCommerce 1.34.1
Pixel Manager for WooCommerce 1.33.1
Pixel Manager for WooCommerce 1.32.5
Pixel Manager for WooCommerce 1.31.1
Pixel Manager for WooCommerce 1.30.6
Pixel Manager for WooCommerce 1.29.1
Pixel Manager for WooCommerce 1.28.1
202217 releases
Pixel Manager for WooCommerce 1.27.9
Pixel Manager for WooCommerce 1.26.0
Pixel Manager for WooCommerce 1.25.1
Pixel Manager for WooCommerce 1.24.0
Pixel Manager for WooCommerce 1.23.0
Pixel Manager for WooCommerce 1.22.1
Pixel Manager for WooCommerce 1.21.0
Pixel Manager for WooCommerce 1.20.2
Pixel Manager for WooCommerce 1.19.4
Pixel Manager for WooCommerce 1.18.1
Pixel Manager for WooCommerce 1.17.11
Pixel Manager for WooCommerce 1.16.14
Pixel Manager for WooCommerce 1.15.5
Pixel Manager for WooCommerce 1.15.0
Pixel Manager for WooCommerce 1.14.3
Pixel Manager for WooCommerce 1.13.1
Pixel Manager for WooCommerce 1.12.4
20215 releases
Pixel Manager for WooCommerce 1.11.7
Pixel Manager for WooCommerce 1.10.11
Pixel Manager for WooCommerce 1.9.6
Pixel Manager for WooCommerce 1.8.28
Pixel Manager for WooCommerce 1.7.13
20201 release
Pixel Manager for WooCommerce 1.6.17
20192 releases
Pixel Manager for WooCommerce 1.5.5
Pixel Manager for WooCommerce 1.4.17
20171 release
Pixel Manager for WooCommerce 1.3.6
20162 releases
Pixel Manager for WooCommerce 1.2.2
Pixel Manager for WooCommerce 1.1
20152 releases
Pixel Manager for WooCommerce 1.0.6
Pixel Manager for WooCommerce 0.2.4
20141 release
Pixel Manager for WooCommerce 0.1.9
20131 release
Pixel Manager for WooCommerce 0.1.1
Questions about Pixel Manager for WooCommerce’s releases
What is the latest version of Pixel Manager for WooCommerce?
1.72.0, released on Nov 4, 2026 (6 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.3 or later.
How often is Pixel Manager for WooCommerce updated?
36 releases in the last year, about one every 10 days. Its first release on WordPress.org dates from August 2013.
Know when your rivals ship
Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.
Start freeRelease dates come from the day each version’s folder was made in Pixel Manager for WooCommerce’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.