Item: Coveo Qubit
Rating: 10
Author: David Pert

Overall Satisfaction with Qubit

Use Cases and Deployment Scope

We have been using QuBit in two primary ways;
1) Test conversion rate optimisation changes to the user experience, primarily the purchase journey (without requiring development/site releases)
2) Manage and test changes to on-site promotional banners. Including the addition of banners/messages in locations which our current CMS is not able to.

Pros and Cons

Pros

A/B testing of complex changes to the customer journey (as opposed to simple/show/hid/change colour tests)
Providing a development stream which can run independently from standard development (therefore maximising resource capacity)

Cons

The tool is clearly very powerful, but the most impressive changes require javascript coding to implement. One of the key benefits of QuBit is the ability to make site changes without needing development resource, so this creates a catch 22 of sorts. Adding more capability to the non-coding interface would be a real advantage.

Alternatives Considered

Primarily reference from companies I know who do A/B testing/CRO well. Speed of implementation was a factor, as was the excellent support of the on boarding/account management team.

Other Software Used

Bronto Marketing Platform, Google Analytics Premium

Likelihood to Recommend

In order to fully utilise QuBit, the company using it should ideally have the following;
- Semi-dedicated resource to set up, refine and report on tests. There's no limit to the number of tests which can be set up so maximising volume is key to getting the most value from the tool. Simple variations to the test setup/user experience delivered can make the difference between a conversion rate increase or decrease. So allowing for time spent on refining/improving tests is critical.
- Access to Javascript coding resource (ideally with QuBit experience) OR a readiness to invest in QuBit's own Javascript coding resource. QuBit can deliver some very impressive site improvements, but the best ones need JS.
- Visitor volumes of around 250,000 per month or more. Lower than this means that tests take a very long time to deliver statistically sound test results. At around 100,000 sessions per month or less, many tests will not be able to deliver meaningful results for months.

Comments

Please log in to join the conversation

George Barker
commented 8 years ago
Hi David, Firstly, thanks for writing this very detailed review of the Qubit platform - I've been able to share it with all the teams internally who can both learn and understand how we can continue to make Qubit better. Your insight around visitor volumes and resource is something we're looking to fix in upcoming updates. We're glad to hear that delivering changes is so quick and that you've made some 'no brainer' decisions backed up by the data. Any questions - just let us know. George, Customer Advocacy, Qubit.

Powerful tool, requires time investment (but worth the effort)