Fleetorix
Request access

A CookieYes alternative with one flat price for all your domains

Fleetorix is an alternative to CookieYes with one flat monthly price for all your domains, for developers and agencies with several sites. Below, you can see what that saves, what works differently from CookieYes and how to switch.

What do 10 domains cost at CookieYes?

  • CookieYes

    from€90per month, excl. VAT

    10 domains, price per domain

  • Fleetorix Team

    €39per month, excl. VAT

    One flat price, up to 15 domains

  • You save

    at least€51per month, excl. VAT

    With 10 domains at Fleetorix

Prices checked on . CookieYes pricing

Compare with other providers

Price per month, excl. VAT, by number of domains
DomainsFleetorixCookiebotCookieYesConsentStack
5 domains€19 (Starter)from €75from €45from €39*
10 domainsExample€39 (Team)from €150from €90from €100*
25 domains€79 (Fleet)from €375from €225from €166*

Per domain, the cheapest paid plan for a site with fewer than 350 pages and 5,000 visitors a month, billed monthly, excl. VAT.

At ConsentStack, all domains are in one site, which shares the visitors and the settings.

With yearly billing, other providers may be cheaper.

* ConsentStack prices are converted from USD at the ECB rate of 28 September 2026 (1 euro = 1.1403 dollars).

Prices checked on .

How Fleetorix differs from CookieYes

  • One price for all your domains

    At CookieYes, every extra domain needs its own premium plan (CookieYes's pricing page). Fleetorix costs one flat monthly price per plan, for up to 5, 15, or 50 domains.

  • No automatic scanner

    Fleetorix doesn't scan your site and blocks nothing automatically. You mark every script that has to wait for consent yourself. CookieYes blocks third-party scripts automatically by default until the visitor consents (What is automatic script blocking?), and can also block a script by a URL pattern you enter in the dashboard (Prior Consent).

  • Scripts, iframes, images, video and audio

    Fleetorix holds back <script>, <iframe>, <img>, <picture>, <video> and <audio> tags, such as an embedded video, a map or a tracking pixel. Fleetorix can't block a CSS background image or a font.

  • Three cookie categories

    Besides Necessary, Fleetorix has three categories: Functional, Analytics and Marketing. Their names are fixed. CookieYes has four: functional, analytics, performance and advertisement, and you can rename them there (Prior Consent, Edit a Cookie Category).

  • No US opt-out

    Fleetorix asks for consent first (opt-in), as the GDPR requires. An opt-out under the US CCPA isn't included.

  • Consent log kept for 5 years

    Every choice goes into a consent log that you can export as CSV. We keep each consent for 5 years: that's how long the Dutch Data Protection Authority can still fine a violation. You can't change that period. Why 5 years is a reasonable choice: Cookie consent explained.

  • Consent asked again every 12 months

    The banner asks for consent again after 12 months, or sooner if you change the banner's cookie categories. That period is fixed. What regulators say about asking again: Cookie consent explained.

  • Consent Mode without settings

    The Fleetorix tag sets the Google Consent Mode v2 default itself. Whether you use basic or advanced mode is decided only by where you place your Google tag. At CookieYes, you choose the mode with switches in the dashboard. You set the default with the CookieYes CMP tag in Google Tag Manager or with a Consent Mode script of your own. If you choose the script, the order of your scripts also decides the mode (Implementing Google Consent Mode).

Switching from CookieYes

  1. 1. Replace the CookieYes script with the Fleetorix tag

    Remove the CookieYes script (<script src="https://cdn-cookieyes.com/client_data/…/script.js" …>) from your <head>. In its place, put your domain's Fleetorix tag, as high in the <head> as possible and without async or defer. You'll find it on the Installation tab in the dashboard.

    <script src="https://cdn.fleetorix.com/v1/JOUW-DOMAIN-KEY/snippet.js"></script>

    Do you load CookieYes with the CookieYes CMP tag in Google Tag Manager? Then remove that tag from your container.

  2. 2. Remove your own Consent Mode script

    Did you put the script with gtag("consent", "default", …) above your Google tag, as CookieYes's Implementing Google Consent Mode describes? Remove it. The Fleetorix tag sets that default itself: everything denied except security_storage, until the visitor chooses.

  3. 3. Place your Google tag or GTM snippet

    CookieYes's Support GCM and Allow Google tags to fire before consent switches have no counterpart at Fleetorix. How you place the tag decides the mode of Google Consent Mode v2:

    • Want nothing to reach Google before the visitor consents? Then mark the tag as Analytics: basic mode.
    • Relying on the Google tags' built-in consent checks? Then leave the tag as it is, straight after the Fleetorix tag: advanced mode.

    Tags in your container with additional consent settings, such as ad_storage, keep those settings. For functional, analytics and advertisement, Fleetorix sends the same consent types as CookieYes. Triggers on the cookie_consent_update event or on the cookieyes-consent cookie no longer work, because Fleetorix doesn't send that event or set that cookie. Change those triggers and check in GTM's preview mode which tags fire.

  4. 4. Convert your other scripts

    For each script, change data-cookieyes to data-fleetorix-category, as in the table below. Also change src to data-src and add type="text/plain": only then does the script wait for consent. You don't mark necessary scripts at Fleetorix either. The Scripts tab in the dashboard converts a script for you. Paste the original script there, without data-cookieyes.

    Is an inline script inside a listener on cookieyes_consent_update or cookieyes_banner_load? Take it out of that listener and mark it as an ordinary script.

    Do you have scripts blocked by CookieYes's automatic blocking or by a URL pattern in the dashboard? Then those scripts have no markup, and you first mark every script that has to wait for consent.

  5. 5. Check the installation

    Visit your site, make a choice in the banner and check that your scripts only load after that. On the Installation tab in the dashboard, your domain then shows as Seen.

Your CookieYes markup in Fleetorix

CookieYesFleetorixCategory in the banner
data-cookieyes="cookieyes-functional"data-fleetorix-category="functional"Functional
data-cookieyes="cookieyes-analytics"data-fleetorix-category="analytics"Analytics
data-cookieyes="cookieyes-performance"data-fleetorix-category="analytics"

Fleetorix doesn't have a separate category for performance. Analytics is the closest.

Analytics
A script in the advertisement categorydata-fleetorix-category="marketing"Marketing
A script in the uncategorised category

First choose a category for the script, then mark it as above.

–
src="…"data-src="…"

On a script that waits for consent.

–
type="text/javascript"type="text/plain"

Also on a script without a type. Another type, such as module, goes in data-type.

–
asyncasync

Stays.

–
An inline script in a listener on cookieyes_banner_load or cookieyes_consent_update

Take the script out of the listener and mark it as above.

–
A Script URL Pattern in the dashboard

No replacement. Mark the script itself.

–

Frequently asked questions

Ready to switch?

Fleetorix is invitation-only for now. Request access and try Starter free for 30 days on your own domains.

Request access

Fleetorix is not affiliated with CookieYes.