CookieYes review

CookieYes is a consent management platform for business websites. It provides customizable cookie banners, cookie blocking tied to consent, website scans, and a centralized consent log. The company describes it as Google-certified and says it supports Google Tag Manager, Consent Mode V2, and IAB TCF v2.4. Those integrations do not remove the need to check that consent signals are configured correctly on your site.

Pricing is per domain. The Free plan costs $0 and covers up to 5,000 pageviews a month, 100 pages per scan, and five scans a month. Basic starts at $10 monthly, or $8.33 per month with annual billing, and raises the limits to 100,000 pageviews and 600 pages per scan. CookieYes lists a 14-day free trial; its pricing page says annual billing includes two months free. The product is aimed at handling consent display and records, not guaranteeing that a site meets every privacy requirement.

The main draw is a usable free entry point and a straightforward set of consent-management basics. For a small site, the free allowance may be enough to scan pages, show a customized banner, and keep consent records without paying upfront. A commenter in a WordPress thread said CookieYes blocked cookies until consent on projects they had implemented; that is a user report, not a guarantee for every setup.

The paid plans scale by traffic and scan needs:

• Basic is $10 monthly or $8.33 per month annually, with unlimited scans, 100,000 monthly pageviews, and 600 pages per scan.
• Pro is $25 monthly or $20.83 annually, with 300,000 pageviews, 4,000 pages per scan, geo-targeting, and monthly scheduled scanning.
• Ultimate is $55 monthly or $45.83 annually, with unlimited pageviews, 8,000 pages per scan, weekly scheduled scanning, and removal of CookieYes branding.

For teams already using Google’s tools, the stated support for Tag Manager and Consent Mode V2 is relevant. A Reddit commenter also reported using CookieYes reliably, though the thread does not establish how it was configured or tested.

The free plan has tight ceilings: 5,000 pageviews a month, 100 pages per scan, and five scans a month. Basic removes the scan limit but caps traffic at 100,000 pageviews and scans at 600 pages. Basic and Pro charge $0.30 per 1,000 pageviews above their limits. If you need more domains, each requires a premium plan, but CookieYes does not publish the additional-domain price. Enterprise pricing is also not published.

Scheduled scans are not included on every paid tier: the pricing details list them monthly on Pro and weekly on Ultimate. Ultimate is the listed tier for unlimited pageviews and removing CookieYes branding. A Reddit commenter reported that multilingual support had moved to a paid plan, but the published pricing details do not specify which plan includes it, so confirm before switching.

One WordPress thread described a sharp GA4 decline after installing CookieYes. Other commenters said consent-based tracking can exclude visitors who reject or ignore the banner; the thread does not establish that CookieYes itself caused the drop. Check analytics behavior and consent signals before treating reporting changes as lost traffic.

CookieYes has a free plan, then paid plans priced per domain. The pricing page lists Basic at $10 per month, or $8.33 per month with annual billing; Pro at $25 monthly, or $20.83 annually; and Ultimate at $55 monthly, or $45.83 annually. Annual billing includes two months free, and the page also lists a 14-day free trial.

The sharpest jump is Basic to Pro: $15 more per month, for a higher scan and pageview allowance, scheduled monthly scans and geo-targeting. Basic allows 100,000 pageviews a month; Pro allows 300,000. Both charge $0.30 per 1,000 pageviews above the limit. Ultimate removes the pageview cap and allows weekly scheduled scans, but costs $30 more monthly than Pro. Free is limited to 5,000 pageviews and five scans per month. Enterprise pricing is not published. Additional domains require a premium plan for each, but the exact price is not listed. The Agency Partner Program advertises discounts up to 50%.

The published materials describe CookieYes’s banner, cookie blocking, scans and consent log, but don’t explain how to migrate an existing banner, import consent records or export data. Treat those as questions to settle before switching: ask CookieYes what transfers, what needs to be configured again, and whether you can export your consent history if you leave. The documented plan limits also matter during a move: scans cover up to 100 pages on Free, 600 on Basic, 4,000 on Pro and 8,000 on Ultimate.

CookieYes supports Google Tag Manager, Consent Mode V2 and IAB TCF v2.4, according to the published feature list. Confirm your current setup can be reproduced before changing CMPs; the materials don’t specify migration steps or integrations beyond those named. They also don’t include Reddit posts, so we can’t substantiate a claim about why users leave. Support quality is flagged as something buyers should verify, not as a documented shortcoming. Data export, cancellation terms and post-cancellation access are not published on the vendor's site.