Conversion Optimization

Varify.io

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 4 dimensions proven

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

by Varify Software GmbH · varify.io

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Growth Lead v1.0 · The E-Commerce Manager v1.0 · The Product Engineer v1.0 · The CRO Consultant v1.0 · The Data Protection Officer v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 5 Oct 2026

Compare with VWO → Report an error on this page Is this your product? →

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

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 Product Engineer

Client-side coverage is solid and documented — visual editor with CSS/HTML/JS, redirect and split-URL tests, multi-page experiments, full-factorial multivariate tests with automatic combination generation, audience targeting and mutual exclusion — but delivery is the snippet-and-editor model throughout. The only server-side mention is a feature-grid entry, and we found no public documentation of server-side SDKs, feature-flag experiments, holdouts or personalisation. 5 6 1 11 13

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 Product Engineer

The method is named with real assumptions — frequentist by default, one-sided chi-square for rates and a one-sided t-test for value metrics, two-sided and Bayesian as account-level Pro options — plus a significance calculator, a Bayesian runtime forecast to 95 % significance, A/A testing, and written guidance to run at least ten days with 500 conversions per variant and to ignore interim significance. We found no public information on sequential testing or other peeking protection, correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction or guardrail metrics that stop a harmful test. 7 8 11

Report an error

Consent & visitor tracking

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.

Report an error

The Product Engineer

The strongest part of the product: variant playout and tracking are separate, the snippet can serve experiments without consent while tracking fires only after consent via Google Consent Mode V1/V2 or a consent tool, assignment lives in localStorage with no cookies, and the vendor publishes its own ePrivacy reasoning that consent-free variant assignment is exempt. Log files are deleted after 14 days and a general deletion policy exists; we found no public information on per-visitor deletion or a written mapping of every mode to consent requirements. 9 10 2 1

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 Product Engineer

They publish an 11.5 KB snippet, recommend head placement, and document the anti-flicker script unusually honestly — a configurable 4-second hide, and a warning that it can hurt Core Web Vitals and SEO. We found no public information on measured load cost or Core Web Vitals impact, an asynchronous loading option, self-hosting or first-party-domain delivery, or an edge or server-side alternative for flicker-sensitive tests. 10 11 12

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 Product Engineer

The BigQuery path is real: automatic setup into the customer's own project, raw line-by-line data with no sampling, events displayed as goals, and exact per-combination numbers for e-commerce multivariate tests, alongside GA4 import, a broad set of analytics and tag-manager integrations, results export and an Experiment API offered as an expert function. We found no public information on the API's limits or versioning or on CDP integration for audiences, and metrics still live in the vendor's reporting rather than being defined once and computed in the warehouse. 14 13 6 8 12

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 Product Engineer

A German GmbH registered in Munich, Frankfurt hosting claimed on the vendor's own pages and a data protection officer via heyData, but the privacy policy names neither the hosting provider nor the subprocessors for the testing product itself, and the website chain includes Cloudflare and HubSpot, both US companies, with transfers relying on Data Privacy Framework certification or standard contractual clauses. The captured pages also name the entity differently — Varify Software GmbH in the imprint, Varify GmbH in the privacy policy, same Grünwald address — and we found no public information on a data processing agreement covering the visitor data the script collects. 3 2 1 10

Report an error

Pricing transparency

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 Product Engineer

Tier prices, annual totals, trial terms and per-tier limits are public — one domain, unlimited subdomains, unlimited traffic, five active experiments on Growth — and the flat rate means the invoice does not depend on traffic estimates. The captured pages give different figures for the entry price — '€119 per month' on the homepage, a starting price of 199 €, and 249 € as the Growth monthly price on the plans page — while AI credits are priced only as 'a monthly credit package or with your own API key', Enterprise services are 'quoted separately', and we found no public information on VAT treatment or minimum term. 4 1 10 6

Report an error

European sovereignty — proven facts

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

Legal entity	Incorporated in DE ⚠ unverified	3/3 pts	3 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	EU only ⚠ unverified	3/3 pts	1 Report an error
Subprocessors	US CLOUD Act reach ⚠ unverified	0/2 pts	2 Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Legal entity. The imprint names "Varify Software GmbH" whereas the privacy policy names the controller "Varify GmbH"; both use the same Grünwald address.
Weak sourcing — Data residency. The residency claim sits in marketing copy on the homepage, and the privacy policy itself does not confirm where product data is stored and even describes transfers of website data to US providers (Cloudflare, HubSpot).
Weak sourcing — Subprocessors. The policy states HubSpot processes this chat data in the EU, but HubSpot, Inc. is US-headquartered; there is no subprocessor list for the hosted testing product itself, whose hosting provider is never named.
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.

15 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
7 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
4 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
4 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
3 subprocessors 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 support 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

Do you know more about Varify.io? Tell us Report an error on this page

Sources (14)

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

1 Vendor homepage varify.io Checked 22 Sep 2026 Details →
2 Privacy policy varify.io Checked 22 Sep 2026 Details →
3 Legal notice varify.io Checked 22 Sep 2026 Details →
4 Pricing page varify.io Checked 30 Sep 2026 Details →
5 Experiment types & delivery — found from sitemap varify.io Checked 1 Oct 2026 Details →
6 Experiment types & delivery — found from sitemap varify.io Checked 1 Oct 2026 Details →
7 Statistical method & guardrails — found from sitemap varify.io Checked 1 Oct 2026 Details →
8 Statistical method & guardrails — found from sitemap varify.io Checked 1 Oct 2026 Details →
9 Consent & visitor tracking — found from sitemap varify.io Checked 1 Oct 2026 Details →
10 Consent & visitor tracking — found from sitemap varify.io Checked 1 Oct 2026 Details →
11 Snippet performance & flicker — found from sitemap varify.io Checked 1 Oct 2026 Details →
12 Snippet performance & flicker — found from sitemap varify.io Checked 1 Oct 2026 Details →
13 Analytics, data export & integrations — found from sitemap varify.io Checked 1 Oct 2026 Details →
14 Analytics, data export & integrations — found from sitemap varify.io Checked 1 Oct 2026 Details →