Ups and Downs with VWO
December 07, 2018

Ups and Downs with VWO

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with VWO

We use VWO for A/B testing smaller features on site (e.g. hiding some text) and split testing with larger features (e.g. layout and image changes). It's primarily used by engineering currently, but we are trying to move priorities to product and marketing (with some constraints) for the majority of tests.

It allows us to make business decisions around the wording of text that's shown, or the user experience around a new UI.
  • General overview of which test variation is doing better
  • Simple A/B and Split URL tests
  • Simple testing mechanics (e.g. blanking the page before simple tests are run like with the WYSIWYG editor)
  • UI/UX for finding certain options are confusing. Even having used the tool for a bit, can't remember where certain editing options are .
  • Bugs with the visual editor and preview mode (having to refresh the page until it works)
  • More complicated tests (which may involve mechanics specific to certain companies)
  • Helps us A/B test features for site improvement
  • Helps us direct traffic to one variation before we implement the feature into code
  • Helps us plan future tests with current test results
At the time we made the decision, these tools didn't allow for AB testing or at least a more built out infrastructure for implementing the testing. They allow us to analyze data though.
Good:
Simple tests like hiding and showing a button, text, etc.
Adding text onto the page
Changing the color of things
Split tests where the whole page can change

Bad:
Complicated tests regarding custom JavaScript that's run (there may be asynchronous actions happening in that script that we need the page blank for until those actions finish)
Want a smarter visual editor (e.g. we can change the layout and the test would still work, by class or id selectors)