VWO and AB Tasty Are Combining: What the Merger Means for Your Testing Stack

On January 20, 2026, VWO and AB Tasty announced that they are combining. The companies frame it as a merger of equals: the combined business claims more than $100 million in annual revenue and over 4,000 customers, with VWO co-founder Sparsh Gupta as CEO and AB Tasty’s co-founders Rémi Aubert and Alix de Sagazan taking chief customer and chief revenue roles. Everstone Capital remains the largest institutional shareholder.

If you run your testing program on either platform, this is worth a moment of attention — not because anything breaks tomorrow, but because the questions that matter get easier to ask before the integration settles than after.

What was actually announced

• VWO and AB Tasty “entered into an agreement to combine” — the announcement avoids the word acquisition.
• The stated ambition is “an industry-leading digital experience optimization platform” with AI-native capabilities.
• Leadership merges: VWO’s CEO leads the combined company; AB Tasty’s co-founders move to customer and revenue roles.
• Nothing was said about discontinuing either product line — and nothing was promised about keeping both, either.

What consolidation usually means for customers

Announcements like this one are always reassuring on day one; the real answers arrive over the following renewal cycles. Two platforms that do substantially the same job rarely stay two platforms forever — engineering effort concentrates on one codebase, and one side’s customers are eventually invited to migrate. None of that is sinister. It is simply how mergers of overlapping products work, and it is why the right move now is to get answers in writing:

• Which of the two platforms carries the long-term roadmap — and is it the one you are on?
• If the lines converge, what happens to your historical experiment data, your integrations, and your setup work?
• What does renewal pricing look like while the merged company aligns its plans?
• What is the feature pace likely to be during the integration years, when engineering attention is on unification?

Good answers to all four exist. But they are answers you want from your account team before you sign the next renewal, not after.

The alternative: testing that was never separate from personalization

The merger’s stated goal — a full-stack digital experience platform — is a destination some tools have to assemble and others simply are. Personyze’s A/B testing was built inside a personalization engine from the start: tests resolve to a winner per audience rather than one winner per site, and a variant that wins for one segment can be promoted mid-campaign while the test keeps running for everyone else.

Because it is one product on one visitor profile, the rest of the toolkit is already attached — recommendations, behavioral targeting, dynamic landing pages, email, and an AI chat agent — with no second contract and no integration project. There is a free plan to evaluate on, and a switch path designed for zero downtime: both tags run side by side until you are satisfied, then the old one comes out.

Compare for yourself

• Personyze vs VWO — a feature-by-feature comparison.
• VWO alternatives — the wider field, honestly assessed.
• The best A/B testing tools — where audience-first testing fits.
• Book a demo — see a test resolve per audience on your own use case.

Mergers reshape vendors; they do not have to reshape your program. Whatever you decide, decide it with the roadmap answers in hand.