Convert Experiences

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by Convert Insights, Inc. · www.convert.com

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

Link to this page

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

Convert Experiences at a glance

Vendor
Convert Insights, Inc.
Headquarters
Incorporated in the United States source, captured 16 Nov 2026
Data hosting
Outside the EU by default; pages mention Germany source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Starting price
“With plans starting at USD $399/month.” (vendor’s words) source, captured 26 Oct 2026
Panel verdict
The AI panel rates Convert Experiences 3.5/5, the mean of 6 judges. Convert Experiences scores 7 for experimentation scope, performance impact and pricing transparency, 7 to 8 for statistical rigour, consent and tracking and data and integrations, and 4 to 5 for sovereignty — the clear low point. how scores are made
As of
Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Convert Experiences alternatives, European ones first →

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

The panel's verdict

Convert Experiences scores 7 for experimentation scope, performance impact and pricing transparency, 7 to 8 for statistical rigour, consent and tracking and data and integrations, and 4 to 5 for sovereignty — the clear low point. The strengths are concrete: Frequentist, Bayesian and sequential testing engines named and academically cited, an always-on sample ratio mismatch check that blocks decisions while flagged, consent modes that hold back cookie writing or the experiment itself until the visitor consents, a published snippet weight of 93 KB gzipped, and tier prices with defined overuse rates. The weakness is the chain end to end: visitor tracking data stays on servers in Frankfurt, Germany and "does not leave Europe", but the contract is with Convert Insights Inc. of Delaware, customer account data is stored in the US under the Data Privacy Framework, and we found no public information on a published subprocessor list. The judges did not materially split; the one wrinkle noted is that the captured pages give different figures for the frequentist test statistic.

Report an error

Speaks for it

  • Published tier prices — Growth $399/mo monthly or $299/mo paid annually, Pro $599/mo or $420/mo — with overuse rates of $399 per 100K and $699 per 250K that can be turned off
  • Sequential testing named and grounded in published academic work, with an always-on sample ratio mismatch check that blocks decisions while flagged
  • Cookie writing or the experiment itself can be held back until the visitor consents, with first-party-only cookies, a six-month lifetime and no IP addresses stored for identity
  • Visitor tracking data stays in Europe on German servers in Frankfurt on all plans, with a free signed data processing agreement offered
  • Snippet weight is published at 93 KB gzipped with loading modes whose trade-offs are stated, including the Core Web Vitals cost of the default sync mode

Report an error

Held against it

  • The contract is with Convert Insights Inc., a Delaware company under Delaware law, and customer account data is stored in the US under the Data Privacy Framework
  • We found no public information on a published subprocessor list with locations, including for the Akamai CDN that delivers the script
  • We found no public information on mutually exclusive experiment groups, holdouts, or personalisation tested against a control
  • We found no public information on CUPED-style variance reduction or guardrail metrics that stop a harmful test
  • Enterprise is price on request only and available solely as an annual plan, and seat counts are not published

Report an error

Best for

  • You need visitor experiment data processed in Europe — the captured pages state it stays on German servers in Frankfurt and does not leave Europe, on all plans
  • You must defend a test result to finance or a client — three named statistical engines, a written stop rule and a sample ratio mismatch check that blocks decisions give the reporting spine
  • Your team wants to cross-check winners in its own data — the GA4 integration pushes experiment and variation IDs straight into GA4 ready for BigQuery export
  • You want predictable published pricing — two tiers priced monthly and annually on a defined monthly tested users metric, with overuse rates that can be turned off

Report an error

Avoid if

  • You need a European setup end to end — the contract is with Convert Insights Inc., a Delaware entity under Delaware law, and your customer account data is stored in the US
  • Your team must re-analyse results at the individual-visitor level — the vendor states individual visitors are not stored, and data-subject erasure is limited to cookie deletion
  • You must price the top tier before procurement — Enterprise is price on request only and available solely as an annual plan

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Experiment types & delivery 3.5 of 5
Statistical method & guardrails 3.5 of 5
Consent & visitor tracking 3.5 of 5
Snippet performance & flicker 3.5 of 5
Analytics, data export & integrations 3.5 of 5
European sovereignty 2.5 of 5
Pricing transparency 3.5 of 5

Experiment types & delivery

Show 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 — 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 Growth Lead

The captured pages show A/B, split-URL, multivariate and multi-page tests built end-to-end in a no-code Visual Editor, targeting far beyond the URL with 40+ filters including traffic source, behaviour and weather, plus server-side and feature-flag testing through six named SDKs, bandit auto-allocation, 1:1 personalisation and even edge decisions via Cloudflare Workers. That is almost everything my team needs without a developer; I found no public information on mutually exclusive experiment groups or holdouts, which is what I would want before running an overlapping programme at volume. 6 1 1 2 6 12

Report an error

The E-Commerce Manager

A/B, split URL, multi-page, multivariate in a visual editor, server-side experiments through six named SDKs (JavaScript, PHP, Python, Ruby, iOS, Android), feature flags and rollouts, a multi-armed bandit, Shopify price testing and an edge path via Cloudflare Workers — that is the full menu a shop like mine needs. We found no public information on holdouts or mutually exclusive experiment groups, and while 1:1 personalisation is listed among the test types, the captured pages do not show it being tested against a control, which is how I would want to buy it. 1 12 2 1 7

Report an error

The Product Engineer

A/B, split-URL, full-factorial multivariate and multi-page tests run from a visual editor, server-side experiments ship through six SDKs (JavaScript/Node, PHP, Python, Ruby, iOS, Android) with feature flags and rollouts, and there is a Cloudflare Workers path where the variation decision happens at the edge before the page reaches the browser. What keeps me below the top level is that I found no public information on mutually exclusive experiment groups, holdouts, or personalisation that can itself be tested against a control — the governance layer I need before betting a release programme on it. 12 1 7 2

Report an error

The CRO Consultant

A/B, split-URL, multivariate and multi-page tests run through a visual editor, with server-side experimentation and feature flags documented across six SDKs (JavaScript, Python, PHP, Ruby, iOS, Android) and an edge decision path through Cloudflare Workers. 1:1 personalisation appears on the pages, but we found no public information showing personalisation tested against a control, mutually exclusive experiment groups or holdouts. 1 12 7

Report an error

The Data Protection Officer

The captured pages document A/B, split URL, multivariate, multi-page, price and multi-armed bandit tests, full-stack experimentation through six SDKs (JavaScript, Android, iOS, PHP, Python, Ruby), feature flags and rollouts, 1:1 personalisation, and variation decisions at the edge through Cloudflare Workers. I found no public information on mutually exclusive experiment groups or holdouts, which keeps this below the highest documented level. 12 1 7

Report an error

The Skeptic

The documented programme is broad: A/B, split URL, multivariate, multi-page and price tests in a visual editor, six SDKs covering web, mobile and server-side, feature flags, multi-armed bandits, 1:1 personalisation, and edge decisioning via Cloudflare Workers. What holds it below the top band is silence on programme-level controls — I found no public information on mutually exclusive experiment groups, holdouts, or whether the personalisation itself can be tested against a control. 12 2 1

Report an error

Statistical method & guardrails

Show 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 — 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 Growth Lead

Three named engines (Frequentist, Bayesian, Sequential) switchable on a running test, sequential testing built on Asymptotic Confidence Sequences with named academic sources and an always-valid p-value, Bonferroni and Šidák corrections, a chi-square sample-ratio-mismatch check that is always on and blocks declaring a winner while flagged, and a sample-size and duration calculator — this is a report I could defend to finance. The captured pages give different figures for the frequentist statistic (2-tailed z-tests on one, t-tests for every experiment started after October 13, 2023 on another), and I found no public information on variance reduction such as CUPED or guardrail metrics that stop a harmful test. 9 1 7 7 8 12

Report an error

The E-Commerce Manager

Three engines — Frequentist, Bayesian, Sequential — switchable on a running test, with the sequential method named and academically cited (Asymptotic Confidence Sequences, per Waudby-Smith 2023), always-valid p-values that survive repeated reads, Bonferroni and Šidák corrections, and a sample-ratio-mismatch check that is always on, fires at 99% confidence and blocks ship decisions while flagged. The stop rule is written down — sequential evidence crossed, mismatch check clean, business decision rule met — and the calculator publishes sample size, duration and an MDE curve. We found no public information on CUPED-style variance reduction or guardrail metrics that stop a harmful test, and because individual visitors are not stored, independent per-visitor re-analysis is off the table. 7 8 9 9 8

Report an error

The Product Engineer

Sequential testing is documented by name — Asymptotic Confidence Sequences, grounded in published academic work — producing an always-valid p-value that holds under repeated checking, with Bonferroni and Šidák corrections as user-configurable options and an always-on chi-square sample ratio mismatch check at 99% confidence that shows mid-test and blocks decisions when flagged. Sample-size planning (baseline, MDE, power, tails, variants, correction) is public, and the choice between Frequentist, Bayesian and Sequential is explained per use case. I found no public information on CUPED-style variance reduction or guardrail metrics that stop a harmful test. 7 8 9 12 8

Report an error

The CRO Consultant

Frequentist, Bayesian and sequential engines are each documented — sequential via an always-valid, e-value-based p-value grounded in published methodology — with Bonferroni and Šidák corrections and an always-on chi-square SRM check that blocks a decision when flagged. A sample-size and duration calculator with MDE, power and correction inputs sits beside stated stop rules; we found no public information on CUPED-style variance reduction or guardrail metrics that auto-stop a harmful test. 7 8 9

Report an error

The Data Protection Officer

Frequentist (t-tests for every experiment started after October 13, 2023), Bayesian with credible intervals and expected loss, and sequential testing via Asymptotic Confidence Sequences grounded in named published academic work are all documented, alongside Bonferroni and Šidák corrections, an always-on sample ratio mismatch check that blocks a decision while flagged, and planning and analysis calculators. I found no public information on variance reduction such as CUPED or guardrail metrics that can halt a harmful test, which is the gap below the top level here. 8 7 9

Report an error

The Skeptic

A rare vendor that names its statistics: always-valid sequential p-values built on asymptotic confidence sequences with the literature cited, always-on sample ratio mismatch checks via chi-square goodness-of-fit at 99% confidence that block decisions, and configurable Bonferroni/Šidák corrections with a documented recommendation and a stop rule stated before the test runs. It falls short of the top band because I found no public information on variance reduction of the CUPED kind or guardrail metrics that stop a harmful test, and the Bayesian probability-of-winning outputs are published without their prior assumptions; the captured pages also give different figures for the frequentist test statistic — two-tailed Z tests on one page, t-tests for experiments started after October 2023 on another. 7 9 12 1

Report an error

Snippet performance & flicker

Show 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, 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 Growth Lead

Snippet weight is published (93 KB gzipped at baseline, roughly 95–110 KB with three to five experiments, one upfront bundle), delivery runs on the Akamai CDN, three loading modes are documented with their trade-offs stated in writing — the default sync mode "can cost you Core Web Vitals", async "accepts some flicker risk" — and a custom-domain option plus an edge path via Cloudflare Workers cover flicker-sensitive tests. What holds it back is that the Core Web Vitals impact is named as a trade-off but never measured publicly, and I found no public information on per-project bundles trimmed to only the active experiments. 2 12 12 2 12

Report an error

The E-Commerce Manager

The numbers I want are public: 93 KB gzipped at baseline, roughly 95–110 KB with three to five experiments, one bundle with no hidden runtime fetches, delivered over the Akamai CDN, with SmartInsert anti-flicker working out of the box and a custom-domain option that keeps the script first-party. The delivery modes come with honest trade-offs — the default sync mode applies variations before render but can cost Core Web Vitals, the async mode feels faster at some flicker risk — and a Cloudflare Workers path moves the decision to the edge before the page reaches the browser. We found no public information on measured Core Web Vitals impact figures or per-project bundles, so I stop short of full marks. 12 13 2 12

Report an error

The Product Engineer

Real numbers are published — 93 KB gzipped at baseline, roughly 95–110 KB with three to five experiments, one upfront bundle, no hidden runtime fetches — and three loading modes are documented with the trade-off stated plainly: the default sync-with-body-overlay stops flicker but can cost Core Web Vitals, async accepts flicker risk. First-party custom domains (CNAME) and a Cloudflare Workers edge path that removes flicker by deciding before render are documented. I found no public information on measured Core Web Vitals impact figures or per-project bundles containing only active experiments. 12 12 13

Report an error

The CRO Consultant

Three loading modes come with their trade-offs spelled out — sync with body-overlay anti-flicker by default, async accepting some flicker risk, React/Vue packages for SPAs — alongside a published snippet size of 93 KB gzipped and roughly 95–110 KB with three to five experiments, Akamai delivery, a custom-domain CNAME option, and Cloudflare Workers as an edge path. The pages acknowledge the sync mode can cost Core Web Vitals but we found no published measurements of that impact, and the snippet is one bundle rather than per-project builds of active experiments only. 12 12 13

Report an error

The Data Protection Officer

Snippet size is published (93 KB gzipped at baseline, roughly 95–110 KB with three to five experiments, one bundle with no hidden runtime fetches), delivery from the Akamai CDN is stated, the three loading modes are explained with their trade-offs including the Core Web Vitals cost of the default synchronous mode, and a first-party custom-domain option plus an edge path through Cloudflare Workers are documented. Measured Core Web Vitals figures and per-project bundles are not published, so this sits below the top documented level. 12 2

Report an error

The Skeptic

The vendor publishes what most hide: the snippet is 93 KB gzipped at baseline and roughly 95–110 KB with three to five experiments, delivered as one upfront bundle, with three loading modes whose flicker-versus-Core Web Vitals trade-offs are stated plainly, including that the synchronous default can cost Core Web Vitals. Akamai delivery, first-party custom domains and an edge path through Cloudflare Workers for flicker-sensitive tests are documented, but I found no public information on measured Core Web Vitals impact or per-project bundles trimmed to active experiments. 12 12 2

Report an error

Analytics, data export & integrations

Show 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 — 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 Growth Lead

An official GA4 integration pushes experiment and variation IDs straight into GA4 ready for BigQuery export, an API, webhooks and the GTM data layer feed Looker Studio and Power BI, warehouses such as BigQuery and Snowflake connect via Segment and Stitch, and raw data has a CSV export — so I can check a promised uplift in our own data. Caveat for the board pack: the vendor states individual visitor data is not stored, so there is no visitor-level export to re-analyse, and I found no public information on API rate limits. 11 12 2 12

Report an error

The E-Commerce Manager

Raw data leaves via CSV export, an API and webhooks sit on every plan, the native GA4 integration pushes experiment and variation IDs ready for BigQuery, Google Analytics goals import with one click, Tealium iQ integrates flicker-free, and BigQuery or Snowflake are reachable through Segment and Stitch — enough for me to cross-check a winner against my own sales data. We found no public information on warehouse-native analysis on my own metrics or stated API rate limits, which is what separates this from the top band. 12 2 15 14

Report an error

The Product Engineer

An official GA4 integration pushes experiment and variation IDs straight into GA4 ready for BigQuery export, BigQuery and Snowflake connect via Segment and Stitch, webhooks and a GTM data layer feed Looker Studio and Power BI, and raw data exports as CSV. API access and MCP servers (local and hosted) are on all plans, and a headless version can run inside our own stack — good enough to build internal tooling on. I found no public information on stated API limits, and metrics are not documented as defined once and computed in the customer's warehouse. 12 2 2 12 1

Report an error

The CRO Consultant

100+ one-tag integrations cover Google Analytics (an official GA4 link pushing experiment and variation IDs, ready for BigQuery export), Segment, Mixpanel, Heap and Tealium, with API access, webhooks and the GTM Data Layer on all plans, raw data CSV export, and BigQuery and Snowflake reachable via Segment and Stitch. We found no public information on stated API limits or visitor-level raw data streaming to a warehouse. 12 14 2

Report an error

The Data Protection Officer

Raw data CSV export, a native Google Analytics integration pushing experiment and variation IDs ready to export to BigQuery, warehouse connections to BigQuery and Snowflake via Segment and Stitch, an API and webhooks available on all plans, and 100+ integrations including Tealium are documented. The same pages state that individual visitors are not stored, and warehouse-native analysis on the customer's own metrics and stated API limits are not documented. 12 2 14

Report an error

The Skeptic

Experiment and variation IDs are pushed straight into GA4 and ready for BigQuery export, which means a result can be re-checked in the buyer's own data — the test I care about — alongside native goal import, Tealium, webhooks, an API and an MCP server on all plans, and BigQuery and Snowflake reached via Segment and Stitch. What is unclear is grain: raw data exports as CSV while individual visitors are stated not to be stored, and API rate limits are not documented. 12 2 14

Report an error

European sovereignty panel opinion

Show 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 — 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 Growth Lead

Website-visitor and experiment data is stated to stay on German servers in Frankfurt across all plans, and a free, signed data processing agreement is offered — that is the part that touches our visitors. But the contracting entity is Convert Insights Inc. of Delaware with Delaware governing law and FTC oversight, customer account data is stored in the US under the Data Privacy Framework, and the snippet is delivered over the Akamai CDN, so the chain from contract to script delivery is not European end to end. 11 3 2 3 4 2

Report an error

The E-Commerce Manager

My visitors' behaviour data is documented to stay on servers in Frankfurt, Germany and not leave Europe, with EU Standard Contractual Clauses and the EU-US and Swiss Data Privacy Frameworks stated for transfers — the part that matters most, since the script runs on every visitor. But the contract is with Convert Insights Inc., a Delaware company under Delaware law with arbitration in Kent County, my account data is stored in the US, and the snippet rides the Akamai CDN whose serving location is not stated. We found no public information on an EU contracting entity or a published subprocessor list with locations, so it sits mid-scale. 3 11 3 12 12

Report an error

The Product Engineer

Visitor tracking data is stated in writing to stay in Europe on German servers in Frankfurt and not leave Europe, with production on AWS, the login site on Hetzner, and a self-serve data processing agreement offered — that is the part I care about, since the script runs on every visitor. But the contracting entity is Convert Insights Inc., Delaware, customer account data sits in the US under the Data Privacy Framework, and transfers rely on SCCs and the EU-US DPF. I found no public information on a published subprocessor list with locations for the platform. 3 3 11 12

Report an error

The CRO Consultant

Visitor experiment data is stated to stay in Europe on German servers in Frankfurt — production on Amazon Web Services with the login site on Hetzner — with the vendor saying no cross-border transfer outside the EEA occurs in its infrastructure and a data processing agreement offered. But the contracting entity is Convert Insights Inc., a Delaware company, customer account data is stored in the US under the Data Privacy Framework, and the snippet is delivered over Akamai with no stated location, so EU processing of visitor data rather than a European setup end to end is what the pages evidence. 3 3 12

Report an error

The Data Protection Officer

Visitor tracking data staying on German servers in Frankfurt that "does not leave Europe", EU-based servers on all plans, and a free signed data processing agreement offered online are stated, with production infrastructure named as AWS and the login site on Hetzner. But the contracting entity is Convert Insights Inc., a Delaware, USA organisation, the customer's own account data is stored in the US under the Data Privacy Framework, and I found no published subprocessor list with locations that includes the Akamai CDN that delivers the script. 3 11 5 2

Report an error

The Skeptic

Visitor and experiment data processing is stated as standard on German servers in Frankfurt, the vendor states it knows of no cross-border data transfer outside EEA borders in its infrastructure, and a data processing agreement is offered with SCC and Data Privacy Framework transfers documented. But the contracting entity is Convert Insights Inc. of Delaware, customer account data is stored in the US under the Data Privacy Framework, and snippet delivery rides Akamai's CDN — I found no public information on an EU contracting entity. 3 3 12

Report an error

Pricing transparency

Show 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 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 Growth Lead

Two of three tiers are fully priced with the traffic metric defined in writing — monthly tested users, each bucketed visitor counted once — plus per-tier limits, overuse rates ($399 per 100K on Growth, $699 per 250K on Pro, and overuse can be turned off), annual discounts of 25% on Growth and 30% on Pro, a $1000/year per-domain custom-domain add-on, and VAT stated as excluded and applied at checkout. Full computability stops at Enterprise, which is price on request, while seats are not separately priced and Enterprise data segregation carries unspecified additional costs. 2 2 2

Report an error

The E-Commerce Manager

The meter is Monthly Tested Users, defined as visitors actually bucketed into experiments with overlaps counted once — exactly the December-proof unit I want — and Growth at $399/mo or $299/mo paid annually and Pro at $599/mo or $420/mo paid annually are public, with overuse published at $699 per 250K tested users on Pro and $399 per 100K on Growth and switchable off, alerts at 90% and 100%, prices stated to exclude tax with VAT/GST applied at checkout, and no features sold as separate modules. A visitor who sees three of my tests counts once, legacy plans are honoured, and monthly plans cancel any time. Enterprise is price on request, additional custom domains cost $1000/year per domain, and I found no public information on seat counts, so a complete annual invoice for the top tier still starts with a conversation. 2 2 2 7

Report an error

The Product Engineer

Growth and Pro are fully priced with the billing period and a precisely defined traffic metric — monthly tested users, meaning visitors actually bucketed into experiments, deduplicated — plus plan limits, published overuse rates ($699 per 250K, $399 per 100K, can be turned off), alerts at 90% and 100% of the allotment, and VAT stated as excluded and calculated at checkout. Enterprise is price on request and annual-only, additional custom domains cost $1000/year per domain, and multi-year discounts are "Ask!". Seats or collaborators are mentioned in plan lists but not quantified or priced on the pages I read. 2 2 2

Report an error

The CRO Consultant

Growth at $399/mo monthly or $299/mo paid annually and Pro at $599/mo monthly or $420/mo paid annually each include 100K monthly tested users, overuse is priced exactly ($399 per 100K on Growth, $699 per 250K above it) and can be turned off, VAT is stated as excluded and calculated at checkout, and the monthly tested user metric is defined precisely enough to estimate before signing — visitors bucketed into experiments, deduplicated across tests. Enterprise is price on request, data segregation on Enterprise carries unstated additional costs, and we found no public information on seat counts per plan. 2 2 2

Report an error

The Data Protection Officer

Growth at $399/mo paid monthly or $299/mo paid annually and Pro at $599/mo or $420/mo are published with the monthly tested users metric defined, per-plan limits stated, overuse rates published ($699 per 250K and $399 per 100K, with the option to turn overuse off) and VAT treatment stated as excluded and applied at checkout. The Enterprise tier is price on request only as an annual plan, seat pricing is not published, and Enterprise data segregation carries unstated additional costs, so a complete annual invoice is not computable from public pages alone. 2 2

Report an error

The Skeptic

Prices are public per tier on monthly and annual billing, the tested-users metric is defined precisely (visitors bucketed into experiments, overlaps counted once), per-plan limits are published, overuse rates of $699 per 250K and $399 per 100K are stated and can be turned off, VAT treatment is disclosed, and no per-module fees are claimed. The Enterprise tier is price on request only, and I found no public information on seat counts or on what Enterprise data segregation costs, though additional custom domains are published at $1000/year per domain. 2 2 2

Report an error

European sovereignty — proven facts

3 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 Outside the EU unverified
Why unverified?

Residency is split: the customers' own account data is stored in the US while website-visitor tracking data stays on German servers, so the pages give no single uniform location for all customer data.

0/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 Published, self-serve unverified
Why unverified?

The GDPR page instead offers a '(free, signed) Data Processing Agreement' on request, so concluding it may still involve vendor signature.

1/1 pts 3 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Convert Experiences

Is Convert Experiences European?

No. whats-best.ai classifies Convert Experiences as Rest of world. Its vendor, Convert Insights, Inc., is incorporated in the United States, per the vendor’s page captured 16 Nov 2026.

Where does Convert Experiences store data?

Convert Experiences stores customer data outside the EU by default, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 9 Nov 2026.

Does Convert Experiences have a free plan?

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

What are the best alternatives to Convert Experiences?

As of 19 Nov 2026, the panel rates Varify.io (3/5), Webtrends Optimize (3/5) and Kameleoon (2.5/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: Convert Experiences 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 (15)

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

  1. 1 Vendor homepage www.convert.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
  2. 2 Pricing page www.convert.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
  3. 3 Privacy policy www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  4. 4 Terms of service www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  5. 5 Security / trust page www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  6. 6 Experiment types & delivery — found from sitemap www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 26 Oct 2026 Details →
  7. 7 Experiment types & delivery — found from sitemap www.convert.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 1 Oct 2026 Details →
  8. 8 Statistical method & guardrails — found from sitemap www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  9. 9 Statistical method & guardrails — found from sitemap www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  10. 10 Consent & visitor tracking — found from sitemap www.convert.com Checked 16 Nov 2026 Details →
  11. 11 Consent & visitor tracking — found from sitemap www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  12. 12 Snippet performance & flicker — found from sitemap www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 26 Oct 2026 Details →
  13. 13 Snippet performance & flicker — found from sitemap www.convert.com Checked 16 Nov 2026 Details →
  14. 14 Analytics, data export & integrations — found from sitemap www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  15. 15 Analytics, data export & integrations — found from sitemap www.convert.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →