Analytics and consent integration · Updated November 15, 2026

CookieYes integration

CookieYes puts a consent banner on your site, scans for cookies and holds tracking scripts until visitors choose. We set it up on WordPress, Webflow, Astro, Next.js or custom software, configure it for Quebec's Law 25 and Google Consent Mode v2, and check that nothing fires before a yes.

Rated 5.0 out of 5,72 Google reviews

CookieYes at a glance

Connects
Banner script, cookie scanner, Google Consent Mode v2, Microsoft Clarity's consent API, and IAB TCF on Pro and up.
WordPress
The official CookieYes plugin, linked to your CookieYes account.
Webflow
Script in site-wide head code on a paid site plan; CookieYes documents no Webflow app.
Astro or Next.js with Sanity
Script first in the shared head; external tags marked with data-cookieyes.
Custom software
The same script, with CookieYes's consent events starting or stopping your own code.
Complexity
Medium. Most of the time goes into sorting every script into a category and testing.
Typical setup
1 to 2 days for a single-language site, 3 to 5 days with French, geo-targeting and Consent Mode testing.

How we connect CookieYes

  • WordPress

    We install the official CookieYes plugin and link it to your account. Auto-blocking catches common third-party scripts; anything it misses gets a Script URL Pattern in Cookie Manager. Optimization plugins that delay or combine scripts can break blocking, so we exclude the CookieYes script from them, as CookieYes documents for NitroPack.

  • Webflow

    CookieYes documents a custom-code install: the script goes in Head Code under site settings, which needs a paid site plan. Webflow's tracking consent API covers only Webflow Analyze and Optimize, so we call it from CookieYes's consent event to keep those in step. For Consent Mode v2, CookieYes documents a Tag Manager template route.

  • Astro or Next.js with Sanity

    The script loads first in the shared layout's head. External tags get data-cookieyes set to their category, such as cookieyes-analytics. Embeds editors add in Sanity, such as video or maps, render only after their category is accepted.

  • Custom software

    Inline scripts don't take the data-cookieyes attribute, so we load them only after the cookieyes_banner_load and cookieyes_consent_update events allow it. Visitors can't switch off the Necessary category, so we put only strictly necessary cookies in it. Scanning pages behind a login is on the Ultimate plan only.

What organizations use CookieYes for

  • An opt-in banner for Quebec

    CookieYes's Law 25 guide uses its GDPR template, which is opt-in: non-essential cookies stay off until the visitor accepts. That fits Law 25's rule, in force since September 22, 2023, that tracking which can identify, locate or profile someone starts switched off. We add a French banner, on Basic plans and up, and have a person check the translation.

  • One banner for the rest of Canada

    PIPEDA allows implied consent only in narrow cases; the privacy commissioners' guidelines expect express consent when collection falls outside what people would reasonably expect, and clear yes and no options. One opt-in banner across Canada is simplest. Geo-targeting, on Pro and Ultimate, can limit it to the regions you choose.

  • Consent Mode v2 and Clarity

    Every CookieYes plan, Free included, sends Consent Mode v2 signals, and as of November 15, 2026 Google's CMP Partner Program lists CookieYes at Gold tier. Once Clarity's Consent Mode is on, CookieYes passes consent to it too. We open Tag Assistant to confirm Google tags hold until CookieYes sends a choice.

What to watch out for

  • The cost to page speed

    The banner script loads first and has to run before the tags it controls. That adds a request and some script work on every page, and the banner itself can shift layout or become the largest element on a phone screen. We measure LCP and CLS with the banner on and off, and style it so it doesn't push content.

  • Pageview limits, priced per domain

    As of November 15, 2026, CookieYes lists Free at 5,000 pageviews a month, Basic at US$10 a month for 100,000, Pro at US$25 for 300,000 and Ultimate at US$55 with no limit, each per domain. Basic and Pro charge US$0.30 per extra 1,000 pageviews. Annual billing charges for ten months.

  • Auto-blocking misses things

    CookieYes says auto-blocking identifies most commonly used third-party scripts, not all of them. A script in the wrong category, or a banner set to the Info consent type, leaves cookies unblocked. We test in a private window with developer tools open before launch and after each new tag.

Questions about CookieYes

Is CookieYes enough for Law 25?

It covers the banner: tracking held until consent, and a way to change that choice later. Law 25 also asks for a person in charge of privacy, a published privacy policy and an assessment before sending personal information outside Quebec. No banner does those.

Does CASL require a cookie banner?

No. CASL covers commercial electronic messages and installing software, and the CRTC treats cookies as consented while a visitor's conduct shows they accept them. A CookieYes banner answers to PIPEDA, Alberta and BC's private-sector privacy acts, and Quebec's Law 25.

Does CookieYes have a PIPEDA template?

As of November 15, 2026, its consent templates are GDPR, US State Laws, and the two combined, with no PIPEDA or Law 25 template by name. CookieYes's own Law 25 guide points to the GDPR template, and we use the same for Canadian sites.

Related integrations

Need a consent banner that works for Quebec?

Send us your site and the tags it runs today. We'll scan it, pick the CookieYes plan your monthly pageviews fit and set up blocking you can test.

Book a call