The VWO and AB Tasty merger: what it means if you use either testing tool

Two of the biggest names in web experimentation are now the same company. VWO and AB Tasty, tools that a huge share of ecommerce and SaaS teams use to run A/B tests, agreed to combine at the start of 2026, and the integration is still working through its way months later. If your CRO program runs on either platform, or you are choosing a testing tool right now, this changes the questions worth asking before you sign or renew.

What actually happened between VWO and AB Tasty?

Wingify, the company behind VWO, and AB Tasty, the France-based experimentation platform, announced an agreement to combine on January 20, 2026. The combined business reports more than 100 million dollars in annual recurring revenue and over 4,000 customers globally, built from two product lines that used to compete directly for the same experimentation budget. Everstone Capital, the private equity arm that already held a majority stake in VWO, put in additional capital to remain the largest institutional shareholder in the merged entity, according to coverage of the deal. Neither company has framed this as one buying the other out. It reads more like two mid-size platforms deciding that scale beats staying independent in a market that has gotten crowded fast.

This followed months of speculation about consolidation in the experimentation software category, and it is the clearest evidence yet that the prediction was right.

Does this change your contract, pricing or features right now?

For most current customers, no, not yet. As of mid-2026, VWO and AB Tasty still operate as two distinct product suites while the underlying engineering, data models and workflows integrate step by step over several quarters. Existing contracts, pricing and support levels carry over unchanged in the meantime. The one concrete change that has already shipped is cosmetic: VWO's application moved from the app.vwo.com domain to app.wingify.com on June 13, 2026. Your data, plans, features and access stayed exactly where they were.

What is moving, more slowly, is the product roadmap. AB Tasty's personalization engine and its Flagship feature-flag product are being made available to VWO customers, and VWO's heatmap and session recording tools are heading the other way toward AB Tasty's customer base. The stated ambition is a single suite spanning experimentation, personalization, feature management and behavioral analytics under the Wingify name, with a shared AI layer called Wandz sitting across all of it. A roadmap slide is not the same thing as a shipped feature.

Why is A/B testing software consolidating in 2026?

The honest answer is that the core product stopped being the differentiator. Run a fair comparison between the major experimentation platforms and the statistical engine, the visual editor, and the basic reporting all do roughly the same job. Where vendors compete now is on personalization depth, feature-flagging for engineering teams, AI-assisted test idea generation, and how well the platform plugs into a CDP or a data warehouse. Building all of that from scratch, on top of maintaining a mature testing core, is expensive for a company running at 4,000 customers on its own. Combining two customer bases and two engineering teams is a faster route to that broader platform than either company building it alone, which is the same logic behind most software consolidation waves.

It also is not happening in isolation. New AI-native testing entrants promising faster time to a valid result and automated variant generation are pressuring the incumbents from below while consolidation happens at the top, and a market squeezed from both directions tends to produce exactly this kind of merger.

What should current VWO or AB Tasty customers do?

Do less than the headlines suggest. A merger announcement is not a reason to panic-migrate a live testing program, and doing so would cost you more than the merger itself. What is worth doing is putting the renewal date on your calendar with a specific reminder to ask direct questions about pricing before you sign, rather than after. Post-merger price increases rarely show up as an announcement. They show up quietly at the next renewal, framed as aligning plans across the combined platform.

It is also worth asking your account team, in writing, whether any feature your team is relying on is scheduled to be deprecated or folded into the other product's version of it. If your program depends on a specific report or integration that only exists on one side of the merger, get a commitment on its future before it becomes a surprise six months from now.

What should you look for when choosing a testing tool in 2026?

If you are picking a platform now rather than sitting inside an existing contract, the merger is a useful prompt to evaluate on criteria that matter more than a feature checklist.

None of this is specific to VWO and AB Tasty. It is a reasonable habit for any vendor decision where switching costs are real, in any category going through consolidation.

Is vendor consolidation an actual risk for your CRO program?

Yes, but the risk is specific and worth naming precisely rather than treating as vague uncertainty. Your tests will not stop running because two companies merged. The real risk is pricing power. Fewer independent competitors in a category gives the surviving vendors more room to raise prices at renewal, because switching costs, retraining a team, rebuilding test history, re-integrating with your conversion optimization workflow, are real and vendors know it. The second risk is slower response to a specific feature request, because a company mid-integration has finite engineering capacity and a long list of merger-driven priorities ahead of any one customer's ask.

Neither risk is a reason to leave a platform that is working. Both are reasons to negotiate renewal terms with more information than you had a year ago, and to build data portability into your setup regardless of which vendor you use. That habit outlasts any individual merger.

Frequently asked questions

What actually happened with VWO and AB Tasty?

VWO's parent company Wingify and AB Tasty agreed to combine, announced January 20, 2026. The merged company operates under the Wingify brand, reports more than 100 million dollars in annual revenue, and serves over 4,000 customers across both product lines. Everstone Capital, VWO's majority backer, remains the largest institutional shareholder.

Do I need to migrate off VWO or AB Tasty right now?

No. As of mid-2026, both platforms still run as separate suites with unchanged contracts, pricing and support. The one confirmed change so far is a domain move, VWO's app moved from app.vwo.com to app.wingify.com on June 13, 2026, which is a branding update and does not affect your account, data or configuration.

Why are A/B testing platforms consolidating in 2026?

Experimentation tooling has matured into a commodity layer, most vendors run the same statistical engine and visual editor, so growth increasingly comes from adding personalization, feature flagging and AI-assisted analysis rather than from a better testing core. Combining two customer bases and engineering teams is a faster way to fund that expansion than building it alone.

What should I look for when choosing an A/B testing tool now?

Weigh implementation cost against how often you actually ship winning tests, check whether the vendor's roadmap depends on a pending integration, confirm data export and API access are unrestricted, and ask directly about contract terms during a merger or acquisition. A tool you can leave cleanly is worth more than one with the longest feature list.

Should I switch testing tools because of the merger?

Not on the merger news alone. Switching a testing platform mid-program resets your test history, your team's familiarity with the interface and often your statistical baselines. Unless your renewal is close, a support ticket is unanswered, or a specific feature you were promised gets shelved, watching for one or two renewal cycles is the lower-risk move.

Is vendor consolidation a real risk for a CRO program?

Yes, in a specific way. The risk is not that your tests stop running, it is pricing power. A market with fewer independent competitors gives the surviving vendors more room to raise prices at renewal and slower incentive to ship features a customer specifically asked for. Track your renewal date and get pricing in writing before it comes up.

The takeaway

VWO and AB Tasty merging into Wingify does not require anyone to touch their live tests today. It is a signal worth reading correctly, though. Experimentation tooling is consolidating the same way most mature software categories eventually do, and that consolidation shows up first in pricing leverage and roadmap priorities, not in a dashboard that suddenly stops working. Keep your test history and tracking portable, watch your renewal date, and treat this merger as a reason to ask sharper questions rather than a reason to change tools you are otherwise happy with. If you are building or rebuilding a website around a testing program from scratch, this is also the right moment to decide how much of your measurement layer should live outside any single vendor's walls.