whats-best.ai
Search Sign in

Conversion Optimization

Zuko

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–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

Zuko: AI-assisted analysis on whats-best.ai Zuko: AI-assisted analysis on whats-best.ai (dark)

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

Zuko alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Growth Lead

Weighted verdict

Runs the testing programme for a German marketing team and reports uplift to the board. Wants a visual editor the team can use without a developer, targeting that goes beyond the URL, and results she can defend when finance asks where the promised revenue went.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Growth Lead

Panel median The Growth Lead This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Growth Lead
Experiment types & delivery 0.5 of 5 0.5 of 5
Statistical method & guardrails 0.5 of 5 0.5 of 5
Consent & visitor tracking 1 of 5 1 of 5
Snippet performance & flicker 3 of 5 2.5 of 5
Analytics, data export & integrations 3.5 of 5 3.5 of 5
European sovereignty 2 of 5 2 of 5

Experiment types & delivery

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.

Report an error

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

Report an error

Statistical method & guardrails

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.

Report an error

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

Report an error

Snippet performance & flicker

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.

Report an error

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

Report an error

Analytics, data export & integrations

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.

Report an error

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

Report an error

European sovereignty

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.

Report an error

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

Report an error

Pricing transparency not rated — the vendor publishes no price

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.

Report an error

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

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

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

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.

Do you know more about Zuko? Tell us Report an error on this page

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page zuko.io Checked 20 Oct 2026 Details →
  2. 2 Terms of service — found from the homepage www.zuko.io Checked 20 Oct 2026 Details →
  3. 3 Privacy policy — found from the homepage www.zuko.io Checked 20 Oct 2026 Details →
  4. 4 Experiment types & delivery — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
  5. 5 Experiment types & delivery — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
  6. 6 Statistical method & guardrails — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
  7. 7 Consent & visitor tracking — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
  8. 8 Consent & visitor tracking — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
  9. 9 Snippet performance & flicker — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
  10. 10 Analytics, data export & integrations — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →
  11. 11 Analytics, data export & integrations — found from sitemap www.zuko.io Checked 20 Oct 2026 Details →