AB Tasty Is A/B Testing Its Own Identity After the Wingify Merger

The ABWatcher blog

AB Tasty Is A/B Testing Its Own Identity After the Wingify Merger

We caught abtasty.com server-side splitting traffic between two entirely different brands — Wingify and AB Tasty. Here's what that says about post-merger CRO.

Diego Hernandez

Growth Marketer · · Updated

The most CRO thing a CRO company can do: A/B test whether its own brand still works.

We caught abtasty.com doing exactly that. Detected 75% confidence via week-over-week diff on the homepage hero. This isn't a headline swap. This is a server-side split sending visitors to two completely different websites.

TL;DR

  • Detected on abtasty.com home page, hero surface, via week-over-week traffic diff.
  • Analyst confidence: 75%.
  • Variant A routes to wingify.com — pastel branding, "Every visitor is different" messaging, "Create campaign with Wingz" CTA.
  • Variant B stays on abtasty.com — neon lime/purple branding, "Push the limits of experience optimization with AI-powered conversions" hero, "Get ready for better" CTA.
  • This is a server-side redirect split, not a client-side DOM change — a rare pattern for us to catch.
  • Context: comes after the AB Tasty / VWO / Wingify corporate consolidation.

What did AB Tasty actually change?

The test doesn't touch copy or layout on one page — it routes visitors to two different domains entirely. One arm of the split sends visitors to wingify.com. Soft pastel visuals. A calmer promise: "Every visitor is different." CTA reads "Create campaign with Wingz" — friendly, almost playful.

The other arm keeps visitors on abtasty.com. Loud neon lime and purple. Aggressive positioning: "Push the limits of experience optimization with AI-powered conversions." CTA: "Get ready for better."

Same entry point. Two entirely different products being sold. That's not a headline test — that's a brand test running at the infrastructure level.

Takeaway: when a test changes the domain a visitor lands on, you're not optimizing a page, you're optimizing a business decision.

Why does a merger show up as an A/B test?

Because nobody internally knows yet which brand narrative converts better, so they're letting the market decide instead of a committee.

AB Tasty, VWO, and Wingify went through a consolidation, and now there are two go-to-market stories competing for the same traffic. Wingify's pitch leans into a unified "AI-loop" narrative — softer, more platform-agnostic, aimed at teams who want autopilot. AB Tasty's legacy pitch is the classic experimentation-platform pitch — technical, aggressive, built for teams who already believe in testing culture.

Running this as a live server-side split instead of a stakeholder debate is the right move. AB Tasty's own testing guide makes the case for exactly this kind of rigor — measuring what visitors actually do instead of what leadership assumes they'll like. It's a little meta watching the company apply its own gospel to its own merger identity crisis, but credit where due.

Takeaway: if your company just merged or rebranded, don't argue about brand voice in a meeting — split traffic and measure sign-ups.

How rare is a server-side domain-level split?

Very rare — most of what we catch is DOM-level: hero text, button color, layout reflow. A full domain redirect split is an infrastructure-level commitment few teams are equipped to run cleanly.

Here's how this detection compares to typical hero-surface tests we log across the 1,000+ sites we watch daily:

Test type Typical surface Reversibility Signal strength
Copy/headline swap DOM text node Instant Low-medium
CTA color/label DOM button Instant Low
Layout reflow DOM/CSS Instant Medium
Server-side domain split (this one) Full redirect Requires infra rollback High

A domain-level split means someone built redirect logic, aligned two separate marketing sites' tracking, and committed engineering time before a single visitor saw it. Companies don't do that for a font test. They do it when the decision on the table is existential — which name goes on the building.

Takeaway: the harder a test is to build, the more seriously you should take what it's trying to answer.

What does this tell us about post-merger CRO strategy?

It tells us AB Tasty is treating brand consolidation as a conversion problem, not a design problem — and that's the correct framing.

Most companies handle a merger brand decision in a boardroom: pick a logo, pick a tagline, ship it, hope. AB Tasty instead built a live experiment where the dependent variable is sign-ups, not opinions. That matches the operator mindset you'd expect from a company whose own CEO and team built a business on exactly this kind of testing discipline.

It also signals something for the CRO tooling market broadly. AB Tasty, VWO, and Wingify collectively sit adjacent to a crowded field — tools like Zoho PageSense positioned for smaller teams are chasing the same "test everything" gospel downmarket. When the enterprise players themselves are uncertain which brand story wins, that's a signal the whole category's positioning is in flux, not just AB Tasty's logo.

Takeaway: if your category leader is uncertain about its own narrative, don't assume your positioning is settled either — test it.

Common questions

What surface did ABWatcher detect this test on?

The test was detected on the homepage hero of abtasty.com. Rather than changing hero copy in place, the hero click-through routes visitors server-side to one of two entirely separate marketing sites — wingify.com or abtasty.com itself — each with distinct branding and CTAs.

Why is this called a server-side test instead of a normal A/B test?

Because the split happens before the page renders, at the routing layer, not inside the DOM. Client-side tools swap elements after page load; this test decides which entire website a visitor sees based on a server-side traffic split, which is harder to detect and harder to reverse.

What's the actual hypothesis being tested?

Likely question: does Wingify's softer "every visitor is different" AI-loop narrative convert better than AB Tasty's aggressive "push the limits" experimentation-platform pitch, from the same shared entry traffic. Whoever wins probably becomes the primary brand surfaced going forward.

How confident is ABWatcher in this detection?

75% confidence, flagged via week-over-week traffic diff analysis. That's high enough to treat as a real live test, though we always recommend re-checking after a few more weeks of data before drawing final conclusions on which variant is winning.

What should other teams take from this if they're not going through a merger?

Even without a merger, this is a reminder that positioning experiments deserve the same rigor as button-color tests. If you're unsure whether your brand voice matches your buyer, don't debate it internally — split real traffic and let sign-ups decide.

The takeaway for your roadmap

Stop treating brand and positioning decisions as pre-launch debates. If AB Tasty can route live homepage traffic between two entire company identities to settle a merger narrative fight, you can run the same play on a smaller scale — split your hero copy between your "safe" pitch and your "bold" pitch this sprint, and let the data pick the brand voice instead of the loudest person in the meeting.

Read next

More from the ABWatcher blog

From the glossary

Vocabulary the article uses. See all terms →

  • Shrinkage Estimator— A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
  • Flicker Test— A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
  • Pre-Experiment Bucketing Audit— A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
  • Above-Fold Exclusion Rule— A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
  • Flicker-Free Testing— A technical setup that prevents users from briefly seeing the original page before a test variant loads.
  • Orthogonal Test Design— A test structure where multiple variables are changed independently so their individual effects can be measured without interference.

See more like this

ABWatcher catches A/B tests like this across 1,000+ brands.

Watch live experiments at 1,000+ high-converting brands, complete with hypothesis and takeaway. 7 days of Pro, free, no card, then Free forever for ten watched companies.