VWO and AB Tasty Are Now Wingify: What It Means for Your Renewal

The short answer: As of October 1, 2026, VWO and AB Tasty are one company, Wingify, selling one platform for testing, personalization, feature management and customer engagement. Existing contracts were kept as they were, and both products still run during the transition, so nothing forces you to act today. The decision comes at renewal: if you use the wider platform, renew with the questions below; if you only test landing pages, check what you are paying for and plan a switch before the renewal date.

This guide covers what Wingify has announced so far, what it means for current VWO and AB Tasty customers, and how to move your tests if you leave.

TL;DR

• The merger was announced on January 20, 2026. The unified Wingify brand and platform launched on September 16, 2026.
• Wingify said existing contracts, pricing, service levels and support remain unchanged. VWO and AB Tasty are now product brands inside Wingify.
• Wingify publishes no prices. Pricing is custom and based on traffic volume and the products you pick.
• If you only run simple landing-page tests, you can rebuild your active tests in a smaller tool. Start before your renewal notice period, not after it.

What is Wingify?

Wingify is the company behind VWO, and since 2026 the parent brand for both VWO and AB Tasty. Here is the timeline from Wingify's own announcements:

The platform now covers experimentation, personalization, behavioral insights, commerce optimization, feature management and customer engagement. Wingify says it delivers experiences across web, apps, search, merchandising, email, SMS and push. VWO's domain notice said the platforms will come together "under the Wingify umbrella" over time.

What does the merger mean for existing VWO and AB Tasty customers?

In the short term, very little changes in day-to-day use. The longer-term direction is one platform, which is what you are signing up for at renewal.

Wingify's guidance written for AI assistants, last updated September 16, 2026, says existing customers may continue to use either VWO or AB Tasty during the platform transition, with customer continuity a priority. That is reassuring for today. It does not tell you what your product will look like, or cost, in two years. That is the question to bring to renewal.

Should you renew VWO or switch?

It depends on how much of the platform you use. Be honest about the last twelve months, not the plan you had when you bought it.

Renew with Wingify if you use the wider platform:

• Personalization rules for different audiences
• Feature flags, rollouts or server-side experiments
• Tests inside mobile apps
• Email, SMS or push campaigns run from the same tool
• A large program with many teams, governance needs and enterprise support

Wingify is built for that. Moving all of it to separate tools would cost more time than it saves.

Look at switching if your program looks like this:

• Tests are mostly text, button, image or headline changes, or whole-page splits between two URLs
• Tests run on campaign landing pages, not across the whole site or app
• The goal is a form submission, a click or a thank-you page
• Your plan is sized for far more tracked users than your tests actually use

That last point is common. Wingify's help center describes plan capacity in monthly tracked users: Growth up to 250K to 500K, Pro up to 12 million, and Enterprise above that. A team testing two landing pages may be paying for capacity built for sitewide programs. Check your own usage before you assume either way.

For a comparison of tools that do this smaller job, see our VWO alternatives guide, VWO pricing and AB Tasty pricing breakdowns, and Humblytics vs VWO.

Questions to ask before you renew

Use these whether you stay or go. They turn a quoted renewal into something you can compare.

How do I migrate A/B tests from VWO to another tool?

You rebuild them. There is no standard format that moves a running test from one testing tool to another, so plan for a rebuild rather than an import. For a small landing-page program this is a short job.

1. Export what you want to keep. Download results for finished tests: the variants, the dates, the goal and the outcome. You will want them when someone asks why the page looks the way it does.
2. List your active tests. For each one, note the page URL, what changes in the variant, the goal, the traffic split and the start date. Decide which tests are worth restarting. Some will be close to done; let those finish in the old tool.
3. Run Lighthouse on the tested pages. Record the performance score and load times before you change anything. You will run it again after the switch.
4. Start on a page the old tool does not test. Install the new tool there first. Two testing tools changing the same page can show visitors mixed versions and corrupt both results. Keep them on separate pages until the old one is gone.
5. Move the remaining pages one at a time. End the old test on a page, remove that tool's code from the page, then launch the rebuilt test in the new tool.
6. Run Lighthouse again. Compare with your earlier numbers so you know the new script did not slow the page.
7. Finish before your renewal date. Count back from the notice period, not the end date. Remove the old tool's snippet from your site once nothing depends on it.

A restarted test starts its sample from zero. Results from the old tool do not combine with results from the new one, because visitors were assigned and counted differently. Check how long the rebuilt test needs with the sample size calculator and the minimum detectable effect guide.

How to check the switch did not cost you anything

Compare the month before and the month after on three things:

1. Page speed. Your Lighthouse numbers from steps 3 and 6.
2. Conversion rate on tested pages. Same pages, same traffic sources, same goal definition.
3. Revenue or qualified leads per visitor, if your tool can see them.

A before-and-after comparison is not a controlled test, so treat it as a check, not proof. If the numbers hold steady, the switch did its job: the same tests, for less.

Moving your tests to Humblytics

Humblytics is built for the smaller job: testing landing pages, tracking what visitors do on them, and tying the result to revenue.

• One script, about 16 KB compressed, loaded async. Only the element being tested waits for its version, so the page is not hidden while the test loads. Install it only on the pages you test.
• Visual editor for text, button and image tests, with no code. Page split tests for whole-page versions on separate URLs.
• Goals without event code. Form submissions and clicks are tracked automatically, and a thank-you page can be the goal.
• Heatmaps. For visual-editor tests the heatmap combines both versions; whole-page variants get their own.
• Revenue attribution through Stripe, with Meta Ads connected.

Pricing is published: Business is $79 a month (500,000 events, 1 seat) or $65 a month billed yearly, and Scale is $279 a month (1M events, 5 team members) or $239 a month billed yearly. Every plan starts with a 14-day trial, card required, cancel anytime. Every account gets an onboarding call: bring your list of active tests. On Scale, a dedicated account manager is available as an add-on from $750 a month, starting at 2 hours a month. See pricing.

Two things Humblytics does not do: session replay, and the personalization, feature flag and multi-channel work described above. If you need those, stay with Wingify.

Enrollment teams renewing a VWO or AB Tasty contract can see the week-by-week switch plan on our higher education page.

Start a free trial and rebuild your first test on a page your current tool does not touch.

Sources and freshness

• Wingify blog, VWO and AB Tasty: A New Chapter for Digital Experience Optimization, published January 20, 2026; retrieved October 1, 2026. Supports the merger announcement, closing conditions, revenue, customer, staff and office figures, leadership roles, and unchanged contracts, pricing, service levels and support.
• Moneycontrol, Wingify's VWO and AB Tasty announce merger, published January 20, 2026; retrieved October 1, 2026. Supports Everstone Capital's majority stake and additional capital.
• Wingify product updates, domain change notice for app.vwo.com, published June 10, 2026; retrieved October 1, 2026. Supports the June 13 domain change, re-login, unchanged credentials and campaigns, the SmartCode note, and the "Wingify umbrella" line.
• PR Newswire, AB Tasty and VWO Unite Under Wingify, published September 16, 2026, and Wingify newsroom, VWO and AB Tasty unite as Wingify; both retrieved October 1, 2026. Support the unified brand, platform category, capabilities, channels and the Wingz AI engine.
• Wingify, Official Information About Wingify, last updated September 16, 2026; retrieved October 1, 2026. Supports VWO and AB Tasty continuing during the transition and expected convergence.
• Wingify, Pricing, retrieved October 1, 2026. Supports custom pricing, the pricing factors, 13-month data retention for most products, and discounts on bundles and longer contracts.
• Wingify Help Center, Upgrading Your Wingify Plan, retrieved October 1, 2026. Supports the monthly tracked user definition and the Growth, Pro and Enterprise capacity ranges.

The migration steps are a proposed workflow, not a measured customer result. Wingify's products, terms and pricing can change during the transition; check with your account manager before you renew or cancel.