Clickio Consent
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Clickio Ltd · clickio.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Clickio Consent at a glance
- Vendor
- Clickio Ltd
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates Clickio Consent 2.5/5, the mean of 6 judges. Clickio Consent is a consent management platform from Clickio Ltd, founded 2015 in London, and the bench's scores cluster tightly: 7-8 on banner and choice, 7-8 on scanning and classification, 6-7 on standards and platforms, 4-5 on prior blocking, 3-4 on consent records, and 1-2 on sovereignty. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Clickio Consent is a consent management platform from Clickio Ltd, founded 2015 in London, and the bench's scores cluster tightly: 7-8 on banner and choice, 7-8 on scanning and classification, 6-7 on standards and platforms, 4-5 on prior blocking, 3-4 on consent records, and 1-2 on sovereignty. It is strongest where consent mechanics meet measurement: an equal-weight decline fixed on every design, per-purpose and per-vendor choices, A/B testing bounded to presentation so every variant still produces a valid TC string, with per-variant consent rates updated daily, and a real-browser scanner that accepts the consent prompt, collects cookies and storage keys, and classifies them against the Open Cookie Database and TCF vendor disclosures. It is weakest on sovereignty: the pages place the company in London, no further sovereignty attributes are on record, and we found no public information on hosting, subprocessors or a published data processing agreement. Prior blocking is documented as category gating rather than pre-consent script blocking. The judges did not meaningfully split. Pricing transparency scores 3; no monetary price appears on the captured pages.
Speaks for it
- A real-browser scanner accepts the consent prompt and classifies cookies and storage keys against a catalog built on the Open Cookie Database and TCF vendor disclosures, listing unknowns for review
- An equal-weight decline, granular per-purpose and per-vendor choices and valid consent records are stated as fixed components of every design
- A/B testing is bounded to presentation, with every variant producing a valid TC string and per-variant consent rates updated daily
- TCF 2.4 validation with Google certification at Gold Tier, and Consent Mode v2 on by default with no per-tag wiring for GA4 and Google Ads
- One installation geo-matches TCF signals for European traffic and GPP signals with GPC handling for US traffic, with plugins for eight named platforms
Held against it
- Sovereignty scored 1 to 2, with the captured pages placing the company in London and no public information on hosting, subprocessors or a data processing agreement
- Consent records are affirmed in TCF and non-TCF modes, with no public information on record contents, retention, storage location or export
- Blocking is documented as category gating, with no public information on automatic blocking of scripts before consent or on a documented check that nothing fires early
- We found no public information on a persistent control for visitors to change an earlier choice, on banner accessibility, or on a stated number of languages
Best for
- You run your site through Google Tag Manager and want GA4 and Google Ads to react to consent with no per-tag wiring
- You serve EU and US visitors from one installation and need TCF and GPP signals geo-matched per visitor
- You want to A/B test banner presentation while every variant keeps producing a valid TC string and a consent record
- You need a scanner that shows what runs after consent and lists unknown items for review instead of silently classifying them
Avoid if
- Your procurement requires an EU-based contracting entity with a documented hosting and subprocessor chain — the captured pages place the founding in London in 2015 and record no further sovereignty attributes
- You rely on automatic blocking of unmodified scripts before the visitor chooses — the documented model is category gating with essential tags left on standard triggers
- You must show a supervisory authority what a consent record contains, how long it is kept and how it exports — the pages affirm records exist but carry no such detail
The scores
| Criterion | Panel median |
|---|---|
| Banner & choice architecture | 3.5 of 5 |
| Prior blocking & script control | 2.5 of 5 |
| Scanning & cookie classification | 4 of 5 |
| Consent records & proof | 2 of 5 |
| Frameworks, signals & platforms | 3.5 of 5 |
| European sovereignty | 0.5 of 5 |
Prior blocking & script control
Show reasoningHide reasoning
How this is scored
What happens before the visitor decides: automatic blocking of scripts, pixels, cookies and embedded content until consent is given, content blockers with placeholders for videos, maps and social embeds, integration with tag managers (Google Tag Manager, Matomo Tag Manager) and server-side tagging, consent passed to forms and plugins, and a documented way for the site owner to check that nothing loads too early.
0 — No blocking of any kind; the product only shows a banner and leaves every script running.
3 — Blocking by hand: the site owner changes script tags or tag-manager triggers using the consent state; automatic blocking, embeds and testing are basic or not described.
5 — Automatic blocking of known scripts and cookies before consent, placeholders for embedded videos and maps, a Google Tag Manager template or integration, and the blocking method documented in the help centre.
8 — Blocking described in depth: an auto-blocking mode and a manual mode with their limits explained, content blockers for named services that the vendor maintains, consent passed to forms, CAPTCHAs and plugins through a JavaScript API or events, server-side tagging supported, and instructions to test in the browser or a tag-manager preview that nothing loads before consent.
10 — Prior blocking the site owner can verify: an automated check or monitor that reports scripts and cookies set before consent on the live site, alerts when a new tracker bypasses the banner, blocking covering local storage, fingerprinting and pixels as well as cookies, and the method published so an auditor can follow it.
The Data Protection Officer
Analytics and marketing categories are gated on consent, orchestration runs off the TC string with attribute-gated scripts, an official Google Tag Manager template fires on the Consent Initialization trigger so tags react without per-tag wiring, and custom tags can be gated on US privacy state. We found no public information on placeholders for embedded videos or maps, consent passed to forms or CAPTCHAs, server-side tagging, or a documented browser check that nothing loads before the click. 4 6 7 8
The Agency Developer
The Google Tag Manager path is what I want for forty client sites: an official template in the community gallery, installation with no site-code changes, Consent Mode v2 on by default so GA4 and Google Ads need no per-tag wiring, plus a dataLayer consent event and a consent data variable for non-TCF vendors and custom purposes. Category gating on decline and tag orchestration with attribute-gated scripts are described. We found no public information on placeholders for embedded videos or maps, on automatic blocking of unmodified scripts, or on a documented way to verify nothing fires before consent. 4 6 7
The Publisher Marketing Lead
Tag orchestration gates analytics and marketing categories on the TC string, an official Google Tag Manager template installs the CMP with no site-code changes, and categories are stated to block correctly when a visitor declines. I found no public information on placeholders for embedded videos or maps, on consent passed to forms or CAPTCHAs, on server-side tagging, or on a way for the site owner to verify that nothing loads before consent. 4 6 7 8
The In-House Lawyer
Blocking is documented as category-level gating — analytics and marketing categories blocked on decline, tag orchestration with attribute-gated scripts following the TC string, and a Google Tag Manager template with Consent Mode reacting without per-tag wiring. We found no public information on automatic blocking of unknown scripts before consent, content blockers with placeholders for videos or maps, server-side tagging, or a documented way to verify on the live site that nothing loads too early. 4 6 7
The WordPress Webmaster
For my WordPress-plus-GTM setup this is workable: an official GTM template fired on the Consent Initialization trigger, Consent Mode v2 on by default so GA4 and Google Ads react with no per-tag wiring, categories gated until a visitor declines, and tag orchestration driving attribute-gated scripts. But I found no public information on placeholders for my YouTube and Maps embeds, on passing consent to forms or CAPTCHAs, or on any documented way to check on the live site that nothing fires before consent. 4 6 7 8
The Skeptic
What is documented is gating and signalling: analytics and marketing categories are gated while essential tags stay on standard triggers, a Google Tag Manager template lets Google tags react to consent with no per-tag wiring, consent is pushed to the dataLayer on load and on every change, and orchestration can gate custom tags on the US privacy state. We found no public information on automatic blocking of scripts before consent, placeholders for videos, maps or social embeds, consent passed to forms or CAPTCHAs, or any documented test that nothing fires before the visitor chooses — the scanner itself accepts the consent prompt and looks at the post-consent state. 4 6 7 8
Scanning & cookie classification
Show reasoningHide reasoning
How this is scored
How the product knows what the site sets: a scanner that crawls the site for cookies, local storage, pixels and third-party requests, scheduled rescans, a maintained database that classifies cookies and services by purpose, provider and lifetime, alerts on new or changed trackers, and a cookie declaration or policy section that updates itself from the scan.
0 — No scanning and no cookie list; every service is entered and described by the site owner from scratch.
3 — A one-off scan or a list of services the site owner fills in, with some predefined templates; scheduled scans, classification and the declaration are basic or not described.
5 — A scanner that finds cookies and third-party services on the site, regular rescans, automatic classification into categories from a vendor database, and a cookie declaration generated from the result and kept on the site.
8 — Scanning described in depth: scheduled scans with a stated depth or page count, scanning behind logins or in different regions, local storage and pixels as well as cookies, a large maintained database of services with purposes, providers and lifetimes, email alerts on new or changed trackers, and the declaration updated automatically in several languages.
10 — The cookie list stays true without manual work: continuous monitoring of the live site with a change history, unknown trackers flagged for review rather than silently classified, the classification sources and update process published, and scan reports exportable for an audit.
The Data Protection Officer
The scanner runs in a real browser, accepts the consent prompt to capture the post-consent state, collects first- and third-party cookies plus local and session storage, and classifies each item against a catalog built on the Open Cookie Database and TCF vendor disclosures, with unknowns listed as unclassified for the owner to resolve. The same data drives the dialog's cookie list so the two never disagree, and scan history is kept; we found no public information on alerts for new or changed trackers, cookie lifetimes, or exportable scan reports. 4 5 6
The Agency Developer
The scanner runs pages in a real browser, accepts the consent prompt first, and collects first- and third-party cookies plus local and session storage, matching each item to a vendor through a catalog built on the Open Cookie Database and TCF vendor disclosures — and unknown items surface as unclassified for review rather than silently categorized, which is what I need when a client adds a tracker on Friday. Page and frequency limits per plan are stated, scan history is kept, missing vendors can be added from the results in one click, and the cookie declaration self-updates in every enabled language. We found no public information on email alerts for new or changed trackers or on exportable scan reports. 5 6
The Publisher Marketing Lead
A real-browser scanner accepts the consent prompt to capture the post-consent picture, covers cookies plus local and session storage, and has stated page and frequency limits per plan. Unknown items are held as unclassified for review rather than silently classified, the catalog sources are named (Open Cookie Database and TCF vendor disclosures), scan history is kept, and a self-updating localised cookie-policy embed keeps the declaration current. I found no public information on email alerts for new trackers or on exporting scan reports for an audit. 5 6
The In-House Lawyer
The scanner opens pages in a real browser, accepts the consent prompt to capture the post-consent state, covers first- and third-party cookies plus local and session storage, and states page counts and scan frequencies per plan; unknown items are listed as unclassified for one-click review rather than silently classified, and the classification sources are named (the Open Cookie Database and TCF vendor disclosures). The declaration embeds itself into the policy page and localizes automatically. We found no public information on email alerts for new or changed trackers or on scan reports exportable for an audit. 4 5 6
The WordPress Webmaster
This is the strongest part: the scanner opens pages in a real browser, accepts the consent prompt first so it sees what runs after consent, collects first- and third-party cookies plus localStorage and sessionStorage, auto-classifies against a catalog built on the Open Cookie Database and TCF vendor disclosures, and lists unknowns for review instead of silently labelling them. Plan limits are concrete (20 pages twice a month on Free up to 5,000 pages on Enterprise), scan history is kept, and the cookie policy embed and the dialog's cookie tab update themselves from the same data in every enabled language; I found no public information on email alerts for new trackers. 4 5 6 7
The Skeptic
Scan depth and frequency are stated per plan in pages and scans, the scanner runs in a real browser, accepts the consent prompt to see what runs after consent, and collects cookies plus local and session storage keys, classified automatically against a catalog whose sources are named — the Open Cookie Database and TCF vendor disclosures — with unknown items listed as unclassified for review, scan history kept, missing vendors addable in one click, and a cookie declaration that updates itself and localises into the enabled consent languages. We found no public information on alerts for new or changed trackers, on pixel or third-party request detection, or on exporting scan reports for an audit. 4 5 6
Consent records & proof
Show reasoningHide reasoning
How this is scored
What the site owner can show afterwards: a record per consent with time, pseudonymous ID, the choices made and the banner version shown, how long records are kept and where, export of the consent log, re-consent when the services or texts change, consent expiry, records available to the visitor (a consent ID), and proof that withdrawal took effect.
0 — No record of consent is kept anywhere; the choice lives only in the visitor's browser.
3 — Consent stored in a cookie with a simple log or counter; per-visitor records, retention, export and banner versions are basic or not described.
5 — A consent log with a record per consent (time, pseudonymous ID, choices), a retention period stated, export of the log as a file, and the banner asking again when the configuration changes.
8 — Proof described in depth: each record tied to the banner version and texts shown, a consent ID the visitor can look up, retention and storage location stated, consent expiry configurable, withdrawal recorded as its own event, cross-domain or cross-device consent recorded consistently, and the log searchable and exportable through an API.
10 — Records built for a dispute: a tamper-evident or audit-proof log, every record reproducible with the exact banner and texts the visitor saw, documentation on how to answer a supervisory authority's request, and the full log exportable in an open format when the customer leaves.
The Data Protection Officer
The pages affirm a consent record is created for every choice, in TCF and non-TCF modes alike, and that re-consent rules are configurable per market. We found no public information on what each record contains, retention, export, a visitor-lookup consent ID, or any tie between a record and the banner version the visitor saw — the exact detail I would need in hand before answering a supervisory authority. 2 3 7
The Agency Developer
A consent record for every choice is affirmed in both TCF and non-TCF modes, held identical across designs and A/B variants, and a Reporting API is listed with Enterprise. We found no public information on retention periods, where records are stored, export of the consent log, banner-version capture, or a consent ID a visitor could look up. 2 3 7
The Publisher Marketing Lead
Records are affirmed as a fixed component of the product, with a consent record every time and in both TCF and non-TCF modes, and re-consent rules configurable per market. But I found no public information on what a record contains, retention, storage location, export of the log, or a consent ID the visitor can look up — the detail an ad-funded publisher would need to answer a supervisory authority. 2 3 7
The In-House Lawyer
Records are affirmed repeatedly — a consent record for every visitor in every variant, valid records as a fixed component across designs, and records also in non-TCF mode — and re-consent rules are configurable per market. But that is where the documentation stops: we found no public information on retention periods, storage location, export of the log, the banner version shown, or a consent ID a visitor could look up, which for a dispute is a log rather than proof. 2 3 7
The WordPress Webmaster
The pages repeatedly promise a valid consent record on every choice, in both TCF and non-TCF modes, and re-consent rules configurable per market, which tells me records exist. But I found no public information on what a record contains (timestamp, pseudonymous ID, banner version), how long records are kept or where, or how I would export them for an authority — a Reporting API appears only as an Enterprise feature. 2 3 7
The Skeptic
Records are asserted repeatedly and consistently: a valid consent record every time alongside the TC string and Consent Mode update, as a fixed component of every design, and in non-TCF mode too; re-consent rules can be set per market. We found no public information on what a record contains, how long it is kept, where it is stored, whether the visitor can look up their consent ID, or how a customer exports the log when they leave. 2 3 7
Frameworks, signals & platforms
Show reasoningHide reasoning
How this is scored
Where the consent goes and where the product runs: the IAB Transparency and Consent Framework (TCF, current version) with a registered CMP ID, Google Consent Mode v2 and Google's CMP certification, Microsoft UET consent mode and other ad-platform signals, the Global Privacy Platform and Global Privacy Control for US laws, plugins and apps for WordPress, Shopify, TYPO3 and other systems, iOS and Android SDKs, connected TV, multi-domain and agency accounts, and an API.
0 — No consent signal is passed on; other tools cannot read the visitor's choice.
3 — Consent readable through a cookie or a JavaScript variable, perhaps one CMS plugin; TCF, Consent Mode, app SDKs and multi-site management are basic or not described.
5 — Google Consent Mode v2 supported with the vendor named as a Google-certified CMP, IAB TCF supported, plugins or integrations for several named CMS and shop systems, a JavaScript API, and several domains manageable from one account.
8 — Signals and platforms described in depth: a registered IAB Europe CMP ID and the current TCF version, Google Consent Mode v2 in basic and advanced mode, Microsoft UET consent mode and other named ad signals, GPP and GPC for US states, iOS and Android SDKs documented, agency or partner accounts managing many client sites, and a REST API for configuration.
10 — One consent across every channel: web, apps and connected TV under one configuration, consent shared across domains and logged-in devices, every signal (TCF, Consent Mode, GPP, ad platforms) documented with its mapping to the banner choices, and configuration exportable or managed as code.
The Data Protection Officer
TCF 2.4 is validated with the standard API surface and Global Vendor List auto-updates, Google certification is claimed at Gold Tier with Consent Mode v2 on by default for new sites, and GPP, GPC and usnat-plus-state handling are documented in depth from a single installation geo-matched per visitor. Plugins cover eight named platforms, In-App SDKs are listed, and a Reporting API ships on Enterprise; we found no public information on a registered CMP ID number, Consent Mode advanced mode, Microsoft UET, or agency accounts. 2 3 4 7 8
The Agency Developer
Signals run deep: TCF 2.4 validated with Google certification at Gold Tier, Consent Mode v2 on by default, and one installation geo-matching TCF for European traffic and GPP with GPC honoring for the US, both surfaced through the standard TCF and GPP JavaScript APIs. Named integrations cover Google Tag Manager, WordPress, Drupal, Wix, Squarespace, Webflow, Shopify and WooCommerce, with in-app SDKs listed as a module — I would ask directly about TYPO3. We found no public information on a registered IAB CMP ID number, Microsoft UET consent mode, basic versus advanced Consent Mode, agency accounts for many client sites, or managing several domains from one account. 3 4 7 8
The Publisher Marketing Lead
TCF 2.4 validated with Google certification at Gold Tier, Consent Mode v2 on by default for GA4 and Google Ads with no per-tag wiring, GPP with an early-stubbed standard API and GPC handling from the same installation, and plugins for WordPress, Shopify, Drupal, Wix, Squarespace, Webflow and WooCommerce — the ad stack is largely covered. I found no public information distinguishing basic from advanced Consent Mode, no Microsoft UET signal, no agency or partner account tier, and the app SDKs are named as a module with no documented sharing of consent between site and app. 3 4 7 8
The In-House Lawyer
TCF 2.4 is validated with Google certification at Gold Tier, Consent Mode v2 is on by default with no per-tag wiring, GPP strings are generated with early __gpp stubbing and GPC handling, and plugins exist for eight named systems including WordPress, Shopify and Google Tag Manager, plus listed in-app SDKs. We found no public information on the registered CMP ID number, Consent Mode basic versus advanced mode, Microsoft UET or other ad-platform signals, documented SDK depth, agency accounts, or a configuration API — the Enterprise plan names only a Reporting API. 3 4 7 8
The WordPress Webmaster
Good coverage for my stack: WordPress sits on the platform list alongside Shopify, Drupal, Wix, Squarespace, Webflow and WooCommerce, the vendor is Google-certified at Gold Tier with Consent Mode v2 on by default, TCF 2.4 is validated with __tcfapi provided, and GPP and GPC for US states run geo-matched from the same installation with automatic regulation-catalog updates. In-App SDKs are listed but not detailed, and I found no public information on Microsoft UET consent mode, the distinction between basic and advanced Consent Mode, or a configuration API. 2 3 4 7 8
The Skeptic
TCF 2.4 validation with Google Gold Tier certification, Consent Mode v2 on by default with no per-tag wiring for GA4 and Google Ads, GPP with the __gpp API stubbed early, GPC detected and honoured, and one installation geo-matching European TCF and US GPP traffic, plus eight named platforms from Google Tag Manager to Shopify and __tcfapi provided for vendor scripts. We found no public information on a registered CMP ID number, Consent Mode in basic and advanced mode, Microsoft UET or other named ad signals, agency or partner accounts, or a configuration API; in-app SDKs appear only as a listed module, and the Reporting API is named only as an Enterprise inclusion. 2 3 4 7 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where the banner script is served from, where consent logs and scan results are stored, and who the subprocessors are (hosting, CDN, geolocation, scanner infrastructure, app SDK telemetry, email and support). Independently sourced by the sovereignty pipeline; a CMP runs on every page of the customer's site and sees every visitor, so the whole chain counts, not only the database. For a plugin that runs on the customer's own server, the vendor's licence, update and scanner services are the chain.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (CDN for the banner script, geolocation, scanner, analytics, support) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, banner script and consent logs served and stored in the EU, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, CDN and every subprocessor, or a self-hosted option that keeps the banner and the logs on the customer's own server; data export and deletion documented, and certifications published with their scope rather than implied.
The Data Protection Officer
The only fact bearing on the chain is the vendor's own page placing the company in London. We found no public information on where the banner script or consent logs are hosted, on subprocessors, or on a data processing agreement among the captured pages — for a tool that renders on every page and sees every visitor, I cannot clear this on the evidence captured. 1
The Agency Developer
The captured pages place the vendor's founding in London in 2015, so the company behind the tool is United Kingdom-based. We found no public information on where the banner script is served from, where consent logs and scan results are stored, the subprocessors involved, or a published data processing agreement — for a CMP that runs on every page of every client site, that is a chain I cannot assess from these pages. 1
The Publisher Marketing Lead
The only fact on record is that the company was founded in 2015 in London, so the contracting entity is UK-based rather than EU-based. Beyond that I found no public information on where the banner script or consent logs are served and stored, which subprocessors are involved, or whether a data processing agreement is published — for a CMP that renders on every page and sees every visitor, that unproven chain is a serious gap. 1
The In-House Lawyer
The vendor's own page places the company in London, and the independently captured sovereignty attributes are empty for this vendor. We found no public information on where the banner script is served from, where consent logs and scan results are stored, the subprocessors in the chain, or a published data processing agreement — for a script that runs on every page and sees every visitor of a German, French and Austrian shop, that gap must be closed before contracting. 1
The WordPress Webmaster
The only chain fact the captured pages give me is the 2015 founding in London, which places the vendor outside the EU. I found no public information on where the banner script is served from, where consent logs and scan results are stored, who the subprocessors are, or a data processing agreement and security certifications — the whole rest of the chain is undocumented from what I can see. 1
The Skeptic
The captured pages place the contracting entity in London — Clickio Ltd, founded 2015 — which sits outside the EU, and the fact set records no sovereignty attributes beyond that. We found no public information on where the banner script is served from, where consent logs and scan results are stored, who the subprocessors are, whether a data processing agreement is published, or any security certification with its scope. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per domain or site licence, the page-view, session or consent limits of each tier and what happens above them, the free tier's limits, which features (TCF, app SDKs, A/B testing, multi-domain, white label) cost extra, agency or reseller terms, minimum term, and setup.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with domains, traffic or features is unclear.
5 — Tiers are public with their price per domain or licence and their main inclusions, but at least one commonly needed piece (traffic overage, extra domains, TCF, app SDKs, agency use) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (per domain, per page view or session band, per site licence), overage and extra domains priced, add-ons listed with prices, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of domains, traffic and apps, with every add-on, setup, support, overage and agency fee and the cancellation and data-return terms published.
The Data Protection Officer
Plan names and their feature boundaries are public — scanner limits run from two scans of twenty pages a month on Free to five thousand pages per scan on Enterprise, TCF sits on every plan, GPP starts on Starter, and A/B testing, the Reporting API and white label sit on Enterprise — but no monetary price appears on any page we read. We found no public information on per-domain or traffic limits, overage charges, minimum term, setup fees, or VAT treatment. 2 3 6 7 8
The Agency Developer
The tier structure is public and fairly granular: scanner page and frequency limits per plan (20 pages twice a month on Free, up to 5,000 pages per scan on Enterprise), GPP from Starter, custom TCF and Google ATP vendor lists from Pro, A/B testing with the Reporting API and white label on Enterprise, TCF signals on every plan and a 14-day free trial for paid plans. We found no public information on prices — no per-domain amounts, minimum term, overage rules or VAT treatment — so I cannot compute an annual cost for a client portfolio from the captured pages. 2 6 7 8
The Publisher Marketing Lead
A free plan and a 14-day trial exist, and the feature-to-plan mapping is unusually detailed: multi-language dialogs, geo settings and GPP from Starter, custom vendor lists from Pro, A/B testing and white label on Enterprise, and scanner page and frequency limits per plan. But I found no public information on any monetary price, per-domain or traffic scaling in money, overage charges, VAT treatment or minimum term, so no annual cost can be computed from the captured pages. 2 3 5 6 7
The In-House Lawyer
Plan gating is unusually clear — scanner page counts and scan frequencies per plan, A/B testing and the Reporting API on Enterprise, custom first-layer texts, multi-language, geo settings and GPP from Starter, TCF signals on every plan, and a 14-day free trial — but we found no public prices at all: no currency figure, no per-domain or traffic-based scaling, no overage, minimum term or setup fees. The real annual cost cannot be computed from the public pages. 2 3 6 7
The WordPress Webmaster
A Free plan and a 14-day trial exist, and the scanner limits per plan are public (20 pages twice a month on Free, 5 scans of up to 100 pages on Starter, up to 5,000 pages on Enterprise), with A/B testing, the Reporting API and white label reserved for Enterprise and geo settings from Starter. But I found no public information on the price in money of any paid plan, so I cannot compute a yearly cost per site from these pages — exactly the call-to-sales situation I wanted to avoid. 2 3 6 7
The Skeptic
A free tier exists with stated limits — up to 20 pages, twice a month — and the feature-to-plan mapping is unusually public: multi-language dialogs, custom first-layer texts, geo settings and GPP from Starter, custom TCF and Google ATP vendor lists on Pro, A/B testing, the Reporting API and white label on Enterprise, with a 14-day free trial on paid plans. We found no public price figures for any plan on the captured pages, so the real annual cost for a given number of domains and traffic cannot be computed. 2 3 6 7 8
Questions about Clickio Consent
Is Clickio Consent European?
Not determined: the vendor’s pages as captured do not say where Clickio Consent is based.
Where does Clickio Consent store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does Clickio Consent have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to Clickio Consent?
As of 19 Nov 2026, the panel rates Uniconsent (3.5/5), Usercentrics CMP (3.5/5) and Didomi (3.5/5) highest among the other 25 Consent Management (CMP) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Usercentrics CMP (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Clickio Consent alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on compliance on the pages we read (clickio.com, clickio.com/consent/ab-testing, clickio.com/consent/customization, clickio.com/consent/integrations/google-tag-manager, clickio.com/consent/cookie-list, clickio.com/consent/cookie-scanner and 2 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 7 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page clickio.com Checked 10 Nov 2026 Details →
- 2 Banner & choice architecture — found from sitemap clickio.com Checked 10 Nov 2026 Details →
- 3 Banner & choice architecture — found from sitemap clickio.com Checked 10 Nov 2026 Details →
- 4 Prior blocking & script control — found from sitemap clickio.com Checked 10 Nov 2026 Details →
- 5 Scanning & cookie classification — found from sitemap clickio.com Checked 10 Nov 2026 Details →
- 6 Scanning & cookie classification — found from sitemap clickio.com Checked 10 Nov 2026 Details →
- 7 Frameworks, signals & platforms — found from sitemap clickio.com Checked 10 Nov 2026 Details →
- 8 Frameworks, signals & platforms — found from sitemap clickio.com Checked 10 Nov 2026 Details →