API v2.0

Welcome to the VWO developer hub. You'll find comprehensive guides and documentation to help you start working with apoorv as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

VWO FullStack lets you do the enterprise-grade serverside testing of your product by deploying code behind features, experiment with A/B tests, and rollout or rollback features immediately. With VWO FullStack, you can literally test anything- be it the search algorithms or recommendation engine for your e-commerce store or subscription workflows for your SaaS business. VWO FullStack is built to help you execute even the most complex tests. It enables you to test on any platform and not just limited to devices that have a browser. Think native apps, beacons, and connected devices.

With VWO FullStack, you can perform the testing wherein the variations of a particular test are rendered directly from the webserver and are then sent to the visitors’ device. Implementing directly on the server allows you to run more sophisticated tests that might otherwise hamper the user experience if implemented on the client-side. In addition to that, serverside testing is also opted for in cases when it is simply unfeasible to experiment on the client-side. For example, testing two different product recommendation algorithms for an eCommerce website.

Typical use cases of VWO FullStack are:

  • A/B Test deep within your stack
  • You can test multiple variations of the feature with a different set of variables
  • Manage Features' Lifecycle With Feature Flag Management
  • Deliver Features Confidently with Staged Feature Rollouts

VWO FullStack enables you to test much deeper. Rather than being limited to testing images or buttons on your website, you can test algorithms, architectures, and re-brands. But for complex applications, client-side testing may not be the best option: Layering more JavaScript on top of an already-bulky application means even slower load time and an even more cumbersome user experience.

Consider the following situation. An eCommerce store owner, with an aim to optimize for better conversions, wants to test two different checkout flows on both his/her website and mobile app at the same time. To do so, they need an advanced testing methodology, which is more inherent to the process and integrates with the website to ensure a seamless user experience. Neither of which is possible by running a simple A/B test on the client-side and that is why serverside testing is required.

Learn More here.

Updated 5 months ago



Overview


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.