Convert Experiences vs VWO

Convert Experiences

The captured pricing pages list A/B and split-URL tests, multivariate and multi-page testing, behavioural targeting, and full-stack experiments with feature flags on the upper tiers — the right shape — but the evidence names no SDK languages and we found no public information on holdouts, mutually exclusive experiment groups, or personalisation, so the server-side half rests on a feature name alone.

VWO

The published feature lists cover visual and code editors, A/B/n, split and multivariate tests, single-page-app support, a personalisation module, and mutually exclusive groups on the top tier — a solid client-side programme. But everything I can see is a pricing-page feature grid: we found no public information on server-side SDKs, feature-flag delivery or edge distribution, and feature management appears only as a suite name. I land between a capable client-side tool and one programme across surfaces, weighted toward the client side.

Convert Experiences

An SRM check ships on every paid tier and sequential testing plus a multi-arm bandit arrive on Pro, which is more guardrail than most publish — but we found no public information naming the statistical method, confidence or credible intervals, sample-size guidance, or correction for multiple comparisons, so I cannot audit a winner call.

VWO

Sample ratio mismatch detection and guardrail metrics are listed as Pro features and multi-armed bandit campaigns on the lower tier, so some statistical machinery clearly exists. But we found no public information naming the statistical method, showing confidence or credible intervals, sample-size guidance, or how peeking and multiple comparisons are handled. A feature grid is not a methodology a team can defend to a data scientist.

Convert Experiences

Cookies are documented as first-party only with a six-month non-PII lifetime, IP addresses are not stored for identity, and an opt-out link with do-not-track respect is described — genuinely privacy-forward — but we found no public information on what the script does before consent, consent management platform integrations, or a consent-pending mode.

VWO

The privacy policy states outright that it applies only to the customer and not to the visitors of the customer's website, and the only visitor-facing provision I found is a tracking opt-out. We found no public information on what the test script stores on a device, whether it runs before consent, cookie or storage lifetimes, or integrations with consent management platforms. That leaves the §25 TDDDG questions unanswered on the vendor's own pages and shifted to the customer's paperwork.

Convert Experiences

Snippets are delivered over the Akamai CDN and a first-party CNAME domain option is priced at $1000/year per additional domain beyond plan allowances, yet we found no public information on script size, asynchronous loading, flicker handling, or measured Core Web Vitals impact.

VWO

Self-hosting of the script appears as an enterprise feature and the CDN is described with named providers and ten edge locations, which is more than nothing. We found no public figures for script size or loading behaviour, and no information on flicker handling or Core Web Vitals impact. For a snippet that runs on every page, that silence is the story.

Convert Experiences

API access and an MCP server come on all plans alongside 90+ integrations and CSV plus raw data export — enough to start wiring internal tooling — but we found no public information on warehouse-native analysis, visitor-level streaming, or stated API limits.

VWO

Google Analytics is named, an integrations listing exists, Data Studio is a paid add-on, and API access is gated to the enterprise tier with no API documentation visible. Pull-based integrations and data platform access appear only as feature-list items. We found no public information on visitor-level export or streaming to a warehouse, so an experiment result stays a claim I cannot check in my own data.

Convert Experiences

Visitor data is stated to stay on German servers in Europe with a published DPA, but the contracting entity is Convert Insights, Inc. under Delaware law with the FTC as regulator, customer account data sits in the US under the Data Privacy Framework, and we found no published subprocessor list for the service even though authorized third parties may track visitor information including IP addresses.

VWO

The privacy policy states all customer data is stored centrally in Washington DC and Dallas, the contracting entities are Wingify Software Pvt. Ltd. in India together with Wingify Inc., and we found no public information on subprocessors. The EU anchors are an Article 27 representative, offices in Hamburg and Palma, and standard contractual clauses on offer. For a script that records every EU visitor's behaviour, that footing is hard to put in front of legal.

Convert Experiences

The traffic metric, per-tier tested-user limits, overage rates ($699 per 250K and $399 per 100K, with overuse that can be turned off), VAT treatment and add-on domain pricing are all public — but the captured pricing facts give no base plan price, enterprise is price on request, and some features carry unstated additional fees, so the annual invoice is still not computable.

VWO

Tier structure and included features are published, a free trial and free tools exist, and the traffic basis surfaces as monthly tracked users in a pricing question. But the pricing page states there are no fixed plans, only a custom proposal, and we found no price figures, traffic limits or overage terms on the captured pages — the annual invoice is not computable from public information. Wingz AI Core is free with all products while the Advanced tier is marked a paid upgrade with no figure shown.