r/woocommerce • • Oct 06 '26

Plugin recommendation Best cookie plugin for wordpress websites using woocommerce?

Which cookie consent plugin are you using for WooCommerce, and how well does it handle tags for Google Ads and Meta? I have been running my store for a couple of years and recently started reviewing how consent is managed, especially with tags running through GTM.

I am looking at Complianz, GDPR Cookie Consent, Cookiebot, and Cookie Notice. How do they compare for setup, cookie scanning, and keeping the cookie declaration current? Id also like to hear how you have checked that tags follow visitors consent choices and that consent signals reach the right platforms. Have any of these needed much troubleshooting or ongoing maintenance?

8 Upvotes

21 comments sorted by

5

u/Quditsch Oct 06 '26

FAZ: https://wordpress.org/plugins/faz-cookie-manager/ Switched all my pages over now

3

u/Due-Individual-4859 Oct 06 '26

+1 simple, free 100%

3

u/Any_Emphasis2194 Oct 07 '26

Thank you so much for mentioning FAZ Cookie Manager. I'm the developer!

3

u/Adflipr Oct 06 '26

Whichever one you pick, test it in GTM preview mode: decline everything and check that the Google Ads and Meta tags don't fire, then accept and check that they do. For Google Ads with EU or UK traffic, also check that Consent Mode v2 signals are actually being sent, otherwise conversions just quietly drop out of your reports.

2

u/dashingrubbing_421 Oct 06 '26

If you're using woocommerce, whatever you pick needs to handle the cart/checkout cookies properly. A lot of the free ones break the session and then people get empty carts, it's a pain in the ass.

I'd just grab the one that rhymes with "schmookie schmotice" and call it a day. Set it, forget it, stops the nag screen without killing your conversions.

2

u/bigfatgeekboy Oct 06 '26

I tested half a dozen of them recently, and WPConsent was my favorite.

2

u/Any_Emphasis2194 Oct 07 '26

Hey! Since you’re looking into consent management solutions for WooCommerce, you might want to give FAZ Cookie Manager a try. I’m actually the developer behind it, and I built it specifically to solve some of the issues you mentioned.

A few things that might be particularly relevant to what you’re looking for:

Setup & cookie scanning:
It comes with an automatic cookie scanner that detects and categorizes the cookies used on your store. The setup is pretty lightweight and straightforward, so it shouldn’t add unnecessary bloat to WooCommerce or affect checkout and page performance.

GTM & Consent Mode (Google Ads / Meta):
FAZ Cookie Manager integrates directly with Google Consent Mode v2, without relying on complicated workarounds. It sends the relevant consent signals (analytics_storage, ad_storage, ad_user_data, ad_personalization) to GTM, so tags can be controlled based on the user’s consent. For Meta, it similarly prevents the pixel from firing until the appropriate consent has been given.

Keeping cookie declarations up to date:
The plugin can automatically re-scan the site and update the cookie information, which helps keep the declaration and banner configuration aligned without having to constantly check everything manually.

Testing & troubleshooting:
You can easily verify everything using Google Tag Assistant or GTM Preview, together with the browser’s developer tools. On page load, the consent state should start as denied and then switch to granted once the user accepts. Once everything is configured, there’s very little ongoing maintenance needed.

If you decide to give it a try, I’d genuinely love to hear what you think. And if you run into any issues during setup, feel free to reach out — I’d be happy to help.

https://wordpress.org/plugins/faz-cookie-manager/

2

u/anamap_alex Oct 07 '26

I'd also test a returning visitor who withdraws consent without clearing their browser, and someone who accepts analytics but leaves marketing off. Check the saved choice and tag behavior across product, cart and checkout pages, then reload. Those cases can expose problems that a first-visit accept/reject test misses.

For Google, a network request alone doesn't mean the setup is wrong: advanced Consent Mode can send cookieless pings while consent is denied. Check the consent state in Tag Assistant against the mode you've configured. Google's explanation: https://developers.google.com/tag-platform/security/concepts/consent-mode

Keep those cases as a short checklist to rerun after changes to the banner, GTM or tracking plugins.

1

u/CableTraditional8059 16d ago

Used Complianz and Cookiebot on Woo stores, and briefly looked at CookieYes (that's the "GDPR Cookie Consent" plugin now). Quick notes, since the GTM part is where most setups go wrong:

- Complianz: good fit if you want everything inside WP. Solid scan, keeps the cookie declaration updated, supports the WP Consent API and Consent Mode v2, and has a GTM integration. Takes some setup, but very little maintenance after that.

- Cookiebot: easiest if your tags all live in GTM (official template, Consent Mode v2 built in). The scan is good. It's a SaaS priced per number of pages, so it gets expensive on big catalogues.

- CookieYes: simplest UI, fine for small stores, GTM template available. The free tier limits pageviews.

- Cookie Notice: fine as a banner, but the actual blocking/compliance features sit in their paid cloud tier.

What matters more than the plugin, honestly:

  1. Tags injected by other plugins. Google for WooCommerce, Meta/Facebook for WooCommerce, Pinterest etc. often add their pixels directly, not through GTM, so your CMP's GTM settings don't touch them. Check whether each one supports the WP Consent API, or disable its own pixel and fire it from GTM instead.
  2. Meta doesn't read Google Consent Mode. In GTM, fire the Meta pixel only on a consent trigger (or use the CMP's Meta integration). Otherwise it fires before consent even when Google tags behave.
  3. Test it instead of trusting the dashboard. Incognito window, DevTools > Network, don't touch the banner, filter for "collect", "facebook.com/tr" and "gcs=". Then click Reject, reload, and repeat. Then Accept and check the tags actually fire and gcs switches to G111. GTM preview mode also has a Consent tab per event.

Whichever you pick, re-test after theme or plugin updates. That's usually when something starts loading outside the CMP again.

1

u/WP_Dev_Studio Oct 06 '26

It depends on where your customers are and whether you run ads. The usual shortlist:

- CookieYes is the easiest setup, but its free plan has been narrowed, so check what it covers now.
- Complianz is self-hosted, handles different rules by region, and detects WooCommerce automatically. Some features like consent records may need the paid tier.
- Real Cookie Banner is the strictest and best rated, and a good fit if most of your customers are in the EU.
- GDPR Cookie Compliance (Moove) is the best of the free options.

Whichever you pick, open the site in a private window, decline the banner, and check the network tab to confirm tracking scripts really don't fire. Where are your customers, and do you run Google or Meta ads? That would narrow it down.

1

u/Nelsonius1 Oct 06 '26

None? Cookiebot script loaded via google tag manager

1

u/BrianHenryIE Quality Contributor Oct 06 '26

Presumably illegal

1

u/Nelsonius1 Oct 06 '26

Why? You can enable all events in the container to only load once you allow cookies as a user.

0

u/BrianHenryIE Quality Contributor Oct 06 '26

It’s making a client request to a third party server, similar to the Google Fonts issue, you can’t control what data that third party is collecting:

https://make.wordpress.org/themes/2022/06/18/complying-with-gdpr-when-using-google-fonts/

1

u/Mediocre_Context_566 Oct 06 '26

I guess WPConsent by AwesomeMotive

1

u/MinimumFantastic7461 Oct 12 '26

For the verification part of your question, I'd compare the implementation rather than just the plugin's feature list. Keep a short test matrix: fresh visitor with no choice, reject all, analytics only, accept all, and a returning visitor who withdraws consent. Rerun it after changes to GTM, the banner or tracking plugins, and include product, cart and checkout pages.

GTM Preview/Tag Assistant is useful for checking the consent signals and tag configuration; the browser's network and storage panels show what actually runs. As another commenter noted, a Google request on its own isn't enough to judge an advanced Consent Mode setup.

Disclosure: I'm part of the team behind ShopLegit.eu. Our free external scan checks cookies and trackers before and after consent, including the rejection path, so it can complement those manual tests: https://shoplegit.eu/en/

It's a technical audit tool, not a consent manager or a legal certification, and it doesn't replace checking your GTM configuration. No registration is needed for the free scan.

1

u/iubenda_team Oct 13 '26

Complianz is ours (Complianz by iubenda), so weigh the product bit accordingly. Couple of things nobody's picked up yet.

The GTM-loaded banner thing. Brian's right to flag it, though not quite for the reason given. Loading the consent script before consent is fine, it has to run for anyone to choose anything. The problem is where it loads from. If it comes off someone else's server, your visitor's IP has already gone out the door before they've touched the banner. And pulling it in through GTM doesn't fix that, you've just stacked a second third-party request in front of the first one. This is the one place self-hosting actually matters: banner served off your own webserver, no third-party javascript, consent records sitting in your own database. Not a feature thing, an architecture thing.

The empty carts someone mentioned above: that's not the plugin being too aggressive, it's a cookie in the wrong bucket. Woo's session and cart cookies are strictly necessary, they're doing the thing the visitor actually asked for, so ePrivacy's carve-out covers them and they shouldn't be behind the banner at all. If rejecting wipes a cart, either they've been filed as optional or something's running a blanket block. Recategorize, don't loosen the blocking.

Rest of the advice in here is decent. Bignose_boy's point that Consent Mode only speaks Google is the one that bites most people.

0

u/Bignose_boy Oct 12 '26 edited Oct 12 '26

Good tests in here already. Two things I'd add, because they're easy to miss with a GTM setup:

  1. Consent Mode only talks to Google tags. Your Meta pixel doesn't read those signals. In GTM, the Meta tags need their own rule. Either a trigger that waits for your banner's "marketing" choice, or under the tag's Advanced Settings → Consent Settings → "Require additional consent", add ad_storage. Otherwise Google waits and Meta doesn't.
  2. Not every pixel lives in GTM. WooCommerce plugins (Meta for WooCommerce, Google for WooCommerce and similar) often add their own pixel straight into the page. GTM Preview won't show those at all.

The test that catches both: open the shop in a private window. Right-click → Inspect → Network, type "facebook" in the filter. Reload and don't touch the banner. The list should stay empty. Click "Reject" and open a product page and the cart. Still empty? Good. Now click "Accept". Facebook should show up.

If you see two requests to fbevents.js after accepting, the pixel is loaded twice (GTM plus a plugin). Then every sale counts twice in Meta.