Fleetorix
Request access

A Cookiebot alternative with one flat price for all your domains

Fleetorix is an alternative to Cookiebot with one flat monthly price for all your domains, for developers and agencies with several sites. Below, you can put the price of Cookiebot next to that of Fleetorix, see what works differently and read how to switch, also if you use Cookiebot in Google Tag Manager.

What do 10 domains cost at Cookiebot?

  • Cookiebot

    from€150per 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€111per month, excl. VAT

    With 10 domains at Fleetorix

Prices checked on . Cookiebot 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 Cookiebot

  • One price for all your domains

    Cookiebot charges per domain, based on each domain's number of subpages (Cookiebot's pricing page). Fleetorix costs one flat monthly price per plan, for up to 5, 15, or 50 domains. How many pages a site has makes no difference to the price.

  • No automatic scanner

    Fleetorix doesn't scan your site and blocks nothing automatically. You mark every script that has to wait for consent yourself. Cookiebot can block cookies automatically until the visitor consents (Cookiebot's developer documentation).

  • 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. Cookiebot blocks iframes and images with data-cookieblock-src (Manual cookie blocking).

  • 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.

Switching from Cookiebot

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

    Remove the Cookiebot tag (<script id="Cookiebot" src="https://consent.cookiebot.com/uc.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 Cookiebot with the Cookiebot CMP tag in Google Tag Manager? Then remove that tag from your container.

  2. 2. Remove your own Consent Mode default

    Did you put a script with gtag('consent', 'default', …) above your Google tag, as Cookiebot'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

    Remove data-cookieconsent="ignore" from your Google tag and your GTM snippet. How you then 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. Fleetorix sends the same consent types for the same categories as Cookiebot. Triggers on the cookie_consent_update event no longer fire, because Fleetorix doesn't send that event. Change those triggers and check in GTM's preview mode which tags fire.

  4. 4. Convert your other scripts

    For each script, change data-cookieconsent to data-fleetorix-category and src to data-src, as in the table below. type="text/plain" stays, and 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 the Cookiebot markup.

    Do you use Cookiebot's automatic blocking (data-blockingmode="auto")? Then your 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 Cookiebot markup in Fleetorix

CookiebotFleetorixCategory in the banner
data-cookieconsent="preferences"data-fleetorix-category="functional"Functional
data-cookieconsent="statistics"data-fleetorix-category="analytics"Analytics
data-cookieconsent="marketing"data-fleetorix-category="marketing"Marketing
data-cookieconsent="statistics, marketing"data-fleetorix-category="marketing"

One category per script. Pick the strictest, or split the script.

Marketing
type="text/plain"type="text/plain"

Stays.

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

On a script that waits for consent.

–
data-cookieconsent="ignore"

Remove it. A script without a mark always runs.

–
data-blockingmode="auto"

No replacement. Fleetorix blocks nothing automatically, so first mark every script that has to wait for consent.

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

On an iframe, image, video or audio, with data-fleetorix-category. A srcset or poster becomes data-srcset or data-poster.

–
class="cookieconsent-optin-marketing"

No replacement.

–
Cookiebot.runScripts()

No replacement. Fleetorix has no function for that.

–

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 Cookiebot or Usercentrics.