VWO FullStack comprises the following features:
Projects let you manage multiple business objectives by keeping a segregated workspace for your teams or applications. You can have multiple projects to manage different parts of your application. For example, you can create one project called Mobile App and another project called Web App.
Using Projects in VWO, you can:
- Choose the SDK language as per your backend server.
- Specify an environment where you want to run the campaigns. Typical environments within a project could be Production, QA, Staging, or individual environments.
A feature represents the functional capabilities of your product that you want to test and roll out. Using Features in VWO, you can typically experiment with the features before you roll them out for your users. VWO lets you deliver a feature in phases instead of making them live to all your users, universally, at once. This way, you can mitigate risk, learn from inconclusive tests faster and iteratively, and as a result, launch features confidently.
Using Features in VWO, you can:
- Create a new feature.
- Define variable(s) for a feature to test or rollout.
A rollout is a gradual launch of a new feature. Sometimes, to ensure a smooth launch, we don't show a new feature to every user at once. Instead, we start with a small percentage of users and increase that percentage over time until 100% of users have the new feature.
Feature Rollout lets you deliver a new feature in incremental phases. It is also referred to as Feature Toggle, which enables you to turn your features ON/OFF and alter user experience without deploying new code. Once rolled out, you can control your features – enable them for some users, disable them for others, hide them for a certain period, and so on. If necessary, you can also roll out an incomplete feature and hide it until you are confident about making it live.
From studying user response around the feature to turning it ON/OFF, all can be done in real-time. For example, as a SaaS company, you can roll out a new feature for your enterprise customers.
Using the Feature Rollout in VWO, you can:
- Turn a feature on or off just by using the toggle control.
- Specify the Environment(s) where your feature will be visible
- Allocate traffic percentage that you want to include in the campaign
Feature Rollouts helps deal with the adverse effects of any feature you are releasing by turning a feature off or adjusting the traffic percentage for a feature. This helps you validate your feature's functionality and performance before you roll it out for all your users. For example, if you are not too sure about a feature's performance, you can turn the feature off using the toggle option.
With Feature Test, you can test a product feature by creating variations with a different set of variables until you are sure you are rolling out the best one. This enables you to thoroughly experiment with them, measure their impact based on critical metrics, and then roll out the winning variation. Most importantly, you get real-time visibility into your products’ features’ performance.
Additionally, you can test multiple variations with different configurations of the feature variables. For example, if you are a SaaS company and want to launch a free trial for your product, you can create multiple variations with different duration of free-trial periods, identify the winning variation and then make it available universally. You can test each of these variants without any manual effort.
Using the Feature Test in VWO, you can:
- Assign variable values in different variations.
- Define a goal to track visitor interaction.
- Allocate the traffic percentage that you want to include in the campaign.
In a Feature Test, you can measure the impact of the feature on your user experience by tracking the metrics.
With the A/B test, you can test the different algorithms, subscription flow, etc., configured from the server. Here, a particular test's variations are rendered directly from the webserver and then premeditatedly sent to the visitors’ device. Implemented directly on the server, these tests allow you to run more complex tests, which may otherwise affect the user experience if run on the client-side.
Additionally, serverside testing is the only answer when it's unfeasible to experiment on the client-side. For example, testing two different product recommendation algorithms for an eCommerce website. Since the algorithm is rendered from the server, a sophisticated serverside testing tool (VWO FullStack) must run this test.
Using the A/B test in VWO, you can overcome issues associated with client-side A/B testing, such as flickering and security concerns with tag integration.