Convert Experiences vs VWO

Convert Experiences

The test types I build programmes on are named and specific: A/B and split-URL testing with behavioural targeting on the entry plan, and multivariate, multi-page, full stack and feature flags, bandit and sequential testing one tier up. Server-side delivery is evidenced only as a feature name though, and we found no public information on documented SDKs, personalisation, mutually exclusive experiments or holdouts, so I stop at the middle of the road.

VWO

The pages show a full client-side programme: visual and code editor, A/B/n, split and multivariate tests, multi-arm bandit campaigns, advanced targeting, cross-domain testing and a personalisation suite, with mutually exclusive groups reserved for the top tier. We found no public information on server-side delivery or documented SDKs — feature management appears as a suite name, not documentation — so I cannot credit the server-side half of what a mid score would require.

Convert Experiences

Two genuine guardrails are published — an SRM check even on the entry plan and sequential testing one tier up — which is more than a bare winner badge. But the decision method is never named as frequentist or Bayesian anywhere I could point a client's analytics lead to, and we found no public information on intervals, a sample-size calculator, multiple-comparison handling or guidance on when a result may be read.

VWO

Guardrail metrics and sample ratio mismatch detection are named as paid-tier features, so the concepts exist in the product. But we found no public information naming the statistical method, no sample-size or duration calculator, and no guidance on when a result may be read or how peeking is handled — I could not brief a client on how a winner gets called from these pages.

Convert Experiences

A DPO can start from what is published: only first-party cookies with a six-month non-PII lifetime, no IP addresses stored to work out identity, and an opt-out link customers can place on their site. What decides a §25 TDDDG sign-off is not addressed though — we found no public information on what the script does before consent, on consent management platform integrations, or on a cookieless mode.

VWO

The privacy policy states its scope covers the customer and not the visitors of the customer's website, and we found no public information on what the test script stores on the device, when it runs relative to consent, or how visitor identifiers are handled. A visitor tracking opt-out, a data processing addendum and standard contractual clauses are documented, which is the only thing lifting this off the floor — as it stands I could not take this consent posture to a client's data protection officer.

Convert Experiences

Performance appears as a claim, not a measurement: the Akamai CDN "will deliver your content fast" and a CNAME custom-domain option exists. We found no public information on script size, loading behaviour, anti-flicker handling or any measured Core Web Vitals impact, so I cannot estimate what a client's pages would pay.

VWO

CDN delivery across ten edge locations including the Netherlands and Germany is documented, and self-hosting is named as an enterprise feature — both genuinely useful for European load times. We found no public information on script size, asynchronous loading, flicker handling or any Core Web Vitals figures, so the actual page cost of the snippet stays unknown to me and to my clients.

Convert Experiences

Every plan carries ninety-plus integrations, API access and an MCP server, and raw data export in CSV is on the pricing page — enough to get results and data out for a second opinion. But we found no public information naming the analytics and tag-management tools, on visitor-level streaming or warehouse-native analysis, or on stated API limits, which is where the re-analysis story would need to go next.

VWO

An integrations section exists, Google Analytics is named in the privacy policy, and the tiers list pull-based integrations and data platform access, with API access reserved for the enterprise tier. We found no public information on a documented API, results export or visitor-level data — API access as a tier line is not something I can build a client's analysis pipeline on.

Convert Experiences

The visitor-data half is stated plainly and would help in an EU pitch: EU-based Frankfurt servers on all plans, and visitor data stays in Europe on German servers. The contracting side pulls the other way — Convert Insights, Inc. of Delaware under FTC enforcement, customer data stored in the US under the Data Privacy Framework — and the third parties who may track visitors appear only as a list reference we could not see, so the chain is only partly defensible.

VWO

The contracting entities are Wingify Software in India and Wingify Inc., and the privacy policy states all customer data is stored centrally in Washington DC and Dallas; we found no public information on an EU residency option, and no subprocessor list appears on the captured pages. Standard contractual clauses, a data processing addendum, an Article 27 representative in Vienna and European offices in Hamburg and Palma are documented, which keeps this above the floor — but for my EU clients this is a transfers-with-safeguards story, not a residency story.

Convert Experiences

The criterion my clients care about most, and it mostly delivers: the traffic metric is monthly tested users with per-tier yearly caps, overuse is priced at "$399 per 100K" on Growth and "$699 per 250K" on Pro and Enterprise and can be turned off, VAT treatment is stated, and a "$1000/year per domain" add-on is published. Held below the top because the Enterprise tier is price on request, some features carry unspecified additional fees, multi-year discounts are something you ask about, and we found no public information on the base subscription figures for Growth and Pro.

VWO

The pricing page states "No fixed plans. Just a custom proposal built around your goals and scope", and no price figure appears anywhere on the captured pages; the monthly-tracked-users metric surfaces only as an unanswered question about a shared quota across products. A trial and demo exist, but with add-ons like Predictive Data and Emotions unpriced I cannot estimate a client's annual invoice before a sales conversation — exactly the number I need up front.