Works with your stack

Cookie consent for Pixel Manager for WooCommerce

ten pixels, one script

Pixel Manager for WooCommerce adds the Google tag, Meta, Microsoft, TikTok, Pinterest and other pixels to your shop from one script. Cookie Rocks holds that script until the visitor chooses.

By SweetCode · sweetcode.com · WordPress.org

Is this your product? Tell us if anything here is out of date. Write to us

Start your free trial

Get the free audit

Pixel Manager for WooCommerce

WordPress plugin

Tested

Tested version: 1.72.0
How: Tested automatically around each Cookie Rocks version
Last test: 7 November 2026
Latest version: 1.72.0 tested
Active installs: 40,000+

See it on WordPress.org

What Pixel Manager adds to your visitors’ browser

Trackers it loads

Pixel Manager for WooCommerce →Marketing_ga 2 years _ga_* 2 years _gcl_au 90 days _fbp 90 days _fbc 90 days _fbleid 7 days _uetsid 1 day _uetvid 13 months _ttp 13 months _tt_enable_cookie 13 months _pin_unauth 1 year _epik 1 year _scid 13 months _scid_r 13 months _rdt_uuid 90 days __oppref 30 days __obref 1 year __oaiq_consent 30 days _hjSessionUser_* 1 year _hjSession_* 30 minutes

Cookies seen in our test

sbjs_migrationssbjs_current_addsbjs_first_addsbjs_currentsbjs_firstsbjs_udatasbjs_session

Browser storage

_pmw_session_data

What matters for consent with Pixel Manager

One script for every pixel

The free plugin prints the IDs of all your pixels in one inline script and starts them from one local file. There is no separate tag per pixel on the page.

Google and Microsoft start in denied mode

Once its script runs, Pixel Manager starts the Google tag and Microsoft UET with Consent Mode set to denied. The other pixels wait for consent.

It reads WP Consent API

Pixel Manager learns the visitor’s choice through WP Consent API. With that free plugin installed, all its pixels start right after the visitor accepts, without a reload.

What our tests found on Pixel Manager

Set before the choice · Pixel Manager for WooCommerceCookie Rocks lets Pixel Manager follow the choice when it waits itself
Explicit Consent on and both Consent Modes off: Pixel Manager follows the choice itself; otherwise Cookie Rocks holds it and names the setting.
Seen in our tests, 4 November 2026, Pixel Manager for WooCommerce 1.72.0.
Full detail
With the WP Consent API on, Cookie Rocks 2.9.14 no longer holds Pixel Manager for WooCommerce when Explicit Consent is on and its Google and Microsoft UET Consent Modes are off: on an EU site nothing was sent before the choice or after Reject all, and all ten pixels started on Accept all without a reload. With a Consent Mode on, it keeps holding Pixel Manager and the dashboard names the setting to change. On a site that targets only Switzerland, Pixel Manager runs and Google and UET start in denied mode.
Set before the choice · Pixel Manager for WooCommerceWith the WP Consent API on, Cookie Rocks holds Pixel Manager until consent
Nothing before the choice or after a refusal; all ten pixels start at once on Accept all.
Seen in our tests, 4 November 2026, Pixel Manager for WooCommerce 1.71.0.
Full detail
With the WP Consent API on, Cookie Rocks 2.9.12 held Pixel Manager for WooCommerce 1.71.0: before the choice and after Reject all, none of its ten pixels sent anything and no tracking cookie was set, _uetmsdns included. After Accept all, all ten started at once, without a reload.
Set before the choice · Pixel Manager for WooCommercePixel Manager with Explicit Consent and both Consent Modes off waits
Explicit Consent on, both Consent Modes off: nothing before the choice or after a refusal; all ten pixels on Accept all.
Seen in our tests, 4 November 2026, Pixel Manager for WooCommerce 1.72.0.
Full detail
In Pixel Manager for WooCommerce 1.72.0 (free) with Explicit Consent on and its Google Consent Mode and Microsoft UET Consent Mode settings off, nothing was sent and no cookie was set before the choice, with the WP Consent API in opt-in and the plugin not held by the banner. After Reject all nothing was sent; after Accept all its ten pixels started at once, without a reload.
Set before the choice · Pixel Manager for WooCommerceExplicit Consent alone does not stop Pixel Manager's Google and UET
The Consent Mode settings, on by default, start Google and UET before the choice even with Explicit Consent.
Seen in our tests, 4 November 2026, Pixel Manager for WooCommerce 1.72.0.
Full detail
With Explicit Consent on but its Google and Microsoft UET Consent Mode settings left on (the default), Pixel Manager for WooCommerce 1.72.0 still loaded the Google tag and Microsoft UET before the choice, sent a GA4 page view with gcs=G100 and UET hits, and set _uetmsdns with an empty value. The other pixels waited.
Set before the choice · Pixel Manager for WooCommercePixel Manager starts Google and UET before the choice, even with opt-in
Google and UET start with denied signals before the choice (page view, client ID, _uetmsdns empty); the eight other pixels wait.
Seen in our tests, 4 November 2026, Pixel Manager for WooCommerce 1.71.0.
Full detail
With the WP Consent API on, consent type optin and no choice made yet, Pixel Manager for WooCommerce 1.71.0 still loaded the Google tag for GA4 and Google Ads and sent a GA4 page view with gcs=G100, a client ID and the page address. It also loaded Microsoft UET and sent hits with asc=D, and set _uetmsdns with an empty value. Meta, TikTok, Pinterest, Snapchat, Reddit, OpenAI and Hotjar waited. After a refusal nothing more was sent; after an acceptance all ten pixels started without a reload.
Good to knowCookie Rocks reloads the page only on withdrawal or captcha-only consent
- Accepting does not reload: held tools start at once.
- Withdrawing a consent reloads, because a script that has run can only stop that way.
- Allowing only reCAPTCHA or hCaptcha reloads, since a form needs it from page load.
- Tools that read consent on page load get the signal on the same page.
Seen in our tests, 18 October 2026.
Full detail
When a visitor accepts, Cookie Rocks does not reload the page: held tools start at once. The page reloads in two cases only: when the visitor withdraws a consent already given, because a script that has already run can only be stopped by a reload; and when the visitor allows only reCAPTCHA or hCaptcha, which a form needs from page load. Tools that read consent on page load, such as Pixel Manager for WooCommerce without WP Consent API, get the consent signal on the same page instead.

See the 10 other findings

Set before the choice · Pixel Manager for WooCommerceCookie Rocks holds all of Pixel Manager for WooCommerce until marketing consent
In the test, none of its ten pixels loaded before the choice. Allowing Meta Pixel alone loaded none of them, Meta included.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Cookie Rocks holds the script of Pixel Manager for WooCommerce (pmw-public.p1.min.js) and its pmwDataLayer settings under one service, pixel-manager-for-woocommerce, in the marketing category. In the test, nothing from the ten pixels set up in Pixel Manager loaded before the choice, and allowing the Meta Pixel service alone loaded none of them, Meta included.
Depends on a setting · Pixel Manager for WooCommerceCookie Rocks passes the choice to Pixel Manager without a reload
In the test, Accept all started all ten pixels without a reload, with or without the WP Consent API plugin, and again on the next page.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Without the WP Consent API plugin, Cookie Rocks adds a relay to the inline script pmw-js-before that sends its choice to Pixel Manager for WooCommerce through the wp_listen_for_consent_change event. In the test, Accept all started all ten pixels set up in Pixel Manager without a reload, and all ten started again on the next page view. With the WP Consent API plugin installed, the relay was not added and Accept all also started all ten without a reload.
Depends on a setting · Pixel Manager for WooCommerceWithdrawing marketing stops Pixel Manager's pixels at once
Cookie Rocks sent deny right away: Pixel Manager set its consent to false and Google got denied signals. On the next page none of the ten pixels loaded.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
When the visitor withdrew marketing after Accept all, Cookie Rocks sent deny to Pixel Manager for WooCommerce at once: Pixel Manager set its statistics, marketing and preferences consent to false, and Google Consent Mode updates with ad_storage and analytics_storage denied were pushed to dataLayer. On the next page none of the ten pixels loaded.
Depends on a setting · Pixel Manager for WooCommerceStatistics-only consent starts GA4 but keeps Pixel Manager held
The hard-coded GA4 tag loaded without a reload. Pixel Manager stayed held as marketing, so its own GA4 and pixels did not load.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
On a page with Pixel Manager for WooCommerce and a hard-coded GA4 tag, a visitor who saved statistics only got the hard-coded GA4 tag without a reload: gtag.js, a /g/collect hit and the _ga cookies. Pixel Manager stayed held as a marketing service, so its own GA4 and its marketing pixels did not load, and it received statistics allow, marketing deny through the relay.
Set before the choice · Pixel Manager for WooCommerceWithdrawing marketing erases Pixel Manager's cookies on the site
The page reloaded and every first-party cookie of the ten pixels was removed, even on a first visit. Cookies on the providers' own domains are out of reach of a site script.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Withdrawing marketing after Accept all reloaded the page and removed every first-party cookie set by the ten pixels of Pixel Manager for WooCommerce, including _rdt_uuid, __oaiq_consent and __obref, even on the very first page view of a new site. Only the consent cookie of Cookie Rocks stayed on the site; cookies on the providers' own domains are out of reach of a site script.
Depends on a setting · Pixel Manager for WooCommercePixel Manager acts on consent events even without WP Consent API
It keeps its own consent state by category. On a deny for all, it sent Google every storage type denied except security.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Pixel Manager for WooCommerce keeps its consent state in window.pmw.consent (categories statistics, marketing, preferences, necessary) and acts on the wp_listen_for_consent_change event even when the WP Consent API plugin is not installed. On a deny for all three categories, it pushed Google Consent Mode updates with every storage type denied except security_storage.
Set before the choice · Pixel Manager for WooCommercePixel Manager starts Google and Microsoft UET while its own consent is denied
It relies on Consent Mode: hits are sent with denied signals and UET writes the _uetmsdns cookie. Its other pixels wait for its consent state.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Pixel Manager for WooCommerce starts the Google tag (GA4 and Google Ads) and Microsoft UET as soon as its script runs, even while its own marketing and statistics consent is denied. It relies on Consent Mode: the GA4 hit is sent with gcs=G100, the UET hits with asc=D, and UET writes the _uetmsdns cookie. The other pixels (Meta, TikTok, Pinterest, Snapchat, Reddit, OpenAI, Hotjar) wait for its consent state.
Good to know · Pixel Manager for WooCommercePixel Manager for WooCommerce starts all its pixels from two scripts
One inline script holds every pixel ID and one local script loads a part per pixel. In a test, ten pixels started this way, with no separate tag per service.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Pixel Manager for WooCommerce (free) prints one inline script, window.pmwDataLayer, that holds the IDs of every pixel set up in the plugin, and one local script, pmw-public.p1.min.js, that loads a chunk per pixel. In a test with ten pixels set up (GA4, Google Ads, Meta, Microsoft UET, TikTok, Pinterest, Snapchat, Reddit, OpenAI, Hotjar), all ten started from these two scripts. The page has no separate script tag per service.
Good to know · Pixel Manager for WooCommercePixel Manager loads no pixel for automated browsers and known bots
A default headless scan therefore sees none of its pixels, although real visitors get them.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Pixel Manager for WooCommerce loads no browser pixel when navigator.webdriver is true or when the user agent matches its bot list (Googlebot, bingbot and others). An automated scan with a default headless browser therefore sees none of its pixels, although real visitors get them.
Depends on a setting · Pixel Manager for WooCommercePixel Manager for WooCommerce reads consent through WP Consent API
With the WP Consent API plugin, consent started all its pixels without a reload. Without that plugin, only Google and Microsoft UET started; the other pixels stayed off.
Seen in our tests, 18 October 2026, Pixel Manager for WooCommerce 1.70.0.
Full detail
Pixel Manager for WooCommerce reads consent through the WP Consent API (wp_consent_type and the wp_listen_for_consent_change event). With the WP Consent API plugin installed, a consent given on the page started all its pixels without a reload. Without that plugin and with wp_consent_type set to optin, only Google and Microsoft UET started after consent; the other pixels stayed off.

How we test it

Around each version, with its latest release

Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.

Pixel Manager for WooCommerce 1.72.0, tested on 7 November 2026.
The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
Settings of the test: Default settings after activation.
Last run: Pixel Manager for WooCommerce 1.72.0 on 7 November 2026, with WordPress 7.1.4.

Analytics and ad pixels

Other plugins of the same kind.

Meta Pixel for WordPressThe Meta pixel, plus Meta cookies sent from your server.tested 5.2.2Adds: Meta Pixel Meta for WooCommercePixel and server events, with a hold switch for consent.tested 3.7.8 Pixel CaffeineThe Meta pixel on every page, with no consent setting.tested 2.3.3Adds: Meta Pixel TikTok for BusinessThe TikTok pixel held, server events to decide.tested 1.4.3Adds: TikTok Pixel Microsoft ClarityClarity on every page, with no consent signal.tested 0.10.37 HotjarHotjar held until the visitor agrees.tested 1.0.16 HubSpotHubSpot’s loader on every page, consent only in HubSpot.tested 11.3.75 JetpackStats, comments, videos and images from WordPress.com.tested 16.4 Ad pixel pluginsMeta and TikTok pixels, and what your server sends.MatomoStatistics from your own site, consent through Matomo’s API.tested 5.13.1 Koko AnalyticsStatistics on your own site, with a cookie by default.tested 2.5.3 Independent AnalyticsNo cookie, but returning visitors are still recognised.tested 2.16.2 Burst StatisticsWaits for statistics consent when WP Consent API is there.tested 3.7.4 SlimStat AnalyticsNo consent check by default; one setting changes that.tested 6.0.0Adds: Slimstat Analytics Statistics on your own siteStatistics plugins that count on your own server.Plausible AnalyticsStatistics with no cookie, from plausible.io or your own site.tested 2.6.4 Fathom AnalyticsStatistics with no cookie, from cdn.usefathom.com.PixelYourSiteMeta and Google tags, plus first-party cookies of its own.tested 11.4.5Adds: Google Tag Manager, Google Analytics / Google Ads (gtag.js), Meta Pixel WP StatisticsVisitor counts on your own server, without cookies.tested 14.16.18

Every plugin and theme we test →

Questions

Do I need WP Consent API with Pixel Manager?

Yes, if you want every pixel to start on the page where the visitor accepts. Without it, only Google and Microsoft start at once, and the others wait for the next page.

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For Pixel Manager users

Keep your pixels, ask first.

pixels wait

Every feature of the complete plugin for 30 days, no card.

During the trial: everything, including the full settings and the scans
After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
What waits for a key: most settings, updates and support

How the trial works, in detail

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.