Convert Experiences vs VWO

Convert Experiences

The feature lists show client-side A/B and split-URL testing, multivariate and multi-page testing, behavioural targeting and a full-stack feature-flag tier — a broad programme — but everything I can see is a pricing-grid bullet: no documented SDKs for common languages, no personalisation, no mutually exclusive experiment groups or holdouts, and no published experiment lifecycle or searchable results library.

VWO

The captured pricing page shows A/B/n, split and multivariate testing with a visual and code editor, multi-armed bandit campaigns, mutually exclusive groups and SPA support, plus personalisation and feature management as product suites. What decides the score against it: the evidence is a feature grid, and we found no public information on server-side SDKs, edge delivery, holdouts or personalisation tested against a control.

Convert Experiences

A sample ratio mismatch check ships on the entry plan and sequential testing and a multi-arm bandit are named features, so someone has read the literature — but no page names the estimation method, documents its assumptions, shows confidence or credible intervals or a sample-size calculator, or says how multiple metrics or variants are corrected. A 'Sequential Testing' bullet is a promise, not a protocol.

VWO

Sample ratio mismatch detection and guardrail metrics are named as Pro-tier features — the first two things I check — and that is real. But nowhere on the captured pages is the statistical method named, and we found no public information on confidence or credible intervals, sample-size guidance, any protection against peeking, or correction for multiple comparisons; a feature named on a pricing page is a promise, not a method.

Convert Experiences

First-party-only cookies with a six-month non-PII lifetime and a statement that IP addresses are not stored to identify anyone are published, which is more than most say about storage; but I found no public information on what the script does before consent is given, no consent-management integration, no cookieless or consent-pending mode, and no guidance on the legal basis for testing in the EU.

VWO

The privacy policy states outright that it applies to the customer only and not to the visitors of their websites, so we found no public information on what the script stores on a visitor's device or when it runs relative to consent. A tracking opt-out for end users is mentioned and a compliance page is referenced, which is what lifts this off the floor.

Convert Experiences

The only performance evidence on the captured pages is a marketing line that the Akamai CDN 'will deliver your content fast'; I found no public information on script size, loading behaviour, flicker handling, Core Web Vitals impact, self-hosting or per-project bundles.

VWO

Self-hosting is offered at the Enterprise tier and the privacy policy describes CDN delivery from ten edge locations, so delivery is at least described. We found no public information on script size, flicker handling, asynchronous loading or any measured impact on Core Web Vitals — an anti-flicker snippet with a timeout is the minimum I would expect to see documented, and it is absent from the captured pages.

Convert Experiences

Raw-data CSV export and API access on every plan, with ninety-plus integrations and an MCP server, are enough to pull a result out of the vendor's dashboard and check it. What I found no public information on is warehouse streaming or warehouse-native analysis, the visitor-level granularity of the raw export, CDP audience integration, or stated API limits.

VWO

An integrations section exists, pull-based integrations sit in the Pro tier, API access is gated to Enterprise, and Google Analytics is named as a connected tool. We found no public information on visitor-level export, warehouse or CDP integration, or documented API limits — an API a customer cannot read about is a line on a pricing page, not an audit path for a result.

Convert Experiences

The privacy notice says visitor data 'stays in Europe on German servers and does not leave Europe' and the pricing page lists Frankfurt servers on all plans. Against that, the contracting entity is Convert Insights, Inc. of Delaware under Delaware law, the notice states customer data 'is stored in the US' under the Data Privacy Framework, and it says authorized third parties may track and store visitor information including IP addresses — with no published list of service subprocessors and no statement on where the Akamai-delivered snippet sits.

VWO

The contracting entities are Wingify Software Pvt. Ltd. (India) and Wingify Inc., and the privacy policy states all customer data is stored centrally in Washington DC and Dallas in the United States; the safeguards we could find are standard contractual clauses, a data processing addendum and an Article 27 EU representative. We found no public information on an EU hosting option or a published subprocessor list, so the script's data path runs to the US as standard.

Convert Experiences

The traffic metric with its per-tier limits, per-tier overuse rates, VAT treatment, the USD pricing and even the add-on custom-domain price of $1000/year per domain are all public — unusually honest for a traffic-priced category. But the captured pricing pages show no base price for any tier and the enterprise tier is price on request only, so the annual invoice still cannot be computed from public pages alone.

VWO

The pricing page states there are no fixed plans, only a custom proposal built around the buyer's goals, and we found no public figures for any tier, module or overage; add-ons like Predictive Data and Data Studio are named but unpriced. The traffic quota appears only as an unanswered question about a shared monthly tracked users quota, and a trial is the only visible entry point — the annual invoice is not derivable from public pages.