Convert Experiences vs VWO

Convert Experiences

Client-side A/B and split-URL testing, multivariate and multi-page tests, behavioural targeting and a full-stack feature-flag tier are all listed on the vendor's own pages, but the SDKs behind the server-side tier are not documented in what we captured. We found no public information on mutually exclusive groups, holdouts, edge delivery of experiments, or personalisation that can itself be tested.

VWO

The captured pages show A/B/n, split and multivariate testing with a visual and code editor, multi-arm bandit and rollout campaigns, and personalisation and feature management as named modules. We found no public information on server-side SDKs, edge delivery or a documented experiment lifecycle, so this sits between the client-side editor level and the documented-SDK level even though mutually exclusive groups appear in the enterprise plan.

Convert Experiences

A sample-ratio-mismatch check, sequential testing and a multi-arm bandit appear as plan features, which shows guardrail functionality exists as a product; the statistics that decide a winner are not named on the captured pages. We found no public information on sample-size guidance, confidence or credible intervals, or correction for multiple metrics and variants.

VWO

Guardrail metrics, sample ratio mismatch detection and multi-arm bandit campaigns are listed as plan features, which are genuine guardrails. We found no public information naming a statistical method, no sample-size or duration guidance, and nothing on how early stopping or multiple comparisons are handled.

Convert Experiences

The vendor publishes that only first-party cookies are used, with a six-month non-PII lifetime, and that IP addresses are not stored to work out a visitor's identity; customers can also place an opt-out link. But nothing in the captured pages says whether the test script may run before the consent banner is answered, and we found no public information on a consent-pending mode or integration with consent management platforms.

VWO

The privacy policy states in its own words that it applies only to the customer and not to the visitors of the customer's website, which puts consent and the visitor's device squarely in the customer's hands. We found no public information on what the script stores on the device, whether it may run before the consent banner is answered, any consent-pending mode, or any list of cookies and storage keys; the only visitor-relevant statement is that tracking can be stopped through an opt-out.

Convert Experiences

The only performance evidence is the vendor's statement that the Akamai content distribution network will deliver test content fast, plus Frankfurt-based servers. We found no published figures for script size or loading cost, no anti-flicker snippet described, and no measurement of the effect on Core Web Vitals.

VWO

CDN delivery of test requests on named providers is described, and a self-hosting option sits in the enterprise plan. We found no public information on script size, loading behaviour, flicker handling or any measured effect on Core Web Vitals.

Convert Experiences

Ninety-plus integrations, API access and an MCP server are included on all plans, together with raw-data CSV export, so a buyer can pull results out of the dashboard. We found no public information on stated API limits, warehouse-native analysis on the customer's own metrics, or visitor-level streaming to a data warehouse.

VWO

Google Analytics is named in the privacy policy, integrations and pull-based integrations appear as plan features, data platform access is in the base plan, and API access sits in the enterprise tier. We found no public information on export of visitor-level results, warehouse or CDP integration, or documentation for the API with stated limits.

Convert Experiences

Visitor data is documented to stay in Europe on German servers, which is the part I weigh highest for a script that runs on every visitor; however the contracting entity is Convert Insights, Inc. of Wilmington, Delaware under Delaware law and FTC oversight, and customer account data is stored in the US under the Data Privacy Framework. We found no published subprocessor list that includes the Akamai CDN delivering the test content, while the privacy notice states that authorized third parties may track and store visitor information including IP addresses.

VWO

The contracting entities are Wingify Software Pvt. Ltd. in Delhi and Wingify Inc., and the policy states all customer data is stored centrally in Washington DC and Dallas; the CDN runs on IBM Softlayer and Google Cloud Platform with some European edge locations. A DPA, standard contractual clauses, a named DPO and an Article 27 EU representative are published, but we found no public information on a subprocessor list including the CDN, or any option for visitor data to be processed in the EU.

Convert Experiences

The traffic metric and per-tier limits are published, overuse is priced at $399 per 100K or $699 per 250K and can be turned off, VAT treatment is stated, and additional custom domains carry a published $1000/year per domain price. But we found no public information on the base tier prices in the captured pages, the top tier is price on request only, and the terms reserve additional fees for some features — so a buyer cannot compute the full annual invoice from what we saw.

VWO

The pricing page states there are no fixed plans, only a custom proposal built around goals and scope, and no tier price appears anywhere in the captures. The monthly-tracked-users metric surfaces only inside an FAQ question, and we found no public information on limits, overage or figures for the Predictive Data, Emotions and Data Studio add-ons; a free trial and the free-with-products AI plan are the only public price signals.