Tag: plugin review

Posted in Cookie Consent

Termly Review: Features, Pricing, and Whether the Free Version Is Enough for Your WordPress Site

Posted on by Filip Keser

At a Glance

SpecValue
Installs80,000+
Rating3.6★ (204 ratings)
Free tier10,000 banner views/month, 1 policy
Starting price$10/month billed annually (Starter; $14/month billed monthly)
Best forBundled policy generator alongside the consent banner

Short Verdict

Termly is the odd one out in this series in one specific way: it’s not just a consent banner plugin, it’s a front end for Termly’s own hosted legal-document platform. The free plan gets you one attorney-drafted policy, a cookie banner with script auto-blocking, and quarterly cookie scans — but it’s capped at 10,000 monthly banner views, and once you cross that line the banner reportedly stops working rather than just losing features. Paid tiers start at $10/month with annual billing ($14/month if billed monthly) and add more policies, more frequent scans, and (at $15/month with annual billing, $20/month billed monthly, the Pro+ tier) the features ad-heavy sites actually want: Google Consent Mode v2, IAB TCF 2.3, consent logs, and multi-language support. If you want a bundled policy generator alongside your consent banner and your traffic is modest, it’s a reasonable one-stop option. If you just want a consent mechanism and don’t want to hand your compliance stack to an external SaaS account, Complianz or Cookie Compliance’s free tiers give you more room before you have to pay anything.

What Termly Is

Termly’s WordPress plugin is still listed on WordPress.org under its original slug, uk-cookie-consent — the plugin started life as an independent “UK Cookie Consent” tool before Termly acquired it and rebuilt it around its own platform starting with the version 3.0 release. As of this writing it has 80,000+ active installs and a 3.6-star rating across 204 ratings (129 five-star, 66 one-star — a more polarized split than Complianz or Cookie Compliance, worth reading the low-end reviews on WordPress.org before you commit if that gives you pause). It’s on version 3.3.1, requires WordPress 5.2+ and PHP 5.6+, and is tested up to WordPress 6.9.10.

Unlike Complianz and Cookie Compliance, which run their scanning and script-blocking logic locally with an optional external account for extra features, Termly’s plugin is built to connect to a Termly account from the start — you create a free account (in-plugin or on termly.io) and the plugin syncs your banner, policies, and scan results to Termly’s platform. That’s the trade Termly is making: instead of a self-contained WordPress tool, you get a WordPress front end for a broader compliance product that also generates privacy policies, terms and conditions, an EULA, disclaimers, and other legal documents, plus DSAR (data subject access request) intake forms and CCPA/CPRA “Do Not Sell or Share My Personal Information” links. Termly says it covers 26+ data privacy laws across the regions it operates in — GDPR and the ePrivacy Directive (EU), UK GDPR, CCPA/CPRA and other US state laws, PIPEDA (Canada), LGPD (Brazil), POPIA (South Africa), and Switzerland’s FADP among them — and is a Google-certified “Gold Status” Consent Mode partner.

What’s in the Free Version

  • One legal policy (you pick which — typically the cookie policy or privacy policy)
  • A cookie consent banner with automatic script auto-blocking until a visitor consents
  • Quarterly automated cookie scans
  • HTML-embeddable policy documents
  • Support for up to 10,000 monthly banner views

That visitor cap is the defining constraint of the free plan, and it behaves differently from the caps on the other two plugins in this series: Cookie Compliance’s free Connected Mode keeps working past its 1,000-visit cap (you just lose access to certain features), but multiple third-party sources describe Termly’s banner as deactivating once you exceed 10,000 monthly views on the free plan — meaning your site could be serving cookies and running scripts with no consent banner at all until you upgrade or the next billing cycle resets the count. If your traffic is anywhere near that threshold, that’s a compliance risk worth planning around, not just a nice-to-have feature you’re missing.

What’s Behind the Paywall

Termly sells three paid tiers, billed monthly or annually (annual billing runs roughly 25% cheaper than paying month-to-month):

  • Starter — $10/month (annual billing; $14/month if billed monthly): 2 legal policies, 10 policy edits, 50,000 monthly banner views, monthly cookie scans, regulation monitoring with policy update notifications, 5 included user seats, and basic Google Consent Mode support
  • Pro+ — $15/month (annual billing; $20/month if billed monthly), Termly’s most-promoted tier: unlimited legal policies and edits, unlimited banner views, weekly cookie scans, auto-updated policies, the Termly logo removed from your banner, advanced Google Consent Mode v2, IAB TCF 2.3 support, custom banner styling, multi-language support, region-specific consent rules, consent logs, and unlimited users
  • Agency — custom pricing for managing multiple client sites, with bulk discounts and multi-domain management on top of everything in Pro+

In plain terms: Starter mainly buys you headroom (more views, more policies, more edits) rather than new compliance capability. The features that matter most for ad-driven sites — IAB TCF, full Google Consent Mode v2, and a consent audit trail — are Pro+-only, the same pattern we saw with Complianz’s paid tiers, though Termly’s Pro+ price ($15/month billed annually, or $180/year — $20/month if paying monthly) lands well above Complianz’s Personal tier ($59/year) and roughly in the same range as Cookie Compliance’s Professional plan ($14.95/month).

WooCommerce and E-Commerce

Neither Termly’s own WordPress solutions page nor its plugin listing makes any specific claims about WooCommerce integration — no mention of tracking-pixel handling, payment-gateway scripts, or checkout-flow testing the way Complianz’s marketing does. That doesn’t mean it won’t work on a store (the script-blocking mechanism should apply to any script it can detect, and WooCommerce’s own cart/session cookies are functionally necessary and exempt from consent requirements regardless of which plugin you use), but if you’re running WooCommerce and want a vendor that’s explicitly tested and documented that use case, Complianz currently has the more detailed claims here.

Setup and Day-to-Day Use

Termly markets the plugin as installable “in minutes” with “no coding experience needed,” and setup does follow a simpler path than Complianz’s multi-step wizard: install the plugin, create or link a Termly account, and the banner and policy sync from your Termly dashboard. The trade-off shows up in where your data lives — your consent records and policy content are hosted on Termly’s platform rather than your own server, which is a meaningful difference from Complianz (self-hosted) if data residency or platform independence matters to you. Support is available via chat, email, and phone, with Pro+ customers getting sub-24-hour response targets versus roughly 48 hours for free/Starter users. On the negative side, a portion of the plugin’s WordPress.org reviews (66 of 204 ratings are one-star) cite performance issues and objections to the mandatory external account requirement — worth reading a sample of the lower-rated reviews directly before deciding, since that’s a heavier complaint pattern than either Complianz or Cookie Compliance shows.

Pros

Bundles a real legal-document generator (privacy policy, terms, cookie policy, DSAR forms, and more) with the consent banner, so you’re not running a separate tool for policy pages. Google Consent Mode v2 Gold Status partner with IAB TCF 2.3 support on Pro+. Regulation monitoring that flags when a law changes and updates your policies automatically. Simple setup process relative to Complianz’s more technical wizard. Phone support is available, which neither Complianz nor Cookie Compliance offers.

Cons

The free plan’s 10,000-monthly-view cap doesn’t just gate features — the banner reportedly stops functioning past it, per third-party reporting, which is a bigger risk than a feature downgrade if you’re not watching your traffic. Requires creating and maintaining an external Termly account rather than running self-contained on your own server. Lowest average rating of the three plugin deep-dives in this series (3.6★, with a notably higher share of one-star reviews than Complianz or Cookie Compliance). No documented WooCommerce-specific integration. Full IAB TCF and advanced Consent Mode v2 are Pro+-only, same paywall pattern as Complianz’s premium tiers.

Who It’s a Good Fit For

Site owners who want a consent banner and a set of attorney-drafted legal policies from a single vendor, and whose traffic comfortably sits under 10,000 monthly banner views on the free plan (or who are ready to pay for Starter/Pro+ from the start). It’s also worth a look if you specifically want phone support as an option, or you’d rather not manage a separate policy-generator tool alongside your consent plugin.

Who Should Look Elsewhere

If you’re not interested in the bundled policy generator and just want the strongest possible free consent-management mechanism, Complianz’s uncapped free tier or Cookie Compliance’s free Connected Mode (1,000-visit cap, but no hard cutoff behavior reported) both give you more compliance functionality without paying, as covered in our earlier reviews. If keeping consent data and policy content on your own server rather than a third-party SaaS platform matters to you, Complianz is the self-hosted option in this series. And if your traffic is anywhere near or above 10,000 monthly visits, budget for a paid Termly tier from day one rather than relying on the free plan.

Bottom Line

Termly’s real pitch isn’t “free cookie banner” — it’s “cookie banner plus legal document generator from one vendor,” and if that bundle is genuinely useful to you, the $10–$20/month range (depending on tier and whether you pay monthly or annually) is competitive with buying a policy generator and a consent plugin separately. But judged purely as a free WordPress consent tool, it’s the most limited of the three plugins in this series: a hard traffic cap that reportedly disables the banner entirely, a mandatory external account, and the most polarized review record of the group. As with any consent tool, this isn’t a substitute for legal advice about what your specific site is required to do — treat it as a strong option if the bundled policy generator is what you’re actually after, not a default pick for a pure consent-banner need.

Not sure if you need any of these three yet? Run through our consent-management checklist.

Sources

Posted in Cookie Consent

Cookie Compliance Review: Features, Pricing, and Whether the Free Version Is Enough for Your WordPress Site

Posted on by Filip Keser

At a Glance

SpecValue
Installs800,000+
Rating4.8★ (3,025 ratings)
Free tierBanner Only (uncapped) or Connected Mode (1,000 visits/month, 7-day retention)
Starting price$14.95/month (Professional, 1 domain)
Best forSites already using Google Consent Mode v2 or Meta/Microsoft ads

Short Verdict

Cookie Compliance splits into two genuinely different free options plus one paid tier, and that split is most of the story. “Banner Only” mode is free forever, needs no account, and just shows a customizable notice — no automatic script blocking, no consent logging. Switching on “Connected Mode” gets you the real compliance engine — automatic script blocking, Google and Facebook/Microsoft consent-mode signals, a consent audit trail — for free as well, but capped at 1,000 monthly visits and 7 days of consent history. Past that traffic level, or if you need unlimited history, more languages, or coverage across several domains, you’re into the Professional plan starting at $14.95/month. It’s the second-most-installed plugin in our roundup (800,000+ installs, 4.8 stars), and it leans harder into Google/Meta ad-consent signals than into generating legal documents for you — that’s the main trade-off against Complianz’s broader, less ad-tech-specific free tier.

What Cookie Compliance Is

Cookie Compliance for WordPress is built by Hu-manity.co and is still listed under its original WordPress.org slug, cookie-notice, even though the plugin itself was rebranded from “Cookie Notice” to “Cookie Compliance” — worth knowing so you don’t think you’ve landed on the wrong listing. As of this writing it has 800,000+ active installs and a 4.8-star rating across 3,025 reviews (2,851 of them five-star), running version 3.1.14. It requires WordPress 4.9.6 or higher and PHP 7.4 or higher, and the developer lists it as tested up to WordPress 7.0.7.

Unlike Complianz, which is built around a setup wizard that scans your site and auto-generates legal documents, Cookie Compliance is built around two operating modes. “Banner Only” runs entirely inside WordPress with no external account — you get a banner, and that’s it. “Connected Mode” links the plugin to Hu-manity.co’s own web dashboard and unlocks the actual consent-management functionality: script blocking, consent categories, analytics, and integration with ad platforms’ consent signals. The vendor’s own compliance claims cover GDPR, the ePrivacy Directive, PECR (UK), LGPD (Brazil), PIPEDA (Canada), CCPA/CPRA and other US state laws including the VCDPA and Colorado Privacy Act, across what it describes as 100+ jurisdictions.

What’s in the Free Version

This is the part worth reading carefully, because “free” means two different things here:

  • Banner Only (free, no account, no cap): a customizable consent banner, synced with your WordPress Privacy Policy page, WP Consent API integration (so other privacy-aware plugins can read the visitor’s choice), and WPML/Polylang compatibility for multilingual sites. It does not block scripts or store a consent record — it’s a notice, not a consent-management platform.
  • Basic (free, requires a Hu-manity.co account, “Connected Mode”): this is where script blocking and consent logging actually turn on. The published plan includes GDPR/CCPA/ePrivacy/PECR-oriented compliance messaging, a consent analytics dashboard, Google and Facebook consent-mode signals, geolocation-based banner logic, and one additional language beyond your site’s default — but it’s capped at 1,000 visits per month, keeps only 7 days of consent history, and gets “basic” (as opposed to priority) support.

In practice: if your site gets meaningful traffic, the free Connected tier’s 1,000-visit cap is the number that will push you toward a paid plan faster than any feature gate will — that’s a different free-tier constraint than Complianz, which caps nothing on its free plan but locks specific features (Consent Mode v2, IAB TCF) behind payment instead.

What’s Behind the Paywall

The Professional plan starts at $14.95/month for a single domain, billed monthly, with a 17% discount for annual billing (confirmed directly on cookie-compliance.co/pricing as of this writing — an earlier draft of this review carried a lower figure from a different source; the vendor’s own “Save 17%” label on the pricing page is the figure to trust). The pricing page also offers 5-, 10-, and 20-domain license bundles, but the per-domain price for those tiers isn’t published as a flat number on the site — it’s revealed by the domain-count selector at checkout, so if you’re licensing more than one site, get the actual figure there rather than assuming it scales linearly from the single-domain rate.

What Professional actually removes or adds versus Basic: unlimited monthly visits, lifetime consent-record storage (versus 7 days), unlimited additional languages (versus one), and premium support. The core compliance mechanics — script blocking, Google/Facebook consent-mode signals, geolocation — are the same feature set as the free Basic tier; you’re paying to remove caps, not to unlock functionality that free accounts don’t have at all. One notable gap either way: we found no mention of IAB Europe TCF support anywhere on Hu-manity.co’s site or in its Google Consent Mode documentation, on either tier. If IAB TCF certification is a requirement for your ad exchange relationships, Cookie Compliance doesn’t appear to offer it — Complianz does, on its paid tiers.

WooCommerce and E-Commerce

Cookie Compliance doesn’t market a specific WooCommerce integration the way Complianz does. That doesn’t necessarily mean it fails on a WooCommerce store — the script-blocking mechanism in Connected Mode works on any script tag it can detect and categorize, cart/session cookies would still be treated as strictly necessary the same as with any consent tool — but there’s no vendor documentation walking through WooCommerce-specific scripts, tracking pixels, or payment-gateway scripts the way Complianz’s marketing does. If you’re running a store and want that mapped out for you rather than configured by hand, that’s a point in Complianz’s favor.

Setup and Day-to-Day Use

Reviewers on WordPress.org consistently describe the plugin as working “out of the box” with minimal configuration for the basic banner case, which tracks with it being one of the higher-rated tools in this category. The friction shows up around the free/paid boundary rather than around setup difficulty: one recurring complaint in user reviews is that Google Consent Mode v2’s more specific parameters felt gated behind a paid plan even though the vendor’s current pricing page lists “Google & Facebook consent modes” under the free Basic tier too — this is worth testing directly against your own ad setup before assuming full v2 parameter support (ad_storage, analytics_storage, ad_user_data, and ad_personalization) is available for free, since the vendor’s documentation and some user reports don’t fully agree on where that line sits. A smaller, more cosmetic complaint that shows up in reviews is that plugin notifications can clutter the WordPress dashboard.

Pros

A real free tier that includes actual script blocking and consent logging, not just a banner — Basic Connected Mode isn’t a stripped-down trial. Banner Only mode is a genuinely no-strings option if you don’t want to connect to an external account at all. Strong install base and rating (800,000+, 4.8★) means most common issues are well documented. Built-in Google, Facebook, and Microsoft consent-mode signal support without needing a separate integration plugin. WPML and Polylang compatibility out of the box for multilingual sites.

Cons

The free Connected tier’s 1,000-visit-per-month cap is a hard ceiling that most active blogs or stores will hit, at which point you’re evaluating the $14.95/month-and-up Professional plan, not the free plugin. No IAB TCF support that we could find, on any tier — a gap if your ad partners require CMP certification. No published WooCommerce-specific integration documentation. Multi-domain pricing beyond the single-domain monthly rate isn’t published as flat numbers, so budgeting for more than one site takes an extra step at checkout. At least some user reviews report confusion about exactly which Google Consent Mode v2 capabilities are free versus paid.

Who It’s a Good Fit For

Sites already running Google Ads, GA4, or Meta ads that want consent-mode signals handled natively, without paying anything, as long as monthly traffic stays under 1,000 visits or you’re fine paying once it doesn’t. It’s also a reasonable pick if you want the option to start with a zero-commitment, no-account banner (Banner Only) and upgrade to real consent management later without switching plugins.

Who Should Look Elsewhere

If your site already gets more than roughly 1,000 visits a month and you want real script blocking and consent records without paying, Complianz’s uncapped free tier is the better starting point — you’d trade Cookie Compliance’s native ad-platform consent signals for Complianz’s broader auto-generated legal documents and WooCommerce-specific coverage. If IAB TCF certification is a hard requirement, neither tier of Cookie Compliance covers it, so it’s worth checking Complianz’s paid tiers or a TCF-focused tool instead. And if you’re running a store and want a plugin that documents WooCommerce script handling explicitly, Complianz has the more detailed vendor documentation for that use case.

Bottom Line

Cookie Compliance’s real strength is that its free tier isn’t a watered-down demo — Connected Mode gives you actual script blocking, consent logging, and native ad-platform consent signals at no cost, which is more than a lot of “free” tools in this space offer. The catch is a hard 1,000-visit monthly ceiling that will push any moderately active site toward the $14.95/month Professional plan faster than a feature gate would, plus a documentation gap around exactly which Consent Mode v2 features are actually free. As with any consent tool, this isn’t a substitute for legal advice about what your specific site is required to do — treat it as a strong mechanism for enforcing whatever your compliance requirements turn out to be, not a compliance guarantee in itself.

Still deciding if you even need one of these? Run through our consent-management checklist, or read our Termly review for the third option in this series.

Sources

Posted in Cookie Consent

Complianz Review: Features, Pricing, and Whether the Free Version Is Enough for Your WordPress Site

Posted on by Filip Keser

At a Glance

SpecValue
Installs1M+
Rating4.7★ (1,659 ratings)
Free tierNo page-view or session cap; auto cookie scan, script blocking, policy generation
Starting price$59/year (Personal, 1 site)
Best forBroadest free legal coverage without ad-tech extras

Short Verdict

Complianz is the most fully-featured free cookie consent plugin for WordPress, and that’s not really in dispute — no page-view cap, no session limit, and a free tier that covers more privacy frameworks out of the box than most competitors offer even on paid plans. Where it gets more complicated is everything past the free tier: Google Consent Mode v2, IAB TCF support, and consent records are all gated behind a paid license, and some site owners report banner reliability issues and conflicts with caching plugins. If you want broad legal coverage for free and don’t need ad-tech-specific integrations, it’s a strong default choice. If Google Consent Mode v2 or IAB TCF certification is a hard requirement for your ad stack, budget for the Personal plan before you commit.

What Complianz Is

Complianz GDPR/CCPA Cookie Consent Banner is a Google-certified Consent Management Platform (CMP) built specifically for WordPress (a separate Shopify app also exists, but that’s outside the scope of this review). It’s the most-installed cookie consent plugin on WordPress.org, with 1+ million active installs and a 4.7-star rating across 1,659 reviews as of this writing, running on version 7.5.5. It requires WordPress 5.9+ and PHP 7.4+, and the developer lists it as tested up through WordPress 7.1.2.

The pitch is coverage breadth: instead of building a banner and leaving the legal research to you, Complianz runs a setup wizard that scans your site, asks a series of configuration questions about what you use it for (blog, WooCommerce store, membership site, etc.), and then generates region-specific banners and policy documents covering GDPR, the ePrivacy Directive, UK-GDPR, CCPA/CPRA, LGPD (Brazil), POPIA (South Africa), PIPEDA (Canada), and others, in 15+ languages.

What’s in the Free Version

This is where Complianz stands out from most of the field: the free tier isn’t a stripped-down trial, and it isn’t capped by traffic. It includes:

  • The full guided setup wizard, no coding required
  • Automatic cookie scanning (covers up to 50 posts/pages per scan)
  • Script and iframe blocking with placeholders for common third-party embeds — Google Maps, YouTube, Facebook, Instagram, AdSense, HubSpot, reCAPTCHA, X/Twitter, and ActiveCampaign are explicitly supported out of the box
  • Region-specific banners for the EU, UK, US, Australia, South Africa, Brazil, and Canada
  • Auto-generated cookie policy and privacy policy documents from the scan results
  • 250+ pre-built plugin and service integrations
  • Native Gutenberg blocks
  • Basic WooCommerce compatibility (see below)
  • WCAG 2.1 AA and ADA-oriented accessibility features on the banner itself

For a genuinely free tool, that’s a lot of legal surface area covered — this is the main reason it topped the “best for deep legal coverage without a subscription” slot in our plugin roundup.

What’s Behind the Paywall

Complianz sells three annual license tiers, all billed per year with a 30-day money-back guarantee:

  • Personal — $59/year, covers 1 website
  • Professional — $179/year, covers 5 websites (roughly $3/site/month)
  • Agency — $399/year, covers 25 websites and bundles a separate multisite plugin (roughly $1.35/site/month)

Across all three paid tiers, you get: Google Consent Mode v2 integration (Complianz received Google’s official certification for this in July 2024), IAB Europe TCF support with a registered CMP ID (332) — vendor and third-party sources describe this as TCF v2.0 and up, so if a specific TCF version is a hard requirement for your ad partners, confirm current version support directly with Complianz before buying — plus Geo-IP-based banner targeting, Records of Consent (a stored, exportable log of who consented to what and when), A/B testing for banner copy and design, advanced/hybrid site scanning, data-subject-request handling tools, and priority support.

In plain terms: the free version handles the “show a compliant banner and generate the right legal documents” job well. The paid version is really aimed at sites running serious ad tech (Google Consent Mode v2 specifically matters if you’re running Google Ads or GA4 with ad personalization) or sites that need a defensible, exportable consent audit trail — which matters more once your site’s size or ad spend puts it on a regulator’s radar, per the enforcement examples we cover in “Do You Need a Cookie Policy on Your WordPress Site?”

WooCommerce and E-Commerce

Complianz’s own marketing confirms WooCommerce compatibility, specifically around tracking pixels, payment gateway scripts, and marketing scripts commonly used in WooCommerce stores — the plugin can categorize and block these the same way it handles other third-party scripts. It doesn’t interfere with WooCommerce’s own cart/session cookies, which are functionally necessary for checkout and are exempt from consent requirements. If you’re running a store, it’s worth testing the integration against your specific checkout and payment gateway setup rather than assuming full coverage out of the box, since payment providers change their own tracking scripts periodically.

Setup and Day-to-Day Use

The setup wizard is the plugin’s strongest usability feature: it walks through cookie scanning, a short questionnaire about what the site does, banner template selection, Geo-IP activation, legal document generation, and script categorization, and independent reviewers consistently describe it as completable in a single sitting without needing to touch code. Where the friction shows up is afterward — troubleshooting a false-positive script block, resolving a conflict with a caching or page-optimization plugin, or fine-tuning an edge case the wizard didn’t anticipate all require more manual digging than the initial setup suggests. Some site owners report banner display or reliability issues, particularly on sites running aggressive caching setups; if your site uses a caching plugin, test the banner on a fresh, logged-out, cache-cleared page load before you trust the default configuration.

Pros

Free tier with no page-view or session cap, unusual in a market where most competitors gate volume behind a subscription. Broad regulatory coverage (GDPR, CCPA/CPRA, LGPD, POPIA, PIPEDA, and more) generated automatically rather than left to you to research. Consent data and legal documents are hosted on your own server rather than routed through a third-party service. A large, well-reviewed install base (1M+, 4.7★) means most edge cases have already been hit and documented by someone else. 250+ pre-built integrations cut down on manual script categorization.

Cons

Google Consent Mode v2, IAB TCF, Geo-IP targeting, and Records of Consent are all locked to paid tiers — if any of those is a requirement rather than a nice-to-have, the “free plugin” framing doesn’t really apply to your use case. Some users report banner reliability problems and conflicts with caching/optimization plugins that require manual troubleshooting. Support quality on paid tiers is reported as inconsistent by some reviewers, with response-time targets (24 hours weekdays, 48 hours weekends) not always met. It’s WordPress- and Shopify-only, so it’s not a fit if you manage properties on other platforms and want one consent tool across all of them.

Who It’s a Good Fit For

Site owners who want strong, automatically-generated multi-jurisdiction legal coverage without paying anything, and who are comfortable spending 20-30 minutes in a setup wizard rather than dragging a banner into place with a page builder. It’s also a reasonable default for WooCommerce stores that aren’t yet running heavy ad-tech stacks requiring Google Consent Mode v2 or IAB TCF specifically.

Who Should Look Elsewhere

If Google Consent Mode v2 or IAB TCF is a hard requirement for your ad or ad-tech setup right now, you’re effectively evaluating the $59/year Personal plan, not the free plugin — at that point it’s worth comparing against Cookie Compliance (which builds its paid tier specifically around Consent Mode v2 and Meta/Microsoft consent signals) before deciding, which we cover in our next deep-dive review. Sites already fighting caching-plugin conflicts with other tools may also want to budget extra testing time before assuming Complianz will resolve cleanly on the first try.

Bottom Line

For the price of $0, Complianz gives you more genuine legal coverage than most paid competitors offer — that’s the headline, and it’s earned. The catch is that the features ad-driven sites tend to care about most (Consent Mode v2, IAB TCF, consent records) all sit behind a subscription, so “free” and “fully covers my ad stack” aren’t the same claim. As with any consent tool, this isn’t a substitute for legal advice about what your specific site is required to do — treat it as a strong starting point for the mechanics, not a compliance guarantee.

Not sure if your site even needs one of these yet? Run through our consent-management checklist first.

Sources