New

• The new pmw_fire_parent_view_item_on_variable_products filter fires a view_item with the parent product when a variable product page loads. With variations reported separately, no view_item went out at all until the shopper picked a variation, and WooCommerce preselects none by default, so those page views were unreported
• The new pmw_facebook_auto_config filter switches Meta's automatic configuration off per pixel, which stops Meta's automatic event detection, its microdata scraping and its SmartSetup instrumentation. The snippet our troubleshooting page documented for this defined a placeholder fbq and stopped the Meta pixel from loading at all
• OpenAI Advanced Matching now sends the hashed phone number, first and last name plus the billing region and postal code, on the browser pixel and on the Conversions API. Server-side events also carry the browser reference from the SDK's __obref cookie, so a purchase reported from the server is matched to the browser that clicked the ad (Pro)
• The OpenAI pixel and Conversions API report a new customer account as registration_completed, and the Conversions API now sends each order line with its unit price, parent product and chosen variation attributes (Pro)

Improved

• The Meta Event Setup Tool warning and the debug report now name every rule and value extractor by its ID and by the URL it is scoped to. Meta sometimes keeps delivering rules after they were deleted in the Events Manager, and only Meta support can remove those, for which they need those IDs
• The debug report now has a Google Tag Gateway section that counts gateway requests which ended in a WordPress 404 that day, and names the last one. Nothing in the plugin could show that gateway traffic was being dropped, which is what made the resulting server load so hard to trace
• The Pinterest events now use Pinterest's own standard event names throughout. Product views move from PageVisit to ViewContent, and starting a checkout is reported as InitiateCheckout instead of Checkout. Expect reported Pinterest Checkout conversions to drop, because checkout starts were previously counted as completed orders
• The Freemius section of the debug report now states whether the in-dashboard account page exists, why it does not, and which link the plugin hands out in its place. None of that was visible anywhere, so a shop reporting a dead account link could not be diagnosed from a debug report
• The Click ID Capture Quality section of the debug report now counts only the orders created after click ID capture became active on this shop, and states that date. It scanned the newest 250 orders regardless of age, so a shop that had just updated read 0% captured, which is indistinguishable from broken capture (Pro)
• The Meta Conversions API now writes one log entry per purchase and per subscription event, naming the event ID and how many pixels it was sent to. Shops that send directly rather than through the Server-Side Proxy had no way to confirm a server-side send from the log at all (Pro)
• Updated the bundled third-party libraries to their current releases
• The Triple Whale pixel now sends Triple Whale's full checkout funnel (Contact, contactSubmitted, addressSubmitted, shippingSubmitted, paymentSubmitted, Purchase) plus NewSubscription for orders that start a WooCommerce Subscription, and switches the tracking of Triple Whale's own plugin off while it is active, so nothing is reported twice (Pro)

Fixed

• Purchase tracking no longer ends in a fatal error when WooCommerce cannot resolve the order behind an order line item. That broke the checkout response after the payment had already been captured, so those customers read it as a failed payment and ordered again, which charged them twice
• On LiteSpeed Cache the Pixel Manager excludes itself from "Load JS Deferred: Delayed", which held every script back until the visitor clicked or scrolled and lost purchases on the order confirmation page. It also keeps its ?ver cache buster when "Remove Query Strings" is on, so browsers stop replaying a pre-update script that requests chunk files no longer shipped
• The automatic cache purge after a Pixel Manager update now clears NitroPack, Kinsta and Proxy Cache Purge, which failed silently and left those shops serving the previous release's tracking library, so it disabled itself and tracked nothing. A cache that cannot be cleared now raises an admin notice, and a stale library names itself in the console
• pmw.trackCustomFacebookEvent() now honors the visitor's current marketing consent, the same gate every other Meta event passes. It only checked whether the pixel had loaded at some point, so a custom event fired from a shop's own snippet still reached Meta after the visitor withdrew consent in the cookie banner
• A jQuery snippet that fires a Pixel Manager event from a pmwLoad handler no longer sends the page into an endless loop that freezes the browser and floods the server with requests, which our own documented parent view_item snippet did. Legacy jQuery handlers on the lifecycle events also ran twice per page load and now run once
• The deprecated wpmLoad event again reaches listeners that register after the tracking library has loaded. Printing the deprecation warning also switched off the compatibility dispatch, so a snippet registering from _pmwq or from any late-loading script was warned that the event is deprecated and then never called, while identical code running earlier still worked
• Requests to the Google Tag Gateway service worker, which Google's tag registers under the measurement path, are answered by the gateway instead of falling through to a full WordPress 404 page. Every visitor triggered one, which flooded 404 logs and put shops with regular traffic under load they had no way to explain
• The Google Tag Gateway proxy no longer writes several log lines per tracking request at the info level, which grew a normal shop's daily log to several megabytes and buried the entries the logger was turned on to find. That detail is now logged at the debug level; warnings and errors are unchanged

Other

• *Release date – 07.09.2026*

New

• The debug report now states whether Meta's own Conversions API Gateway is connected to the pixel, and which events it mirrors. The Gateway copies every browser event into the server channel from Meta's side, so it explains a server event count of roughly twice the browser one while being invisible in the WordPress plugin list
• Added the Microsoft Advertising Conversions API (Pro): with a token set, all Microsoft Ads events are also sent server-side, including purchases from WooCommerce order hooks. The UET tag and the server events share one event ID so Microsoft deduplicates them, the click ID (msclkid) is attached, and SweetCode Cloud routes them when connected
• Added an experimental server-side Google Ads purchase conversion upload through Google's Data Manager API. It activates automatically when the shop connects its Google account through the setup assistant, uploads into the same conversion action the browser tag fires, and Google deduplicates by transaction ID, so it only adds conversions the tag missed (Pro)
• The server-side Google Analytics refund events can now be modified or blocked through the same payload filters as the purchase event, and the new pmw_google_analytics_refund_tracking filter switches them off altogether, for shops that would rather keep their attribution reports free of the sessionless refund rows than have Google Analytics net the refunds out (Pro)
• The Opportunities tab now flags six more setups a shop is missing: the Pinterest API for Conversions, the Nextdoor Conversion API, Nextdoor and Criteo Advanced Matching, the Triple Whale Orders API, and the Google Analytics 4 Measurement Protocol (Pro)
• The Opportunities tab now flags a Meta pixel that has both the Conversions API Gateway and the Pixel Manager's Conversions API connected to it. Only one of the two is needed, and the Gateway is the one to drop, because it can only mirror events the browser already sent (Pro)

Improved