VWO Release Notes
30 release notes curated from 34 sources by the Releasebot Team. Last updated: Nov 12, 2026
- Oct 13, 2026
- Date parsed from source:Oct 13, 2026
- First seen by Releasebot:Nov 12, 2026
From Figma Design to Live A/B Test, Without Waiting on a Developer
VWO ships Wingz’s Figma connector, letting teams turn selected designs into test variations with a plain-language prompt. The release streamlines the design-to-A/B-test workflow and supports carrying winning variations through feature flags into production.
Every optimization team knows the handoff. A designer finishes a new hero section in Figma. To test it, someone has to write the code, match the spacing, get the colors right, and wait for a developer to pick up the ticket. By the time the variation is live, the idea has lost its momentum.
Wingz’s Figma connector removes that handoff. You connect Figma, paste a link to the design, describe the change in plain language, and Wingz builds the variation for you.
It is one of the most requested features Wingify has shipped, and it is easy to see why.
How it works
There are four steps:
- Click the Figma button in Wingz and grant access.
- In Figma, right-click the section you want and choose “Copy link to selection.”
- Back in Wingz, paste the link into the AI editor and click “Import design,” or paste it straight into the chat.
- Describe the change, for example, “make the hero section match the Figma design.”
Within about a minute, the variation is built and matches the design.
Why Figma beats a screenshot
You can also hand Wingz a PNG or other image, and it will do a reasonable job. But it has to guess the font, the padding, and the colors. It estimates well, but estimates are all they are.
Figma gives Wingz the exact values: the exact SVG, colors, padding, and spacing. That is the difference between a variation that is close and one that matches your design. If you do use an image, add context. Tell Wingz the font, the padding, and the exact colors, and it will go much further.
A concrete example
Say your pricing page hero has been underperforming for a month. A designer mocks up a cleaner version in Figma. Instead of writing a ticket and waiting, you select the hero frame, copy the link to the selection, paste it into Wingz, and type “make the hero section match the Figma design.” A minute later, the variation is ready to launch.
The one step people get wrong
Do not paste the link to your entire Figma file. Select the specific frame or section you want Wingz to work on, then copy the link to that selection.
If you paste the whole file, Wingz will block it. The design is too large, it burns through credits, and the output isn’t good. This is the step that trips people up most often, so it is worth getting right the first time.
From design to production
The connector covers more than the test itself. Once a variation wins, you can pull it through the Wingify MCP server, ask your AI assistant to create a Wingify feature flag, and deploy that code as part of your codebase.
The full path runs from design to A/B test to winner to feature flag to production, with no rewrite in between.
Built for how teams design now
Design work is moving into AI tools. More teams are designing in Claude and other assistants instead of starting on a traditional canvas. Wingify’s MCP connection covers that path too, so whether a design starts in Figma or in an AI assistant, it can still end up as a live test.
Who it’s for
The connector is built for the teams that own the design-to-test loop: CRO and experimentation teams, product designers, and product managers. If your team has ever parked a good design because the build queue was too long, this is for you.
Getting started
Pick a design your team has been meaning to test. Select the frame, copy the link to the selection, and let Wingz build it. Once you see how fast the loop closes, you will want to run the next one.
The bottleneck was never the idea. It was the handoff.
Original source - Sep 25, 2026
- Date parsed from source:Sep 25, 2026
- First seen by Releasebot:Nov 13, 2026
Every Language, One Campaign, No Duplicate Work
VWO introduces Translation Manager, bringing multilingual campaign content into one shared workflow. Teams can translate and edit page changes across languages, preview versions, target visitors by language, and compare results without splitting campaign traffic.
The problem: multilingual campaigns multiply the work
For a global brand, multilingual campaign management gets expensive fast. Consider a single campaign that needs to run in 8 languages. Until now, that meant 8 separate sub-tests. Each had to be built, maintained, and reported on separately. Multiply that by every campaign you run, every quarter, and the overhead compounds: more setup time, more room for error, and less time spent on the work that actually moves metrics.
The real cost isn’t the translation itself. It’s the orchestration around it: the duplicated builds, the version drift, the manual coordination between teams and markets. And because each language lived in its own sub-test, comparing performance across markets was never straightforward.
What Wingify’s Translation Manger does:
Translation Manager brings content internationalization to Wingify. Within a single campaign, you can manage as many languages as you need.
You make your changes once in the Visual Editor — text edits, HTML changes, and widget content — and then translate them. Every element you modify is collected in one place, so there are no scattered files and no hunting for the right version. Because translations are attached to the changes you make, your base page stays untouched.
There are two ways to work. Translate everything at once for a fast first pass across all your target languages, or go element by element and refine individual strings where nuance and brand voice matter most. Automatic translation does the heavy lifting; manual editing gives you final control. You can preview any language with a single click before you publish, so you catch layout or tone issues before they reach a visitor.
How visitors get the right language:
By default, Wingify detects the visitor’s browser language and serves the matching version of your campaign. That covers most cases out of the box.
If your site determines language another way — a URL path like /fr/, a cookie, or geolocation logic — you can pass your site’s language variable, and it takes precedence over the browser setting. Setup takes a couple of lines of JavaScript, using a language value you likely already have in your data layer or URL. There’s nothing to rebuild and no new integration to maintain. And if a visitor’s language isn’t one you’ve configured, the campaign falls back to your default website language, so nothing breaks.
What makes it different:
No split traffic. Some tools handle languages by creating a separate variation for each one. That splits your traffic into language silos, and it unbalances your sampling: a market with a small audience can distort what you see in a market with a large one. With Wingify’s Translation Manager, every visitor sees the campaign in their own language while staying in the same sample. Your results stay clean, comparable, and reliable across markets.
Not just widgets. Translation isn’t limited to pop-ups and widgets. It covers all the content you modify on the page, so a headline change, a new banner, or an edited call to action can all be localized in the same place.
Built to scale. There’s no limit on the number of languages you can add. Translation Manager handles Japanese, Arabic, Indian scripts, and other writing systems correctly. And it works across campaign types, from experimentation to personalization. Whether you support two languages or twenty, the workflow is the same. You can add languages to a running campaign at any time, without rebuilding anything.
Who it’s for:
Translation Manager is built for enterprise, multi-country teams that create campaigns centrally and roll them out across markets. If your team builds one campaign and then spends days producing language declinations, this is for you. It’s especially valuable for teams running global promotions, regional pricing tests, or localized personalization at scale. And if your markets run on different content calendars, or regional teams need to review copy before launch, everything now lives in one shared campaign.
The bottom line:
Global campaigns shouldn’t mean global overhead. Translation Manager gives you one campaign, every language, and results you can trust — without duplicating work or splitting your traffic.
Want to know more? Check out our documentation here.
Original source All of your release notes in one feed
Join Releasebot and get updates from VWO and hundreds of other software products.
- Sep 10, 2026
- Date parsed from source:Sep 10, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
Stop Switching Tabs: Run Your Wingify Experiments From Claude
VWO launches an MCP server that connects Claude, ChatGPT, Cursor, and other assistants to experimentation data and actions. Teams can create tests, review reports and insights, retrieve recordings, and manage feature flags directly from their AI tools, with availability on Core and Advanced plans.
If you already work in Claude, ChatGPT, or Cursor, you know the friction. You want to ask about last quarter’s tests, or spin up a new A/B test, and the assistant can’t see any of it. So you open Wingify in another tab, copy the numbers across, paste them back, and lose the thread of the conversation you were having.
The Wingify MCP server removes that step. It connects your AI assistant directly to your Wingify data and actions, so the tools you already use can read your experiments and act on them.
What is MCP?
MCP stands for Model Context Protocol. It’s the standard way for connecting AI tools or AI assistants to outside tools and data. Wingify’s MCP server is that connection for your experimentation platform. Your assistant brings the intelligence, and Wingify brings the data and the actions.
Think of the difference between an app and a website. A dedicated app can do more and is more deeply integrated. A website is a URL you open instantly, with nothing to install. MCP is the URL. There is no new interface to learn and no new prompting style to master because you keep working in the assistant you already know.
What you can do with it
Once you are connected, you can ask your assistant to:
- Create an A/B test or a split URL test
- Pull the report for a test, including segmentation
- Fetch session recordings and heatmaps
- Read behavioral insights
- Create a feature flag in Wingify and push the code into your codebase
That last item matters. A single connection covers the whole loop of analyzing, testing, and shipping, instead of one tool for analytics and another for releases.
Questions you can ask on day one
The fastest way to see the value is to try it on work you are already doing:
- “Create an A/B test on the pricing page with two variations.”
- “How did last month’s checkout test perform, broken down by segment?”
- “Pull the session recordings from the test that just finished.”
- “Pause the campaign that is underperforming.”
Each of those replaces a manual trip into the platform with a single sentence.
Works with the assistants you already use
Claude, ChatGPT, and Cursor have native, one-click connectors. Gemini Enterprise and Microsoft Copilot Studio are supported with a short setup. For anything else, you can use the MCP URL directly.
Context that carries over
A common question is whether you lose your history when you move into an assistant. You don’t. If you ran and analyzed a test through Claude, Claude remembers it and can build on it later. Plus, upon request, your assistant can retrieve previous tests and historical insights. straight from Wingify and factor them into its analysis.
What still lives inside Wingz
MCP complements Wingz, Wingify’s AI layer, rather than replacing it. Three capabilities remain exclusive to the platform: Synthetic A/B testing, IDEA AI, which is Wingify’s proprietary approach to generating test ideas, and Workflows.
Furthermore, Wingz shares the exact same MCP control plane as your assistant. There is no separate system behind the scenes, so what you can do from Claude uses the same actions the platform uses.
Who it’s for
The MCP server is built for teams that have already made AI part of how they work. Whether your organization is driving a mandate to automate processes through AI or your team simply lives in Claude or ChatGPT all day, MCP meets you where you are instead of asking you to learn another interface.
Getting started
The MCP server is available on both the Core and Advanced plans. Core includes a monthly limit on tool calls, while Advanced raises that limit significantly and adds behavioral insights and heatmap data through MCP.
Connect your assistant, ask your first question, and stop copying and pasting between tabs. Start your free trial today or request a demo for more information!
Original source - Aug 28, 2026
- Date parsed from source:Aug 28, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
Wingz Workflows: AI Automation for CRO Teams
VWO releases Wingz Workflows, customizable AI automation that analyzes campaigns, heatmaps and recordings on a schedule or in response to account events. Teams can start with ready-made templates or describe a workflow in plain language, then receive actionable summaries by email.
Every optimization team knows the drill. To answer one question, ”Why did this campaign underperform?” or “What should we test next?”, someone opens the heatmap tool, reads through session recordings, pulls the campaign report, drops it all into a spreadsheet, and tries to make sense of it. Days later, a deck lands in the team’s inbox.
The insight is usually good. The problem is the timing, the effort, and the fact that it depends on whoever happened to do the analysis that week.
Wingz Workflows changes that. It is customizable AI workflow automation, embedded in Wingify, that runs your optimization work for you, on a schedule or the moment something happens in your account. Instead of a person chasing data across tools, a workflow does the chasing. It runs the analysis, pulls the threads together, and puts the answer in front of you while the moment is still live.
What is a Wingz Workflow?
Think of a workflow as a chain of steps that runs on its own. Every workflow starts with a trigger and ends with an action, with one or more AI agents doing the work in between.
An agent: Does a specific job like analyzing a campaign, reading a heatmap, summarizing session recordings, drafting test ideas.
A workflow: Orchestrates those agents toward a single outcome.
That means a workflow can be as simple as “whenever a campaign is paused, summarize the results and email the team,” or as involved as running heatmap and session-recording analysis in parallel every week, merging the findings, isolating the biggest friction point, and generating three test ideas, each with its own brief.
Start from a workflow template, or just describe what you want
You don’t have to build anything from scratch if you don’t want to. Wingify offers more than 20 ready-made workflow templates, handpicked from the most common optimization use cases.
They are organized around the jobs teams actually do: reporting and summary, monitoring and alerting, ideation and test creation, knowledge management, QA and governance, diagnosis, product and feature flags, and personalization.
A few examples:
- Automated campaign debrief: When a campaign reaches a decision, an agent summarizes the winner, the metric trade-offs, the segment breakdown, and a recommended next test, then emails the team.
- Conversion drop alert: Every day, an agent compares conversion rates against a rolling baseline and emails a diagnosis only when it detects a material drop.
- Weekly heatmap friction scan: Every week, an agent scans heatmaps across active pages and ranks the top friction points by page and severity.
- Heatmap and recording to three test ideas: Every week, an agent analyzes heatmaps and session recordings in parallel, merges both, and turns them into three test ideas with full briefs.
If none of the templates fits, describe what you want in plain language and the Wingz Workflow Assistant assembles the workflow for you. No code, no developer, no ticket to the engineering team.
How a workflow is built
Under the hood, every workflow is assembled from a small set of building blocks: a Start node that defines when it runs, one or more Agent nodes that do the work, logic nodes that route and recombine the flow, and an End node that decides what happens next.
Triggers are flexible. Run a workflow on a recurring schedule — daily, weekly, or monthly — or fire it in response to something happening in your account, such as an A/B test being paused.
And you are never left guessing what happened: when a workflow finishes, it can notify the people you choose by email, with an AI-written summary of the results.
Why context changes everything
Most automation tools make you stitch separate systems together, and you lose the context that made the data valuable in the first place.
Wingz Workflows runs inside Wingify, where your campaigns, audiences, reports, session recordings, and heatmaps already live. The agents work from one shared picture of your program, rather than each person’s slice of it. That also removes a quieter problem: when a designer, a product manager, and an analyst each interpret the same data differently, decisions drift. A workflow applies one consistent reading every time.
You stay in control
Automation does not mean handing over the keys. You define the trigger, the instructions, and the action. Workflows run on your schedule, notify the people you name, and each template shows an estimated credit cost per run, so you can weigh value against cost before you publish.
Where to start with workflows
Pick one recurring task your team does by hand today, such as the weekly status digest, the post-test debrief, or the friction scan, and let a workflow take it from there.
Your team’s time is better spent acting on insight than assembling it. That is what Wingz Workflows is for. Check out the detailed documentation for more or start a free trial.
Original source - Aug 21, 2026
- Date parsed from source:Aug 21, 2026
- First seen by Releasebot:Aug 21, 2026
Introducing Wandz inside Visual Editor: From design to live experiment in a single workflow
VWO introduces Wandz inside Editor, a new AI-powered no-code workflow that turns Figma designs, screenshots, PDFs, or simple prompts into ready-to-launch experiment variations. It brings asset ingestion, visual rendering, campaign setup, and launch steps into one session for Wingify Testing customers.
When VWO introduced the visual no-code editor 16 years ago, it eliminated the primary bottleneck in A/B testing: needing a developer for basic changes.
However, as experimentation programs matured, new friction points emerged. Today, the delay in launching an experiment isn’t just writing code, it is translating design files into web elements, jumping through multi-step setup wizards, defining targeting rules across isolated UI tabs, and managing developer sprint queues for non-trivial variations.
Prompt-to-variation features are fast becoming standard across optimization tools. Wandz inside Editor is built differently. Rather than acting as a simple text-to-HTML generator, it unifies asset ingestion, visual rendering, and campaign configuration into an end-to-end operational workflow within Wingify.
Most AI editors force users to become prompt engineers – requiring long, hyper-specific instructions and endless manual parameter adjustments to get a usable output.
Wandz inside Editor eliminates prompt fatigue by using an advanced engine that automatically infers layouts, page hierarchy, and styling rules from minimal input.
What are the possibilities?
From Figma design to live experience in minutes
With Figma integration, you can go from a Figma design to a fully configured, pixel-perfect experience in under 2 minutes. Just connect your Figma account, paste in the design link, and Wandz inside Editor pulls the frame in as an attachment to your prompt – no more manually eyeballing colors, spacing, or fonts from a design file.
You can even attach a screenshot, PDF mockup, or any image alongside your prompt, and the AI will read the layout, understand the visual goal, and produce the variation in your branding.
Go from idea to live variation in seconds
What used to take hours now takes a single sentence. Just type what you want to change, and it’s done. Within seconds, a new variation is ready.
Select any part of the page and describe your vision. Wandz inside Editor interprets your intent, understands the page context, and intelligently generates the changes – whether it’s refining a single component or reimagining an entire experience.
How this changes the way you experiment:
- Speed: Wandz inside Editor removes the developer bottleneck from experimentation. A marketer’s hypothesis reaches production without waiting for an engineering sprint.
- Scalability: When each experiment takes minutes instead of hours, you can run more tests, learn faster, and compound your wins. The teams that experiment most win most.
- Everything in one place: The entire workflow – Creating variations, reviewing & refining them, configuring campaigns, and launching them – everything happens in a single session, without context-switching.
When you can build your reality as fast as you can think about it, experimentation stops being an activity and starts being a habit.
Getting Started
Wanda inside Editor is now available to all Wingify Testing customers.
Launch Wandz inside Editor: Open Editor in your workspace.
If you have any questions or feedback, please reach out to [email protected]
Original source Similar to VWO with recent updates:
- Zoom release notes229 release notes · Latest Nov 20, 2026
- Slack release notes288 release notes · Latest Nov 18, 2026
- Dropbox release notes30 release notes · Latest Nov 5, 2026
- Twilio release notes110 release notes · Latest Nov 19, 2026
- Semrush release notes34 release notes · Latest Nov 16, 2026
- Plaid release notes90 release notes · Latest Nov 2, 2026
- Jun 18, 2026
- Date parsed from source:Jun 18, 2026
- First seen by Releasebot:Sep 21, 2026
[Most requested!] Introducing interconnected behavior analytics with feature releases
VWO introduces Behavior Analytics for Feature Experimentation, bringing integrated heatmaps and session recordings to campaign reports and Insights. Teams can now inspect clicks, scrolls, hesitations, and drop-offs across web and mobile app experiments to make evidence-backed decisions.
For feature launches, the “why” behind user interactions has always been a black box.
You get the adoption numbers, but you never really see the actual behavior behind them.
That’s the gap we have filled.
Introducing Behavior Analytics linked with Feature Experimentation.
Now, with every feature experiment, rollout, and personalization campaign, you will have integrated heatmaps and session recordings to see where a user clicks, scrolls, hesitates, or drops off.
Step into their digital shoes. Wherever they go – a website or mobile app.
Say bye to guesswork. Say hi to evidence-backed product decisions.
Why do you need it?
To investigate faster:
When a test underperforms, was it the design, the copy, a bug, or wrong placement? Figure out the hidden reason, in minutes.
To stop gambling:
A new feature launch need not be a gamble. Make it strategic with phased releases + behavior tracking to spot usability issues and friction trends before they drastically affect your core business metrics.
To check whether users are feeling special:
Once you personalize certain experiences, there’s a certain bias to think they will work. But do they? If behavior analytics is not interconnected, you might miss early signals about whether they do, or not.
To boost confidence (for real!):
PMs and developers justify roadmap decisions with visual evidence. Designers validate UX choices with real behavior. Developers spot bugs and usability issues instantly. Analysts will be able to tell the complete story behind the numbers.
How does it help you?
Understand test results deeper:
You are a PM, you tested a new checkout experience. Say, it won by 8% uplift. Understand which elements users actually engaged with, and where they hesitated, using variation-specific heatmaps.
Say, your pricing page test lost for mobile visitors. You can see the session recordings of users who dropped off without requesting a demo.
Ideate features with evidence:
As a developer, you get to see visual evidence, you can create data-backed feature stories, pitch them internally, get the buy-in from your higher-ups, and launch with a probabilistically high level of success rate.
Cut losses quickly:
As a growth marketer, you need to adjust experiments, feature rollouts, and personalization campaigns in real-time, or every visitor interaction will bleed revenue loss. Now you can visually see how visitors interact, using heatmaps and session recordings. If your new feature is performing way worse than how it should, you can instantly pause the feature release.
Find bugs faster:
As an engineer, you can use visual insights to spot where users struggle, debug feature issues faster, and validate fixes through experiments – so every release is backed by real user behavior, not guesswork.
What can you do, and where to find this?
Integrated behavioral analysis tab in campaign reports:
Every FE campaign report now has a dedicated “Behavioral Analysis” tab with heatmaps, session recordings (for website and mobile apps), pre-filtered to that campaign. No more jumping between tools and context switching.
Access from Insights:
Any heatmap, recording, or funnel in Insights can be filtered by FE campaigns, specific environments, campaign rules, or test variations. That way, you can go deep into behavioral patterns for any experiment you’ve run.
Enter from mobile app recordings & heatmaps:
Extend the same behavioral analysis to mobile app experiments, with screen taps, user flows, and sessions linked directly to your mobile SDK-powered tests.
How does it help your team?
For E-commerce & Retail:
You launched a new product recommendation engine for your mobile app. It lifted AOV, but bounce rate also rose. The recordings reveal users’ attention drifted from purchasing the product, to browsing the “You might also like” section, to check more options. You fix its position, not the algorithm. Without behavior analysis, this insight would have been hidden.
For SaaS & Software:
The trial onboarding test for your webapp is failing, but the metrics don’t explain why. Using session recordings and heatmaps, you spot a clear drop-off happening at the second step of the flow. Users took a lot of time entering their webpage URLs to configure your product, and when they entered, there were many rage clicks on the “proceed” button. With that insight, you’d know for which field you need to reduce friction in the trial flow (maybe add a regex option for URLs). That way, you catch the flaw before it drags the lead count down.
For News & Media:
Heatmaps could reveal that in the test, where you are testing a new ad placement section, the ads are getting drastically low clicks. Session recordings reveal that users are seeing a cookie consent pop-up on top of it. Rookie mistake, yes. Happens to everyone, but would you have known the reason by just looking at statistical numbers?
See the full picture of your experiments today.
Behavior Analytics in Feature Experimentation is rolling out now to all customers on Pro & Enterprise plans of both Feature Experimentation and Insights.
To get started, open an Feature Experimentation campaign report and click the new “Behavioral Analysis” tab.
Questions or feedback?
Reach out to your Customer Success Manager, or email us at [email protected].
We’re all ears.
Original source - Jun 18, 2026
- Date parsed from source:Jun 18, 2026
- First seen by Releasebot:Jun 19, 2026
[Most requested!] Introducing interconnected behavior analytics with feature releases
VWO adds Behavior Analytics to Feature Experimentation, bringing integrated heatmaps and session recordings to campaign reports and Insights. Teams on Pro and Enterprise can now see how users click, scroll, hesitate, and drop off across web and mobile experiments.
For feature launches, the “why” behind user interactions has always been a black box.
You get the adoption numbers, but you never really see the actual behavior behind them.
That’s the gap we have filled.
Introducing Behavior Analytics linked with Feature Experimentation.
Now, with every feature experiment, rollout, and personalization campaign, you will have integrated heatmaps and session recordings to see where a user clicks, scrolls, hesitates, or drops off.
Step into their digital shoes. Wherever they go a website or mobile app.
Say bye to guesswork. Say hi to evidence-backed product decisions.
Why do you need it?
To investigate faster:
When a test underperforms, was it the design, the copy, a bug, or wrong placement? Figure out the hidden reason, in minutes.
To stop gambling:
A new feature launch need not be a gamble. Make it strategic with phased releases + behavior tracking to spot usability issues and friction trends before they drastically affect your core business metrics.
To check whether users are feeling special:
Once you personalize certain experiences, there’s a certain bias to think they will work. But do they? If behavior analytics is not interconnected, you might miss early signals about whether they do, or not.
To boost confidence (for real!):
PMs and developers justify roadmap decisions with visual evidence. Designers validate UX choices with real behavior. Developers spot bugs and usability issues instantly. Analysts will be able to tell the complete story behind the numbers.
How does it help you?
Understand test results deeper:
You are a PM, you tested a new checkout experience. Say, it won by 8% uplift. Understand which elements users actually engaged with, and where they hesitated, using variation-specific heatmaps.
Say, your pricing page test lost for mobile visitors. You can see the session recordings of users who dropped off without requesting a demo.
Ideate features with evidence:
As a developer, you get to see visual evidence, you can create data-backed feature stories, pitch them internally, get the buy-in from your higher-ups, and launch with a probabilistically high level of success rate.
Cut losses quickly:
As a growth marketer, you need to adjust experiments, feature rollouts, and personalization campaigns in real-time, or every visitor interaction will bleed revenue loss. Now you can visually see how visitors interact, using heatmaps and session recordings. If your new feature is performing way worse than how it should, you can instantly pause the feature release.
Find bugs faster:
As an engineer, you can use visual insights to spot where users struggle, debug feature issues faster, and validate fixes through experiments – so every release is backed by real user behavior, not guesswork.
What can you do, and where to find this?
Integrated behavioral analysis tab in campaign reports:
Every FE campaign report now has a dedicated “Behavioral Analysis” tab with heatmaps, session recordings (for website and mobile apps), pre-filtered to that campaign. No more jumping between tools and context switching.
Access from Insights:
Any heatmap, recording, or funnel in Insights can be filtered by FE campaigns, specific environments, campaign rules, or test variations. That way, you can go deep into behavioral patterns for any experiment you’ve run.
Enter from mobile app recordings & heatmaps:
Extend the same behavioral analysis to mobile app experiments, with screen taps, user flows, and sessions linked directly to your mobile SDK-powered tests.
How does it help your team?
For E-commerce & Retail:
You launched a new product recommendation engine for your mobile app. It lifted AOV, but bounce rate also rose. The recordings reveal users’ attention drifted from purchasing the product, to browsing the “You might also like” section, to check more options. You fix its position, not the algorithm. Without behavior analysis, this insight would have been hidden.
For SaaS & Software:
The trial onboarding test for your webapp is failing, but the metrics don’t explain why. Using session recordings and heatmaps, you spot a clear drop-off happening at the second step of the flow. Users took a lot of time entering their webpage URLs to configure your product, and when they entered, there were many rage clicks on the “proceed” button. With that insight, you’d know for which field you need to reduce friction in the trial flow (maybe add a regex option for URLs). That way, you catch the flaw before it drags the lead count down.
For News & Media:
Heatmaps could reveal that in the test, where you are testing a new ad placement section, the ads are getting drastically low clicks. Session recordings reveal that users are seeing a cookie consent pop-up on top of it. Rookie mistake, yes. Happens to everyone, but would you have known the reason by just looking at statistical numbers?
See the full picture of your experiments today.
Behavior Analytics in Feature Experimentation is rolling out now to all customers on Pro & Enterprise plans of both Feature Experimentation and Insights.
To get started, open an Feature Experimentation campaign report and click the new “Behavioral Analysis” tab.
Questions or feedback?
Reach out to your Customer Success Manager, or email us at [email protected].
We’re all ears.
Original source - Jun 1, 2026
- Date parsed from source:Jun 1, 2026
- First seen by Releasebot:Sep 17, 2026
Optimization just got 10x faster, deeper, and scalable. Introducing Wingify AI.
VWO introduces Wingify AI Chat, an early access AI assistant that helps users summarize insights, explore friction, launch experiments, and create stakeholder-ready reports from tests, recordings, heatmaps, and connected data sources.
Hours, days, weeks – How long does it practically take to gather insights from user interactions, brainstorm about what would solve their friction, and execute that strategy?
That’s the question we asked ourselves, and one of us thought –
Why not just a few moments?
Sounded ambitious to us too, until we actually built it.
Introducing Wingify AI Chat.
Now you can just talk to Wingify AI about everything you know about your users.
Every interaction, friction, feedback – everything!
Ask for a quick recap of what you’ve optimized, check the status of your projects, summarize what your users have been doing lately, get ideas on what to optimize next, launch experiments, or quite honestly, get anything done that feels like grunt work to you.It’s like having a personal CRO assistant. One who has read every report, watched every user interaction, and knows what works & what doesn’t.
How exactly do we help you optimize experiences faster?
Compress hours of analysis: Get summarized, filtered answers about how users interact. Whether you want to see how users from a specific country behaved in a test, or investigate the reasons behind why users bounced off without buying, just ask away!
Let Wingify AI do the insight hunting, while you focus on strategy.Eliminate human errors: We can only analyze so much at once. But Wingify AI can scan millions of signals across user behavior & test results, to identify hidden optimization opportunities you’d never spot manually. Nothing slips through.
Turn insights into action instantly: The gap between “knowing what’s wrong” with your user experience and “fixing it” just vanished. Find a friction point and launch a test to validate your idea, all in the same conversation. No clicking through menus, no switching tabs.
Make the optimization process more efficient: Whether you’re a solo operator or leading a team, Wingify AI multiplies your capacity. Junior team members can pull nuanced insights that would have needed years of experience to spot, and operate at a much deeper level. Experienced seniors can get snippet summaries, and oversee the program efficiently.
What are the possibilities?
Wingify AI can help you:
Catch user friction faster:
Example: “Where are users dropping off most frequently in our checkout funnel, and what’s causing it?”
The AI looks across your funnel data, session recordings, and heatmaps, spots the exact step where people leave, and connects it to what they were doing right before they left.Try it yourself – Interactive demo
Get detailed report summaries:
Example: “Summarize all the campaigns I’ve run on my pricing page, and tell me what has worked, and what has caused drop-offs.”
The AI goes through every test you’ve run on that page, compares the results, understands the patterns, and tells you what lifted conversions, what caused dropoffs, and what you can learn from both.Try it yourself – Interactive demo
Get practical optimization recommendations:
Example: “Give me the top 3 high-impact changes to reduce friction on our product pages, based on both heatmaps and recordings.”
The AI watches how users surfed your pages, spots the moments of hesitation or confusion, and suggests the fixes based on what has worked for you in the past, not generic tips.Try it yourself – Interactive demo
Get stakeholder-ready reports:
Example: “Create a monthly summary of our tests, and evolved changes in user behavior patterns. I need to share it with my leadership.”
The AI gathers your test results of the month, combines them with how user behavior changed incrementally, and structures it all into a clean summary that you can share with your team lead. No more drafting your “work summary” every month.Try it yourself – Interactive demo
Most AI tools give answers. We show you the full picture.
Reference specific tests and personalization campaigns: Type # followed by a test or a personalization campaign’s name to instantly pull in context. Ask “Why did #homepage-redesign-test underperform?” and the AI will analyze that specific experiment.
Call specific AI agents in your prompts: Type @recordings to focus on session data. Want heatmap analysis? Use @heatmaps.
You control exactly which data the AI draws from.
You can create these custom AI agents specific to your use cases. Use available tools like heatmaps, session recordings, campaign analysis, web search, UX analysis, ROI analysis, and many more!Attach files and images to give deeper context for AI: Upload screenshots, competitor pages, or design mockups. The AI can analyze visual content alongside your data, so that it stays context-rich and gives highly relevant responses.
Find patterns and chat with the data from third-party platforms: Connect to GA4, Mixpanel, Amplitude, Notion, Sentry, or Semrush, and prompt what you want to know about your users. Discover hidden patterns that would otherwise go unnoticed.
How does it help your business?
For E-commerce & Retail:
Prompt:
“Compare the checkout behavior of users who converted during Black Friday versus those who abandoned. What friction points were unique to the high-traffic period?”
The AI can find the what, why, and where to ensure you know how your Black Friday sale performed.For SaaS & Software:
Prompt:
“Which user segments saw the biggest drop in trial conversion this quarter, and what changed in their product experience?”
The AI can discover hidden user cohorts that showed confusion in your test variations, study their behavioral patterns, detect the unseen reason behind this drop-off, and suggest how it can be fixed, for higher trial conversions.For News & Media:
Prompt:
“For which cohorts did increasing paywall limit work, instead of discounting the subscription price?”
The AI can reveal behavior patterns of specific users, so that you align your editorial and product teams on a data-backed optimization strategy for higher retention.Get smarter at optimizing today.
Wingify AI is currently available for early access.To request early access, please reach out to your Customer Success Manager, or drop us a note at [email protected].
We’ve put together a playbook for you to get started. Click here to start exploring!
Original source - Jun 1, 2026
- Date parsed from source:Jun 1, 2026
- First seen by Releasebot:Jun 11, 2026
Optimization just got 10x faster, deeper, and scalable. Introducing VWO AI.
VWO introduces AI Chat, an early-access assistant that helps teams query user behavior, summarize tests, spot friction, and launch experiments faster. It also supports custom AI agents, file uploads, and connections to tools like GA4, Mixpanel, Amplitude, Notion, Sentry, and Semrush.
Hours, days, weeks – How long does it practically take to gather insights from user interactions, brainstorm about what would solve their friction, and execute that strategy?
That’s the question we asked ourselves, and one of us thought –
Why not just a few moments?
Sounded ambitious to us too, until we actually built it.
Introducing VWO AI Chat.
Now you can just talk to VWO AI about everything you know about your users.
Every interaction, friction, feedback – everything!
Ask for a quick recap of what you’ve optimized, check the status of your projects, summarize what your users have been doing lately, get ideas on what to optimize next, launch experiments, or quite honestly, get anything done that feels like grunt work to you.
It’s like having a personal CRO assistant. One who has read every report, watched every user interaction, and knows what works & what doesn’t.
How exactly do we help you optimize experiences faster?
Compress hours of analysis: Get summarized, filtered answers about how users interact. Whether you want to see how users from a specific country behaved in a test, or investigate the reasons behind why users bounced off without buying, just ask away!
Let VWO AI do the insight hunting, while you focus on strategy.
Eliminate human errors: We can only analyze so much at once. But VWO AI can scan millions of signals across user behavior & test results, to identify hidden optimization opportunities you’d never spot manually. Nothing slips through.
Turn insights into action instantly: The gap between “knowing what’s wrong” with your user experience and “fixing it” just vanished. Find a friction point and launch a test to validate your idea, all in the same conversation. No clicking through menus, no switching tabs.
Make the optimization process more efficient: Whether you’re a solo operator or leading a team, VWO AI multiplies your capacity. Junior team members can pull nuanced insights that would have needed years of experience to spot, and operate at a much deeper level. Experienced seniors can get snippet summaries, and oversee the program efficiently.
What are the possibilities?
VWO AI can help you:
Catch user friction faster:
Example: “Where are users dropping off most frequently in our checkout funnel, and what’s causing it?”
The AI looks across your funnel data, session recordings, and heatmaps, spots the exact step where people leave, and connects it to what they were doing right before they left.
Try it yourself – Interactive demo
Get detailed report summaries:
Example: “Summarize all the campaigns I’ve run on my pricing page, and tell me what has worked, and what has caused drop-offs.”
The AI goes through every test you’ve run on that page, compares the results, understands the patterns, and tells you what lifted conversions, what caused dropoffs, and what you can learn from both.
Try it yourself – Interactive demo
Get practical optimization recommendations:
Example: “Give me the top 3 high-impact changes to reduce friction on our product pages, based on both heatmaps and recordings.”
The AI watches how users surfed your pages, spots the moments of hesitation or confusion, and suggests the fixes based on what has worked for you in the past, not generic tips.
Try it yourself – Interactive demo
Get stakeholder-ready reports:
Example: “Create a monthly summary of our tests, and evolved changes in user behavior patterns. I need to share it with my leadership.”
The AI gathers your test results of the month, combines them with how user behavior changed incrementally, and structures it all into a clean summary that you can share with your team lead. No more drafting your “work summary” every month.
Try it yourself – Interactive demo
Most AI tools give answers. We show you the full picture.
Reference specific tests and personalization campaigns: Type # followed by a test or a personalization campaign’s name to instantly pull in context. Ask “Why did #homepage-redesign-test underperform?” and the AI will analyze that specific experiment.
Call specific AI agents in your prompts: Type @recordings to focus on session data. Want heatmap analysis? Use @heatmaps.
You control exactly which data the AI draws from.
You can create these custom AI agents specific to your use cases. Use available tools like heatmaps, session recordings, campaign analysis, web search, UX analysis, ROI analysis, and many more!
Attach files and images to give deeper context for AI: Upload screenshots, competitor pages, or design mockups. The AI can analyze visual content alongside your data, so that it stays context-rich and gives highly relevant responses.
Find patterns and chat with the data from third-party platforms: Connect to GA4, Mixpanel, Amplitude, Notion, Sentry, or Semrush, and prompt what you want to know about your users. Discover hidden patterns that would otherwise go unnoticed.
How does it help your business?
For E-commerce & Retail:
Prompt:
“Compare the checkout behavior of users who converted during Black Friday versus those who abandoned. What friction points were unique to the high-traffic period?”
The AI can find the what, why, and where to ensure you know how your Black Friday sale performed.
For SaaS & Software:
Prompt:
“Which user segments saw the biggest drop in trial conversion this quarter, and what changed in their product experience?”
The AI can discover hidden user cohorts that showed confusion in your test variations, study their behavioral patterns, detect the unseen reason behind this drop-off, and suggest how it can be fixed, for higher trial conversions.
For News & Media:
Prompt:
“For which cohorts did increasing paywall limit work, instead of discounting the subscription price?”
The AI can reveal behavior patterns of specific users, so that you align your editorial and product teams on a data-backed optimization strategy for higher retention.
Get smarter at optimizing today.
VWO AI is currently available for early access.To request early access, please reach out to your Customer Success Manager, or drop us a note at [email protected].
We’ve put together a playbook for you to get started.
Click here to start exploring!
Original source - Apr 3, 2026
- Date parsed from source:Apr 3, 2026
- First seen by Releasebot:Oct 16, 2026
Move beyond individual wins. Understand the true impact of your feature releases.
VWO adds Holdouts to Feature Management, giving Enterprise teams a stable baseline to measure the combined impact of feature rollouts, experiments, and personalization campaigns on business outcomes.
Your checkout team ships a winner. Your search team launches a hit.
The individual test reports are glowing green, but when the quarterly review hits, you see little to no impact on your revenue.
Why? Because your “winning” updates might be silently colliding, and there’s no way to know if they are.
You are left wondering:
“Is our product roadmap ‘actually’ delivering the impact?”
Enter Holdouts
Now you can exclude a small, intentional subset of your traffic from a series of new feature rollouts, experiments, and personalization campaigns, over weeks, months, or quarters.
This subset acts as a pure, stable baseline and represents exactly what user behavior would look like if you didn’t deploy any product changes.
How to use Holdouts?
Setting up a Holdout in Wingify is seamless and fits right into your existing workflow. By associating a holdout with your feature flags, it universally works across all your feature rollouts, personalizations, and experiments.
We offer two types of Holdouts:
Global Holdouts:
Automatically exclude your Holdout users from all new feature flags across your product to measure your entire roadmap’s impact.Selective Holdouts:
Manually associate specific feature flags to your Holdouts to measure the combined impact of a specific theme or initiative.
Once active, you get a definitive, dashboard-level view comparing total visitors, conversions, and primary metric values between the Holdouts and users bucketed in your campaigns overall.
How does it help your industry?
- For E-commerce & Retail:
Imagine you launch guest checkout, revamp your recommendation algorithm, introduce an enhanced search experience, revamp the product listing page, and evolve the search experience, all in a single quarter. Individual A/B tests for each, can’t prove the cumulative bottom-line impact. By keeping a set of users that are isolated from these releases, you get scientific proof about these releases, whether they are even increasing your conversions, AOV, or revenue. - For SaaS & Software:
Move the conversation from “Did a specific onboarding change win?” to “Did our Q3 product roadmap actually increase user retention and Customer Lifetime Value?” You finally have the data to prove your strategy works. - For News & Media:
If you launch a new personalization algorithm for the news feed, a metered paywall, and start testing a new ad platform, make a few UI/UX changes, and revamp article writing style, in a single quarter. Such individual A/B tests can’t prove cumulative impact on engagement & revenue. By having the Holdout users as your original baseline, you get a clear indication of the impact of your launches.
Why is this important to you?
Justify your product investments and illustrate ROI:
Solve your leadership’s biggest struggle: “Tangibly understanding the ROI of product development.” Deliver a data-backed analysis to prove exactly how your development efforts are impacting key business goals.
Proactively detect anomalies and course-correct:
Get an early warning if your recent series of improvements is actually causing unintended harm and trending negatively. This allows your team to intervene and course-correct before long-term damage occurs.
Set a culture of true accountability:
Use Holdouts to bring transparency and align your teams towards one common vision, by tying feature launches directly to business health. You shift your team’s mindset from simply shipping features to actually driving business outcomes.
Start visualizing your true roadmap ROI today!
Holdouts are currently available for the Enterprise Plan of Wingify Feature Management. Please reach out to your Customer Success Manager to get access.
To know more, head over to our Knowledge Base.
If you have any questions or feedback, we are all ears at [email protected].
Original source - Apr 3, 2026
- Date parsed from source:Apr 3, 2026
- First seen by Releasebot:Sep 17, 2026
Move beyond individual wins. Understand the true impact of your feature releases.
VWO introduces Holdouts for Feature Experimentation, giving teams a stable baseline to measure the combined impact of rollouts, experiments, and personalization campaigns across weeks or quarters and better understand true roadmap ROI.
Your checkout team ships a winner.
The individual test reports are glowing green, but when the quarterly review hits, you see little to no impact on your revenue.
Why? Because your “winning” updates might be silently colliding, and there’s no way to know if they are.
You are left wondering:
“Is our product roadmap ‘actually’ delivering the impact?”
Enter Holdouts
Now you can exclude a small, intentional subset of your traffic from a series of new feature rollouts, experiments, and personalization campaigns, over weeks, months, or quarters.
This subset acts as a pure, stable baseline and represents exactly what user behavior would look like if you didn’t deploy any product changes.
How to use Holdouts?
Setting up a Holdout in Wingify is seamless and fits right into your existing workflow. By associating a holdout with your feature flags, it universally works across all your feature rollouts, personalizations, and experiments.
We offer two types of Holdouts:
Global Holdouts: Automatically exclude your Holdout users from all new feature flags across your product to measure your entire roadmap’s impact.
Selective Holdouts: Manually associate specific feature flags to your Holdouts to measure the combined impact of a specific theme or initiative.
Once active, you get a definitive, dashboard-level view comparing total visitors, conversions, and primary metric values between the Holdouts and users bucketed in your campaigns overall.
How does it help your industry?
For E-commerce & Retail:
Imagine you launch guest checkout, revamp your recommendation algorithm, introduce an enhanced search experience, revamp the product listing page, and evolve the search experience, all in a single quarter. Individual A/B tests for each, can’t prove the cumulative bottom-line impact. By keeping a set of users that are isolated from these releases, you get scientific proof about these releases, whether they are even increasing your conversions, AOV, or revenue.
For SaaS & Software:
Move the conversation from “Did a specific onboarding change win?” to “Did our Q3 product roadmap actually increase user retention and Customer Lifetime Value?” You finally have the data to prove your strategy works.
For News & Media:
If you launch a new personalization algorithm for the news feed, a metered paywall, and start testing a new ad platform, make a few UI/UX changes, and revamp article writing style, in a single quarter. Such individual A/B tests can’t prove cumulative impact on engagement & revenue. By having the Holdout users as your original baseline, you get a clear indication of the impact of your launches.
Why is this important to you?
Justify your product investments and illustrate ROI:
Solve your leadership’s biggest struggle: “Tangibly understanding the ROI of product development.” Deliver a data-backed analysis to prove exactly how your development efforts are impacting key business goals.
Proactively detect anomalies and course-correct:
Get an early warning if your recent series of improvements is actually causing unintended harm and trending negatively. This allows your team to intervene and course-correct before long-term damage occurs.
Set a culture of true accountability:
Use Holdouts to bring transparency and align your teams towards one common vision, by tying feature launches directly to business health. You shift your team’s mindset from simply shipping features to actually driving business outcomes.
Start visualizing your true roadmap ROI today!
Holdouts are currently available for the Enterprise Plan (Early access) of Wingify Feature Experimentation. Please reach out to your Customer Success Manager to get access.
To know more, head over to our Knowledge Base.
If you have any questions or feedback, we are all ears at [email protected].
Original source - Apr 3, 2026
- Date parsed from source:Apr 3, 2026
- First seen by Releasebot:Apr 3, 2026
Move beyond individual wins. Understand the true impact of your feature releases.
VWO introduces Holdouts for Feature Experimentation, giving teams a stable baseline to measure the true impact of feature rollouts, experiments, and personalization across the full roadmap. It helps compare visitors, conversions, and primary metrics to reveal real business lift.
Your checkout team ships a winner. Your search team launches a hit.
The individual test reports are glowing green, but when the quarterly review hits, you see little to no impact on your revenue.Why? Because your “winning” updates might be silently colliding, and there’s no way to know if they are.
You are left wondering:
“Is our product roadmap ‘actually’ delivering the impact?”Enter Holdouts.
Now you can exclude a small, intentional subset of your traffic from a series of new feature rollouts, experiments, and personalization campaigns, over weeks, months, or quarters.
This subset acts as a pure, stable baseline and represents exactly what user behavior would look like if you didn’t deploy any product changes.How to use Holdouts?
Setting up a Holdout in VWO is seamless and fits right into your existing workflow. By associating a holdout with your feature flags, it universally works across all your feature rollouts, personalizations, and experiments.
We offer two types of Holdouts:
Global Holdouts: Automatically exclude your Holdout users from all new feature flags across your product to measure your entire roadmap’s impact.
Selective Holdouts: Manually associate specific feature flags to your Holdouts to measure the combined impact of a specific theme or initiative.
Once active, you get a definitive, dashboard-level view comparing total visitors, conversions, and primary metric values between the Holdouts and users bucketed in your campaigns overall.
How does it help your industry?
For E-commerce & Retail:
Imagine you launch guest checkout, revamp your recommendation algorithm, introduce an enhanced search experience, revamp the product listing page, and evolve the search experience, all in a single quarter. Individual A/B tests for each, can’t prove the cumulative bottom-line impact. By keeping a set of users that are isolated from these releases, you get scientific proof about these releases, whether they are even increasing your conversions, AOV, or revenue.
For SaaS & Software:
Move the conversation from “Did a specific onboarding change win?” to “Did our Q3 product roadmap actually increase user retention and Customer Lifetime Value?” You finally have the data to prove your strategy works.
For News & Media:
If you launch a new personalization algorithm for the news feed, a metered paywall, and start testing a new ad platform, make a few UI/UX changes, and revamp article writing style, in a single quarter. Such individual A/B tests can’t prove cumulative impact on engagement & revenue. By having the Holdout users as your original baseline, you get a clear indication of the impact of your launches.
Why is this important to you?
Justify your product investments and illustrate ROI:
Solve your leadership’s biggest struggle: “Tangibly understanding the ROI of product development.” Deliver a data-backed analysis to prove exactly how your development efforts are impacting key business goals.Proactively detect anomalies and course-correct:
Get an early warning if your recent series of improvements is actually causing unintended harm and trending negatively. This allows your team to intervene and course-correct before long-term damage occurs.Set a culture of true accountability:
Use Holdouts to bring transparency and align your teams towards one common vision, by tying feature launches directly to business health. You shift your team’s mindset from simply shipping features to actually driving business outcomes.Start visualizing your true roadmap ROI today!
Holdouts are currently available for the Enterprise Plan (Early access) of VWO Feature Experimentation. Please reach out to your Customer Success Manager to get access.
To know more, head over to our Knowledge Base.
If you have any questions or feedback, we are all ears at [email protected].
Original source - Mar 27, 2026
- Date parsed from source:Mar 27, 2026
- First seen by Releasebot:Sep 17, 2026
Introducing Wingify Pulse: Understand Why Users Behave the Way They Do
VWO launches Wingify Pulse, a new Voice of Customer product that captures contextual feedback in the moment, turns responses into AI-powered insights, and supports continuous surveys, concept tests, and closed-loop workflows with VWO experiments.
We’re excited to announce Wingify Pulse, a new Voice of Customer product that helps you capture contextual feedback at the right time, from your users and automatically turn it into actionable insights.
What Wingify Pulse does?
Capture feedback in the moment, across channels
Capture feedback at the point of experience and not days later via email. Pulse lets you deploy surveys inside your web app, mobile app, or via shareable links, triggered by the exact behavior or moment you care about.
Run continuous feedback programs without spamming users
Build continuous feedback loops such as NPS tracking, onboarding checks or feature adoption surveys, that run automatically without over-surveying users.
Pulse’s fatigue controls let you set frequency limits, “only once” rules, and cross-survey coordination to protect user experience and data quality.
From thousands of responses to clear patterns in minutes
With Wingify’s Copilot, teams no longer have to spend hours reading through thousands of open-text responses. Pulse automatically categorizes feedback based on theme and sentiment, and provides user patterns in minutes, not hours.
Get user buy-in before you spend time on developing features
Run unmoderated concept tests to get feedback on designs or prototypes from your users, before spending time on engineering effort. This helps reduce the risk of building features users don’t want.
Close the loop from insight to experiment in one platform
By integrating with the Wingify platform, teams can setup a closed-loop workflow
- Observe and spot the friction in user experience.
- Ask by triggering Pulse at that moment.
- Hypothesize based on feedback themes and form ideas.
- Test the ideas via experiments run on VWO.
- Validate the results by sending a post-test survey.
- Launch the variation with confidence.
Here’s what’s coming for Wingify Pulse subscribers:
- Uncover hidden themes automatically with AI-powered topic extraction and categorization across all your responses.
- Get instant clarity on what users are saying via AI-generated summaries that synthesize feedback into actionable themes.
- Track metrics that matter with custom dashboards that let you visualize and monitor feedback trends your way.
- Connect feedback directly to action through integration with Wingify Insights, Testing, and more.
- View user feedback in one place by consolidating support tickets, app reviews, and other feedback sources into a single view.
Get Started
Explore Wingify Pulse- You’ll see the new Pulse section in your left navigation in the product tab.
If you want a walkthrough tailored to your needs, book a personalized demo anytime. You could also read this KB article that will give you a deeper understanding of Pulse.
Original source - Mar 27, 2026
- Date parsed from source:Mar 27, 2026
- First seen by Releasebot:Mar 27, 2026
Introducing VWO Pulse: Understand Why Users Behave the Way They Do
VWO launches Pulse, a new Voice of Customer product that captures contextual feedback across web, mobile and shareable links, turns responses into AI-driven insights, and connects feedback to experimentation in one platform.
We’re excited to announce VWO Pulse, a new Voice of Customer product that helps you capture contextual feedback at the right time, from your users and automatically turn it into actionable insights.
What VWO Pulse does?
Capture feedback in the moment, across channels
Capture feedback at the point of experience and not days later via email. Pulse lets you deploy surveys inside your web app, mobile app, or via shareable links, triggered by the exact behavior or moment you care about.
Run continuous feedback programs without spamming users
Build continuous feedback loops such as NPS tracking, onboarding checks or feature adoption surveys, that run automatically without over-surveying users.
Pulse’s fatigue controls let you set frequency limits, “only once” rules, and cross-survey coordination to protect user experience and data quality.
From thousands of responses to clear patterns in minutes
With VWO’s Copilot, teams no longer have to spend hours reading through thousands of open-text responses. Pulse automatically categorizes feedback based on theme and sentiment, and provides user patterns in minutes, not hours.
Get user buy-in before you spend time on developing features
Run unmoderated concept tests to get feedback on designs or prototypes from your users, before spending time on engineering effort. This helps reduce the risk of building features users don’t want.
Close the loop from insight to experiment in one platform
By integrating with the VWO platform, teams can setup a closed-loop workflow
- Observe and spot the friction in user experience.
- Ask by triggering Pulse at that moment.
- Hypothesize based on feedback themes and form ideas.
- Test the ideas via experiments run on VWO.
- Validate the results by sending a post-test survey.
- Launch the variation with confidence.
Here’s what’s coming for VWO Pulse subscribers:
- Uncover hidden themes automatically with AI-powered topic extraction and categorization across all your responses.
- Get instant clarity on what users are saying via AI-generated summaries that synthesize feedback into actionable themes.
- Track metrics that matter with custom dashboards that let you visualize and monitor feedback trends your way.
- Connect feedback directly to action through integration with VWO Insights, Testing, and more.
- View user feedback in one place by consolidating support tickets, app reviews, and other feedback sources into a single view.
Get Started
Explore VWO Pulse- You’ll see the new Pulse section in your left navigation in the product tab.
If you want a walkthrough tailored to your needs, book a personalized demo anytime. You could also read this KB article that will give you a deeper understanding of Pulse.
Original source - Feb 3, 2026
- Date parsed from source:Feb 3, 2026
- First seen by Releasebot:Sep 17, 2026
Go SDK for Feature Experimentation: How Wingify Enables Safe, Low-Latency Backend Releases
VWO launches a full Go SDK for teams building Golang applications, bringing low-latency feature experimentation and release control directly into apps without the Wingify Gateway Service. It also adds MCP Server, VS Code support, and flag cleanup tools.
Note
Wingify recently launched a full Go SDK for teams building Golang applications, enabling low-latency performance and native capabilities without relying on the Wingify Gateway Service.
Shipping backend changes has never been about writing code alone. It is about managing risk, coordinating teams, and making sure performance never drops, especially when the code runs in business-critical paths.
For teams building in Go, those constraints are even tighter.
The Wingify Go SDK enables experimentation and feature control directly within your Go application, without introducing latency, complexity, or operational overhead. It allows teams to ship more frequently while staying safe, observable, and in control.
Release management that fits real engineering teams
One of the biggest shifts we see in mature engineering organizations is the move away from tying every change to a deployment. Teams want to decouple engineering effort from product and configuration changes, so they can release continuously without putting production at risk.
With the Go SDK, feature flags and experiments become part of the runtime, not the release event. Backend teams can roll out new logic gradually, pause changes instantly if something goes wrong, or run controlled experiments on high-impact systems like pricing, search, recommendations, or subscriptions. This makes release management calmer, without slowing teams down.
Easy to integrate, easy to live with
The Go SDK is lightweight and is designed to drop into existing services without retooling.
Integration is straightforward, and once in place, the SDK stays out of the way. Teams can monitor, manage, and evolve experiments using REST APIs, IDE integrations, and clear, example-driven documentation. Whether you are running a monolith, a microservice, or an event-driven system, the Go SDK adapts to your environment rather than the other way around.
Execution support that works with your stack
Modern backend systems rarely exist in isolation. They connect to frontends, mobile apps, data pipelines, and third-party services.
The Go SDK supports OpenFeature and integrates cleanly with existing delivery pipelines. This ensures targeting logic and feature behavior remain consistent across platforms, while letting teams adopt experimentation incrementally. Wingify augments what you already have; it does not replace it.
Governance without slowing development
Speed and governance do not have to be opposites.
With Wingify Feature Experimentation, teams can define role-based access, approval flows, and environment-specific permissions. Production remains tightly controlled, while development and staging environments can be opened up for faster collaboration using Open Access. This allows developers to move quickly where it is safe, while leadership retains confidence where it matters most.
Performance first, always
For backend teams, performance is non-negotiable.
The Go SDK evaluates feature flags entirely in memory, using local data. There are no network calls in the request path, which means decisions happen in sub-millisecond time. Even in high-throughput services, experimentation adds no measurable latency and introduces no runtime dependency on external systems.
This makes the Go SDK safe for critical flows, from checkout and pricing to authentication and personalization.
Keeping experimentation clean over time
As teams experiment more, feature flags can pile up. Without discipline, this leads to dead code and long-term technical debt.
Wingify includes specialized tools and workflow integrations that help teams identify stale or unused flags, clean them up confidently, and prevent flag sprawl from becoming a problem. Experimentation stays structured and intentional, even as it scales.
In addition to flag hygiene features built into feature workflows, Wingify also offers a Tech Debt Client that helps teams take a proactive stance on managing technical clutter. This client analyzes your codebase and checks how Wingify feature flags are being used, generating actionable recommendations that guide teams toward removing unused or redundant flags. By surfacing where flags aren’t referenced or are no longer serving a purpose, the Tech Debt Client reduces uncertainty around clean-up decisions and helps teams maintain a lean, intentional experimentation layer as their codebase and test portfolio scale.
Complementing cleanup tooling, the Wingify MCP (Model Context Protocol) Server bridges your development environment with Wingify’s feature experimentation system so developers can manage flags directly where they code, without context-switching.
It supports AI-powered IDE integrations, letting teams create, list, update, delete, and toggle feature flags in familiar tools like Cursor or VS Code, and ensures consistent control across environments. This server makes flag operations more fluid and accessible, improving workflows and reducing overhead while giving dev teams tighter command over feature release logic and lifecycle.
Developer experience
A recurring theme in modern development is context switching, or more accurately, the desire to avoid it.
Wingify’s developer experience is designed so that feature experimentation lives exactly where developers already spend their time.
Feature flags inside VS Code
With the Wingify VS Code extension, developers can view, toggle, and manage feature flags without leaving their editor. Flags can be enabled or disabled instantly, environments can be switched from the status bar, and SDK code snippets can be inserted automatically.
Instead of treating feature management as a separate task, it becomes part of the coding workflow.
MCP Server and AI-native workflows
As AI becomes a daily development companion, feature management needs to integrate with it naturally.
Wingify’s MCP Server brings feature experimentation directly into AI-powered IDEs like Cursor and Copilot Workspace. From within the IDE, AI agents can create flags on the fly, wrap code blocks, configure experiments, suggest exposure rules, and even help monitor rollout impact.
Developers can also bootstrap SDK integrations instantly. With a single command, MCP Server configures Cursor rules, generates language-specific SDK examples, and ensures best-practice implementations from the start. Installation is intentionally simple, requiring nothing more than an npx command and Wingify credentials.
Over time, MCP Server also helps teams stay clean by scanning codebases for stale or unused flags, reducing technical debt before it accumulates.
One SDK, every stack
The Go SDK is part of a broader, full-stack experimentation ecosystem. Wingify supports Go alongside Ruby, NodeJS, Java, .NET, Python, and more, and works seamlessly with code generated by tools like Cursor, Windsurf, Antigravity, or Replit.
No matter where your logic runs, experimentation behaves consistently.
Why this matters
Together, the Go SDK, MCP Server, and Wingify Feature Experimentation enable teams to treat experimentation as an engineering capability, not a risky add-on.
Teams ship faster without losing control, experiment deeply without hurting performance, and scale optimization without creating chaos. Feature flags become clean, intentional, and easy to manage, even in complex systems.
For Go teams building high-performance, business-critical systems, this is experimentation done right.
Get started
Get started with Wingify Feature Experimentation and start shipping features with more confidence, cleaner workflows, and faster learning from day one.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.