Conversion Optimization
Zuko
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Zuko Analytics Ltd · zuko.io
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.
Zuko at a glance
- Vendor
- Zuko Analytics Ltd
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Default not stated; pages mention Ireland source, captured 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates Zuko 2/5, the mean of 6 judges. Zuko Analytics, a form analytics and session replay platform operated by Formisimo Ltd, is strongest on measurement: data and integrations scored a uniform 7, with a Sessions API returning raw, unaggregated visitor sessions, and performance impact scored 5-6 on published figures — a 15 kb script with 6 kb transferred from an AWS CDN. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Zuko Analytics, a form analytics and session replay platform operated by Formisimo Ltd, is strongest on measurement: data and integrations scored a uniform 7, with a Sessions API returning raw, unaggregated visitor sessions, and performance impact scored 5-6 on published figures — a 15 kb script with 6 kb transferred from an AWS CDN. It is weakest as an experiment engine: experimentation scope ranged 0-2 because the only documented experiment-related capability is the ABlyft integration, which measures tests delivered by another product, and statistical rigour ranged 0-1, as published benchmark relationships carry named dataset sizes but we found no public information on the method behind them. Consent and tracking scored 2-3: the first-party cookie is documented, but securing consents rests on the client as data controller. Sovereignty scored a uniform 4, pairing AWS hosting in the Republic of Ireland with a contracting entity in England and Wales. Scores sat close together on every criterion, and we found no public information on plan prices.
Speaks for it
- A Sessions API returns raw, unaggregated visitor sessions including custom attributes and events, with Python example code published
- Data export paths include a data warehouse, a dedicated Google Data Studio connector, and Power BI, Domo, Tableau and Segment connectors
- The tracking script is published at 15 kb with 6 kb transferred from an AWS CDN, written in vanilla JavaScript, with self-hosting available
- Data is hosted on AWS in the Republic of Ireland, encrypted with AES-256, with a Data Processing Agreement available
- The cookies statement documents one first-party cookie, zukoVisitorId, stored on the client's own domain holding an anonymised visitor ID
Held against it
- The only experiment-related capability documented is the ABlyft integration, which measures tests delivered by another product
- We found no public information on a statistical method, intervals or sample-size guidance behind the published benchmark relationships
- Securing cookie consents sits with the client as data controller, and we found no public information on what the script does before consent or on consent management platform integrations
- The terms permit subcontractors, and we found no published list of who they are
- The API key is provisioned by contacting support, and we found no public information on API rate limits
Best for
- You need field-level form analytics with raw session data flowing into your own warehouse or BI tools
- You run experiments in ABlyft and want a measurement layer comparing form behaviour across test variants
- You deploy compliance-sensitive tracking and value a documented small first-party script, a self-hosting option, AWS hosting in the Republic of Ireland and an available DPA
- You operate forms on Shopify, Jotform, Hubspot or similar providers and want benchmark context with stated dataset sizes
Avoid if
- You need a single platform that builds and delivers the experiments themselves
- Your test read-outs must rest on documented statistical methods, intervals and sample-size guidance
- You expect the vendor, rather than your own compliance setup as data controller, to carry cookie-consent enforcement
- You require an EU contracting entity or a published subprocessor list as a procurement condition
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 0.5 of 5 |
| Statistical method & guardrails | 0.5 of 5 |
| Consent & visitor tracking | 1 of 5 |
| Snippet performance & flicker | 3 of 5 |
| Analytics, data export & integrations | 3.5 of 5 |
| European sovereignty | 2 of 5 |
Experiment types & delivery
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Simple A/B split of one page element through a visual editor; no server-side option, no targeting beyond URL.
3 — Client-side A/B and split-URL tests with basic audience targeting, and no SDK or server-side delivery.
5 — Client-side and server-side experiments through documented SDKs for common languages, multivariate and multi-page tests, audience targeting on behaviour and attributes, and rule-based personalisation.
8 — Feature-flag-based experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, edge or CDN delivery, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
The captured pages present Zuko as a form analytics and session replay platform rather than a testing tool: the only experiment-related capability documented is a native ABlyft integration that pushes test variants in as custom attributes for comparative reporting. We found no public information on a visual editor, SDKs, server-side or edge delivery, multivariate or multi-page tests, holdouts or personalisation from Zuko itself, so my team would still need a separate testing platform and could use this only as the measurement layer. 4 5 1
The E-Commerce Manager
Zuko does not itself run or deliver experiments — what the captured pages show is measurement of tests run elsewhere, with ABlyft test variants pushed in as custom attributes so form behaviour can be compared between them. We found no public information on a visual editor, server-side SDKs, multivariate or multi-page tests, feature flags, holdouts, or personalisation served from this platform. 4 5
The Product Engineer
The only experimentation capability on the captured pages is a one-click ABlyft integration that pushes test variants into Zuko as custom attributes for comparative form-behaviour reports; we found no public information on native test delivery, an editor, SDKs, feature flags or personalisation from Zuko itself. 4 5
The CRO Consultant
Zuko presents itself as a form analytics and session replay platform, and the only experiment-related capability I can find is a native ABlyft integration that pushes test variants into Zuko as custom attributes for comparative reporting — measurement of someone else's tests, not delivery of its own. We found no public information on a visual editor, server-side SDKs, multivariate or multi-page tests, or personalisation from Zuko itself. 4 5 1
The Data Protection Officer
Zuko is a form analytics and session replay product; the only experimentation capability on its pages is a one-click integration that pushes ABlyft test variants into Zuko as custom attributes for filtering and comparative reports, so what can be tested depends entirely on a third-party tool. We found no public information on any editor, SDK or experiment delivery of its own. Multi-step journeys across URLs and single-page apps are handled by chaining the two tracking codes. 4 5 8
The Skeptic
The captured pages describe a form analytics platform, not an experiment platform: the only experiment-related capability is an ABlyft integration that receives third-party test variants as custom attributes for comparative reporting, with variant delivery handled entirely by the other product. We found no public information on running client-side or server-side tests, audience targeting, holdouts or personalisation from Zuko itself. One point rather than zero because analysing variant behaviour side by side is documented and simple to switch on. 4 5
Statistical method & guardrails
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — A "winner" or "probability to beat" figure with no documented method, no stated sample-size guidance and no warning against stopping early.
3 — The method is named (frequentist or Bayesian) but its assumptions are not documented, and nothing prevents a test from being called while it is still underpowered.
5 — Documented method with confidence or credible intervals, a sample-size or test-duration calculator, and stated guidance on when a result may be read.
8 — Sequential testing or an equivalent documented protection against peeking, correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead
We found no public information on a statistical method for experiments — no named frequentist or Bayesian approach, intervals, sample-size or duration guidance, or any treatment of peeking, multiple comparisons or sample ratio mismatch. The only statistics documented are form benchmarking studies with stated dataset sizes and periods, and correlation findings claimed as significant without a documented method, which I could not defend to finance as a test read-out. 6 9
The E-Commerce Manager
We found no public information on a documented statistical method, sample-size or duration guidance, or any protection against peeking and multiple comparisons — and no winner or probability figure that would need one. The published benchmark research reports averages and correlations across large form datasets, which is useful context for my checkout pages but is not a test-decision procedure. 6 9
The Product Engineer
The benchmarking pages publish dataset periods and scale behind their correlation claims, which is welcome provenance, but we found no public information on any significance-testing method, sample-size guidance, peeking or multiple-comparison handling, or sample ratio checks — claims of a "significant positive relationship" appear without a documented test. 6 9
The CRO Consultant
The benchmarking and form statistics pages publish completion, abandonment and correlation figures ("a significant positive relationship"), but we found no documented inferential method behind them, no confidence or credible intervals, and no sample-size or duration guidance. There is also no mention of sample ratio mismatch detection or guardrail metrics, so nothing here would let me defend a test read-out to a client. 9 6
The Data Protection Officer
The published benchmarking research reports aggregated completion rates and relationships between variables, with dataset sizes and research periods named, but we found no public information on any statistical method for calling a result, sample-size or duration guidance, or protection against reading an underpowered comparison. The claimed relationships are presented without a named method or intervals. 6 9
The Skeptic
The published research states its datasets (739 forms, 93 million views, January 2022 to April 2025) but names no statistical method, attaches no confidence or credible intervals to any published rate, and calls relationships 'significant' without naming the test or any multiple-comparison treatment. We found no public information on sample-size guidance, protections against early stopping or sample ratio checks, and the captured pages describe no method for declaring a winning variant at all. As published, the benchmark numbers read as descriptive marketing — real data, undocumented method. 6 9
Consent & visitor tracking
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — Nothing on the vendor's pages says what the script stores on the device or whether it runs before consent; consent is described as the customer's problem.
3 — Cookies or local storage are listed, and a consent integration is mentioned, but the documentation does not say what the script does before consent is given.
5 — Documented behaviour before and after consent, integration with common consent management platforms, a published list of cookies and storage keys with their lifetime, and IP anonymisation described.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, retention of visitor data stated, and guidance on the legal basis for testing in the EU.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
The cookies statement documents a first-party cookie storing an anonymised visitor ID on the tracked site's own domain, and the vendor states no directly identifiable data is collected — but the terms put securing consent squarely on the client as data controller, and we found no public information on what the script does before consent, any consent management platform integration, or a consent-pending or cookieless mode. Deferred firing of the tracking code is documented as a performance option, not as a consent gate my team could rely on. 7 2 3 8
The E-Commerce Manager
The cookies statement does publish what lands on the device — a first-party cookie on the client's own domain holding an anonymised visitor ID — but the terms put consent squarely on the client as data controller. We found no public information on a consent-pending mode, integration with consent management platforms, the cookie's lifetime, or what the script does before consent is given. 7 2
The Product Engineer
The cookies statement documents a first-party cookie storing an anonymised visitor ID on the client's own domain, and the terms place responsibility for securing cookie consent squarely on the client as data controller; we found no public information on what the script does before consent, a consent-pending mode, or integration with consent management platforms. 7 2 3
The CRO Consultant
The cookies statement is genuinely useful for a DPO conversation: it names the first-party zukoVisitorId cookie, its purpose of storing an anonymised visitor ID, and confirms it sits on the client's domain, while the terms concede the Visitor ID may be classed as PII — but consent is explicitly made the client's responsibility as data controller. We found no public information on what the script does before consent is given, on the cookie's lifetime, or on integration with consent management platforms. 7 3 2
The Data Protection Officer
The cookies statement lists one storage item, a first-party cookie named zukoVisitorId stored on the client's domain with its purpose stated, and the terms place responsibility for securing consent on the client as data controller. We found no public information on whether the tracking codes may run before the consent banner is answered, on any consent-pending mode, on consent management platform integration, or on the cookie's lifetime, though the pages confirm no directly identifiable form content is captured and keypress inputs are anonymised in replay. 7 2 8 3
The Skeptic
The cookies statement is specific about what the script stores — a first-party zukoVisitorId cookie on the client's own domain holding an anonymised visitor ID — and the terms state that keystrokes are recorded without the content users enter. But the terms put securing cookie consents on the client as data controller, and we found no public information on what the script does before consent is given, on a consent-pending mode, or on integrations with consent management platforms; cookie lifetime and IP handling are also unstated. 7 2 3
Snippet performance & flicker
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous snippet with no stated size, no flicker handling and no mention of performance.
3 — An anti-flicker snippet that hides the page until the test loads, with a timeout, and no published figures for script size or load cost.
5 — Script size and loading behaviour documented, asynchronous loading option, flicker handling explained with its trade-off, and CDN delivery of the snippet.
8 — Published performance figures including impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead
We found no published figures for Core Web Vitals impact, no tooling showing what a given configuration costs the page, and no mention of flicker handling — less critical for a measurement script than for a variant-serving snippet, but the gap is there. 3 8
The E-Commerce Manager
Concrete, published figures: the JavaScript is 15 kb with 6 kb transferred, hosted on a global AWS CDN, written in optimised vanilla JavaScript with no third-party libraries, and self-hosting of the tracking code is offered for compliance-sensitive shops. The tracking code need not fire on page load and can be narrowed to the form element, though we found no public information on Core Web Vitals impact or per-project bundles. 3 8
The Product Engineer
Published figures exist — a 15 kb script with 6 kb transferred from an AWS CDN, an option not to fire it on page load, GTM support, and self-hosting of the tracking code for compliance-heavy clients; we found no public information on Core Web Vitals impact, per-project bundles, or a server-side or edge alternative. 3 8
The CRO Consultant
This is the best-evidenced area: the tracking JavaScript is published at 15 kb (6 kb transferred) on a globally available AWS CDN with no third-party libraries, the completion code need not fire on page load, targeting can be narrowed to the form element, and clients may self-host the tracking code on their own infrastructure. We found no published figures on Core Web Vitals impact and no per-project bundling, which caps it below the top band. 3 8
The Data Protection Officer
The script is published as 15 kb in size with 6 kb transferred, delivered from a globally available AWS CDN, written in vanilla JavaScript with no third-party libraries, and clients may self-host the tracking code for additional compliance measures. We found no published figures on the impact on Core Web Vitals, and flicker handling is not addressed on these pages, though an analytics script alters nothing on the page. 3 8
The Skeptic
Published figures are concrete: a 15 kb script with 6 kb transferred, delivered from an AWS CDN, with a documented self-hosting option, the ability to fire the code after page load, and scoping of the code down to the form element. We found no public information on measured impact on Core Web Vitals or on tooling showing what a given configuration costs the page, which is what separates documented figures from a stated commitment. 3 8
Analytics, data export & integrations
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — Results visible in the vendor's dashboard only; no export, no analytics integration, no API.
3 — CSV export of aggregated results and one analytics integration, with no visitor-level data and no documented API.
5 — Integrations with common analytics and tag managers, export of results, and a documented API for managing experiments and reading results.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
Strong on getting data out: a Sessions API documented to return raw, unaggregated visitor sessions including custom attributes and events, with Python example code, data warehouse export, a Segment connector and a dedicated Google Data Studio connector alongside Power BI, Domo and Tableau — the checking-results-in-our-own-data story I need. The gaps are that API limits are not stated, the key is issued only by contacting support, and we found no public information on warehouse-native metric computation. 10 11 8 1
The E-Commerce Manager
The Sessions API extracts raw, unaggregated visitor sessions including custom attributes and events, with a data-warehouse export route, Python example code, a Segment connector, and dedicated connectors for Google Data Studio, Power BI, Domo and Tableau — an experiment result I could check against my own data. We found no public information on stated API limits or metrics defined and computed warehouse-natively. 10 11
The Product Engineer
This is the strong part: a Sessions API delivering raw, unaggregated visitor sessions including custom attributes and events, with Python example code, warehouse export, connectors for Data Studio, Power BI, Domo, Tableau and Segment, and a dedicated Google Data Studio connector; the API key arrives via a support email and we found no public information on API limits or versioning. 10 11 8
The CRO Consultant
Getting data out is a real strength: a Sessions API extracting raw unaggregated visitor sessions including custom attributes and events, Python example code, data warehouse export, BI connections covering Google Data Studio, Power BI, Domo and Tableau, a dedicated Google Data Studio connector with audience segments and custom events, a Segment.io connector route, GTM support, and Shopify, Jotform and Hubspot integrations. We found no stated API rate limits or warehouse-native metric computation on the customer's own data, so it stops just short of the top mark. 10 11 8
The Data Protection Officer
The Sessions API extracts raw, unaggregated visitor sessions including custom attributes and events, with Python example code and an API key issued through support, and data can be exported to a data warehouse or connected to Google Data Studio through a dedicated connector, with Power BI, Domo, Tableau and Segment connectors also documented. Integrations cover common form and checkout providers and Google Tag Manager. We found no public information on API limits, and no warehouse-native computation of the customer's own metrics. 10 11 1 8
The Skeptic
The Sessions API extracts raw, unaggregated visitor sessions including custom attributes and events, with Python example code, a data warehouse export path, and a dedicated Google Data Studio connector alongside Segment, Power BI, Domo and Tableau routes. The gap to the top is that we found no public information on API rate limits, API versioning or warehouse-native metric computation, and the API key is provisioned by contacting support rather than self-service. 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and visitor data leaving the EU without a stated safeguard.
3 — EU data residency offered as an option or an enterprise add-on while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU processing of visitor data as standard and an EU contracting entity, but parts of the chain — CDN, support access, analytics — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure including the delivery of the snippet, EU contracting entity, subprocessor list published, and a DPA covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
Visitor data is hosted on AWS in the Republic of Ireland as standard, with a published DPA, a designated Data Protection Officer and encryption in transit and at rest — a solid base for a German buyer. But the contracting entity is Formisimo Ltd registered in England and Wales under UK GDPR with exclusive jurisdiction there, the CDN is described only as globally available rather than EU-located, and subcontractors are permitted without a published list of who they are. 3 2 11
The E-Commerce Manager
Visitor data is stated to be hosted on AWS in the Republic of Ireland, encrypted with AES-256, covered by a DPA, with the visitor cookie sitting on the client's domain. But the contracting entity is Formisimo Ltd, registered in England and Wales rather than the EU, the snippet comes from a globally available CDN, and we found no public information on a published subprocessor list. 3 2
The Product Engineer
The vendor's own privacy page states hosting on AWS in the EEA (Republic of Ireland) with a DPA and AES-256 encryption, but the contracting entity is Formisimo Ltd in England and Wales — outside the EU — and subcontractors are permitted without a published list; the independently sourced checks returned unknown for residency and subprocessors while the vendor's own pages state EEA hosting. 3 2 10
The CRO Consultant
The privacy overview states all data is hosted on AWS in the Republic of Ireland as standard, but the contracting entity is Formisimo Ltd, registered in England and Wales and operating under UK GDPR with a designated DPO — so EU processing with a non-EU entity. Subcontractors are permitted under confidentiality obligations, yet we found no published list of named subprocessors, and the snippet is served from a globally available CDN whose delivery path beyond Ireland is not specified. 3 2 11
The Data Protection Officer
All data is hosted on Amazon Web Services in the European Economic Area, specifically the Republic of Ireland, which puts visitor data in Europe as standard rather than as an enterprise add-on. The contracting entity is Formisimo Ltd, registered in England and Wales, operating under UK GDPR with English governing law, and while the terms permit subcontractors subject to confidentiality obligations, we found no published subprocessor list; the only named infrastructure is AWS for hosting and delivery. 3 2 11
The Skeptic
Visitor data is documented as hosted on AWS in the Republic of Ireland with AES-256 encryption and a Data Processing Agreement available, and the tracking cookie sits on the client's own domain rather than the vendor's. The contracting entity is Formisimo Ltd, registered in England and Wales under English law — a UK rather than EU entity — and while the terms permit subcontractors, we found no public information on their identities. Snippet delivery is described only as a globally available AWS CDN, with no statement that every delivery point sits in Europe. 3 2 10
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A starting price or a free tier exists, but the traffic metric, the limits and what happens above them are unstated — the invoice is unknowable.
5 — Tier prices public with the traffic metric and its limits defined, but at least one commonly needed piece (server-side SDKs, personalisation, overage) is unpriced or "contact sales".
8 — Every tier priced publicly with the traffic metric defined, limits, overage rates, module prices, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
Public pricing information amounts to a free trial including all features, a free form healthcheck with no credit card required, and monthly-rolling or annual billing; the only billing mechanism visible is a monthly visit allowance that page loads count against. We found no public price figures, tier definitions, visit limits or overage treatment, so a buyer cannot compute the annual cost from public pages alone. 8 6 2
The E-Commerce Manager
No price figures appear on the captured pages at all — only that Zuko is offered as a paid plan billed monthly rolling or annually, with a free trial covering all features and a free form healthcheck. The guides do confirm a monthly visit allowance that loading Zuko counts against, but we found no public information on the allowance limits, tiers, overage or VAT treatment, so my December invoice is not computable from public pages. 2 8 6
The Product Engineer
We found no public tier prices: a paid plan, a free trial including all features and a free form healthcheck without a card are documented, with monthly-rolling or annual billing, but the monthly visit allowance that governs the bill is only referenced in passing and we found no public information on its size, tier limits or overage. 2 8 6
The CRO Consultant
Public pages offer a free trial including all features, a free form healthcheck with no credit card required, and monthly rolling or annual billing, and the traffic metric is a monthly visit allowance that loading Zuko counts against. We found no public information on tier prices, allowance sizes or what happens above the allowance, so I cannot estimate a client's invoice before a sales conversation. 2 8 6
The Data Protection Officer
The pages show a free trial that includes all features, a free form healthcheck without a credit card, and a choice of monthly rolling or annual billing, but we found no public prices for any plan and no definition of the monthly visit allowance that the documentation says loading Zuko counts towards. The annual invoice cannot be computed from the public pages alone. 2 8 6
The Skeptic
We found no public information on what any plan costs: the captured pages describe a paid plan, monthly rolling or annual billing, and a free trial that includes all features, but no price, traffic tier or limit is stated. A monthly visit allowance exists and loading the tracking code counts toward it, yet its size and any overage treatment are unstated, so the invoice is unknowable from public pages. 2 8
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Zuko
Is Zuko European?
Not determined: the vendor’s pages as captured do not say where Zuko is based.
Where does Zuko store data?
The default storage location for customer data is not stated on the vendor’s pages as of 20 Oct 2026. The vendor’s pages mention Ireland as hosting location, per the vendor’s page captured 20 Oct 2026.
Does Zuko have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Zuko?
As of 21 Oct 2026, the panel rates GrowthBook (3.5/5), Convert Experiences (3.5/5) and Webtrends Optimize (3/5) highest among the other 31 Conversion Optimization 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 Webtrends Optimize (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Zuko alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Subprocessors, Legal entity. Not confirmed on the vendor’s own pages as captured.
- 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.
- 11 compliance 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
- 7 pricing 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
- 6 legal 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
- 5 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
- 1 hosting 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
- 1 support 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page zuko.io Checked 20 Oct 2026 Details →
- 2 Terms of service — found from the homepage www.zuko.io Checked 20 Oct 2026 Details →
- 3 Privacy policy — found from the homepage www.zuko.io Checked 20 Oct 2026 Details →
- 4 Experiment types & delivery — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
- 5 Experiment types & delivery — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
- 6 Statistical method & guardrails — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
- 7 Consent & visitor tracking — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
- 8 Consent & visitor tracking — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
- 9 Snippet performance & flicker — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
- 10 Analytics, data export & integrations — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
- 11 Analytics, data export & integrations — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →