Script Blockers
Script blockers can cause issues when using the plugin in the back-end. As consequence the settings page can appear broken.
Everyone who is reading this article knows that the plugin's purpose is to track visitors and their actions on a WooCommerce shop. In order to achieve this, the plugin injects tracking pixels provided by popular advertising platforms like Google or Meta (Facebook).
On the other hand, ad and script blockers have emerged due to annoying ads and privacy concerns and user tracking.
Because of the plugin's purpose it was added to some privacy filter lists which are being used by some ad and script blockers.
While this is totally fine for visitors on the front-end of a shop, it can cause issues on the back-end of a shop. The plugin uses a few admin scripts in the back-end in order to make the interface faster and easier to use. But if those scripts are blocked, the interface may appear broken.
The simplest way to fix issues with the plugin in the WooCommerce back-end, caused by script blockers, is to disable the script blocker, or whitelist the shop domain in the script blocker.
We tested the most popular ad and script blockers with the plugin. Most of them work fine with the plugin, but some block the admin scripts. Where possible, we've whitelisted the plugin admin scripts.
| Ad or script blocker | compatible | whitelisted |
|---|---|---|
| Adblock | ✔️ | |
| Adblock Plus | ✔️ | |
| AdBlocker Ultimate | ❌ | |
| AdGuard AdBlocker | ✔️ | |
| Fair AdBlocker | ✔️ | |
| Ghostery | ✔️ | |
| uBlock Origin | ✔️ | ✔️ |
Script blockers in cookie consent plugins
Some cookie consent plugins ship their own script blocker for the front-end of the shop. It scans every page for scripts that look like tracking code and holds them back until the visitor accepts the matching cookie category.
The Pixel Manager doesn't need this. It reads the visitor's choice from the consent plugin and loads each pixel only once its category has been accepted. A second blocker on top can only get in the way.
GDPR Cookie Consent by WebToffee
The script blocker of GDPR Cookie Consent by WebToffee (also known as Cookie Law Info or legacy CookieYes) searches the content of every script on the page for known tracking addresses. Up to version 1.73.0 of the Pixel Manager, the Pixel Manager's configuration script contained the address of Meta's pixel script when the Meta pixel was active. The blocker took the whole configuration for a "Facebook Pixel" and held it back. Without its configuration the Pixel Manager can't start, so no pixel fired at all, Google Analytics included, until the visitor accepted advertising cookies.
How to recognize it:
- Tracking works after accepting all cookies, but nothing is tracked for visitors who decline or only accept analytics cookies.
- The browser console shows
Pixel Manager error: The pmwDataLayer is not defined. - In the page source, the script below
START Pixel Manager for WooCommercestarts with<script type="text/plain" data-cli-class="cli-blocker-script".
How to fix it:
- Update the Pixel Manager to version 1.73.1 or later. Its configuration no longer contains Meta's script address, so the blocker has nothing to match.
- Clear all caches (caching plugin, server cache, CDN).
- Open the shop in a private window, don't answer the cookie banner, and view the page source. The script below
START Pixel Manager for WooCommercemust be a normal<script>withouttype="text/plain".
If the script is still blocked, or you can't update yet, open GDPR Cookie Consent → Script Blocker in the WordPress admin and switch off the entry for the Facebook (Meta) pixel. The Meta pixel stays consent-gated, because the Pixel Manager only loads it after the visitor accepts advertising cookies.
If you use the pmw_facebook_fbevents_script_url filter with an address on Meta's own domain, that address is part of the configuration again and the blocker can match it. Use pmw_facebook_fbevents_script_version to pin a version instead.