Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Clerk.io ApS · www.clerk.io

Report an error on this page Is this your product? →

Link to this page

Clerk.io: AI-assisted analysis on whats-best.ai Clerk.io: 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.

Clerk.io at a glance

Vendor
Clerk.io ApS
Headquarters
Not stated on the vendor’s pages as of 17 Nov 2026
Data hosting
In the EU source, captured 17 Nov 2026
Free plan
Not stated on the vendor’s pages as of 17 Nov 2026
Panel verdict
The AI panel rates Clerk.io 2/5, the mean of 6 judges. Clerk.io is a personalisation engine for e-commerce search, recommendations and email content, and the bench scored it highest as a privacy product and lowest as a testing product. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources

Clerk.io alternatives, European ones first →

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

The Product Engineer

Weighted verdict

Ships experiments behind feature flags and would rather not ship a third-party script at all. Wants server-side SDKs for the stack in use, edge delivery, metrics computed in the warehouse the team already trusts, and an API good enough to build internal tooling on.

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

Scored by The Product Engineer

Panel median The Product Engineer 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 Product Engineer
Experiment types & delivery 2 of 5 2 of 5
Statistical method & guardrails 1 of 5 1 of 5
Consent & visitor tracking 3.5 of 5 3 of 5
Analytics, data export & integrations 2 of 5 2 of 5
European sovereignty 3 of 5 2.5 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 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).

3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.

5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.

8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, 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 Product Engineer

Split testing is documented, but only for this vendor's own content blocks: variants are declared in the embed code with a data-split-test attribute, the client script splits visitors evenly across any number of variants, and results are compared by label in the analytics page. That is a client-side A/B mechanism attached to a personalisation engine — we found no public information on multivariate tests, holdouts, mutually exclusive experiment groups, or allocating experiments from a server-side SDK. If I can only test which of the vendor's own recommendation logics wins, I still need a real experimentation platform next to it. 5 7

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 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.

3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.

5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.

8 — Sequential testing or another documented protection against peeking, plus 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 Product Engineer

The documentation says variants are compared by performance in the analytics page, with sales attribution fed by click and order logging, but no statistical method is named in any of the captured pages. We found no public information on significance or probability figures, confidence intervals, sample-size guidance, peeking, multiple-comparison correction or sample ratio mismatch detection. For a team that re-runs the numbers in its own warehouse, nothing here tells me how a winner is decided. 5 6

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, render-blocking snippet stated as the only way to install the product, with no flicker handling.

3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.

5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.

8 — Published performance figures including the 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 Product Engineer not rated — no public information

We found no public information on the client script's weight, loading behaviour, flicker handling or effect on Core Web Vitals. The pages we read covering the script's setup and split rendering say nothing about what it costs the page, so this stays unevidenced rather than judged. 1 6 5

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 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.

3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.

5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.

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 for managing experiments and reading results 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 Product Engineer

There is a real, versioned REST-like API with a published reference — GET, POST, PATCH and DELETE, JSON responses, and documented click, sale and visitor endpoints — and the privacy policy commits to access to processed and unprocessed data with a valid API key. Beyond that the story stops: we found no public information on analytics or tag-manager integrations, visitor-level export to a data warehouse, or webhooks. I could build against this API, but I would be building my own export pipeline from scratch. 8 2 6

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 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.

3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.

5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.

8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement 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 Product Engineer

The trust documentation states all personal data is stored and processed on servers in Germany with a backup in Ireland, that service providers must keep personal data within the EU, and a subprocessor list sits at the trust center with a standard data processing agreement offered. The contracting entity's jurisdiction is not confirmed on the captured pages, snippet-delivery location is not stated, and the privacy policy discloses optional AI features that send message content to OpenAI in the US — so this reaches solid EU-standard processing but not sovereign end to end. 3 2

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 public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.

5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".

8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, 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 Product Engineer not rated — no public information

We found no public information on pricing — no tiers, no traffic metric such as tracked users or impressions, no seats — in the captured pages. A buyer cannot compute any annual cost from what is published, so this is reported as unevidenced rather than scored as a limitation. 1 5 8

Report an error

European sovereignty — proven facts

1 of 6 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.

Hosting location EU only unverified
Why unverified?

The privacy policy (S1) discloses optional AI features that send message content to OpenAI, L.L.C., so some customer data can leave the EU when those features are enabled.

4/4 pts 3 Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Clerk.io

Is Clerk.io European?

Not determined: the vendor’s pages as captured do not say where Clerk.io is based.

Where does Clerk.io store data?

Clerk.io stores customer data in the EU, per the vendor’s page captured 17 Nov 2026.

Does Clerk.io have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

What are the best alternatives to Clerk.io?

As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Webtrends Optimize (3/5) highest among the other 45 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 Varify.io (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: Clerk.io 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.

Sources (9)

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

  1. 1 Vendor page www.clerk.io Checked 17 Nov 2026 Details →
  2. 2 Privacy policy — found from the homepage trust.clerk.io Checked 17 Nov 2026 Details →
  3. 3 Security / trust page — found from the homepage help.clerk.io Checked 17 Nov 2026 Details →
  4. 4 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →
  5. 5 Experiment types & delivery — found from sitemap docs.clerk.io Checked 17 Nov 2026 Details →
  6. 6 Consent & visitor tracking — found from sitemap docs.clerk.io Checked 17 Nov 2026 Details →
  7. 7 Consent & visitor tracking — found from sitemap help.clerk.io Checked 17 Nov 2026 Details →
  8. 8 Analytics, data export & integrations — found from sitemap docs.clerk.io Checked 17 Nov 2026 Details →
  9. 9 Analytics, data export & integrations — found from sitemap www.clerk.io Checked 17 Nov 2026 Details →