Convert Experiences vs VWO

Convert Experiences

The captured pages show a genuinely broad test menu — multivariate, multi-page, split-URL redirects, behavioural targeting and full-stack feature flags on the top tier — which covers most of what I would run on a shop. We found no public information on personalisation at all, let alone personalisation tested against a control, and full-stack appears as a feature name with no documented SDKs or languages.

VWO

The pricing page names A/B/n, split and multivariate tests, cross-domain testing, mutually exclusive groups, and separate personalisation and feature management modules, which is more than a basic visual editor. We found no public information on server-side SDKs, edge delivery, or personalisation that can itself be tested against a control — the captured evidence is a plan feature grid, not delivery documentation. I can see how to test my product page, but not how I would run a holdout against my personalisation.

Convert Experiences

A sample-ratio-mismatch check even on the entry tier, plus sequential testing and a multi-arm bandit on the top tier, are the guardrails I want before trusting a winner on my checkout. But we found no public information naming the statistical method, and no confidence intervals or sample-size calculator, so I cannot see what actually decides the winner.

VWO

The Pro plan names guardrail metrics and sample ratio mismatch detection, which are real protections I value. But we found no public information naming the statistical method, sample-size or duration guidance, or any protection against reading a result too early — a winner figure without a documented method is exactly what I cannot defend to my accountant.

Convert Experiences

First-party cookies only with a six-month non-PII lifetime, no IP storage for identity, and an opt-out link my shop can place are a real start on ePrivacy. We found no public information on what the script does before consent is given, on consent-management-platform integration, or on how testing modes map to the German consent rule — and the privacy notice says authorised third parties may track visitors including IP addresses.

VWO

The privacy policy states it applies only to the customer and not to the visitors of the customer's website, and we found no public information on what the test script stores on a device or when it runs relative to consent. A tracking opt-out for users and named privacy contacts are the extent of the visitor-facing material captured.

Convert Experiences

My product pages cannot afford a flicker, and this is the thinnest story in the captures: Akamai delivery that will "deliver your content fast" is the whole of it. We found no public information on script weight, asynchronous loading, anti-flicker handling, or any published Core Web Vitals figures.

VWO

The CDN runs on named providers across ten locations including Germany, the Netherlands, London and Paris, and self-hosting appears as an Enterprise feature. We found no published script size, no flicker handling described, and no Core Web Vitals figures — on a product page where a tenth of a second shows in conversion, that silence is the whole story.

Convert Experiences

Raw data export to CSV plus API access and ninety-plus integrations on every plan means a test result can be checked against my own numbers, which I insist on. We found no public information on visitor-level streaming to a warehouse, on API limits, or on warehouse-native analysis.

VWO

An integrations page exists, Google Analytics is named, and API access plus pull-based integrations appear in the plan feature lists. We found no public information on exporting results, visitor-level data, or documented API limits — from what is captured I cannot verify a winner against my own analytics data.

Convert Experiences

The line that matters to me is stated plainly — visitor data stays in Europe on German servers, and Frankfurt hosting ships on every plan. Against that, the contract is with a Delaware entity under Delaware law, my account data sits in the US under the Data Privacy Framework, the snippet rides Akamai, and the list of authorised third parties the privacy notice points to is not among the captured pages.

VWO

All customer data is stated to be stored centrally in Washington DC and Dallas, USA, with the contracting entity Wingify Software Pvt. Ltd. in India; the CDN includes EU locations but the storage does not. Standard contractual clauses and an Article 27 EU representative are documented, and we found no public information on EU data residency for visitor data or a subprocessor list.

Convert Experiences

The traffic metric, per-tier limits and overuse rates are public, overuse can be switched off, and legacy plans are honoured — that keeps a December traffic spike from re-tiering my invoice. But we found no public information on the base tier prices or seats, the terms say some features may require additional fees, and the Enterprise tier is price on request, so the annual invoice is not computable from public pages alone.

VWO

The pricing page states there are no fixed plans, only a custom proposal built around goals and scope, and a free trial and free tools exist — but no tier price, traffic metric definition, limit, or overage rate is published anywhere captured. With monthly tracked users only appearing inside a FAQ question, my December invoice is not computable from public pages.