Good testing and personalisation platform, not suitable as one-stop-shop
Updated January 02, 2018

Good testing and personalisation platform, not suitable as one-stop-shop

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

Overall Satisfaction with Qubit

Qubit is used to create either A/B tests or personalisation experiences. A/B tests are typically developed by a dedicated person in the Tech team, based on a marketing request. They are not meant to be reusable. Personalisation experiences (e.g. banners, marquees, etc.) are created by a dedicated person in the Tech Team, based on a marketing request. They are then reused and modified by the marketing team to update the copy, images, triggers, etc.
  • A/B tests for front-end related changes.
  • Complex experience personalisation (requiring coding).
  • Complex management of segments.
  • DIY/Marketing-friendly personalisation.
  • Multi-variate test or complex test setup.
  • Programmatic experiences.
We use Qubit to deliver A/B tests, which have allowed us to improve our conversion rates and revenue per visitor by testing different page layouts / features. We also use Qubit to enable marketers to take control of merchandising experiences (e.g. banner, marquees, etc.), which have been previously created by someone with technical knowledge.
As alternatives to Qubit, we considered:
* Optimizely: more limited personalisation options, more expensive to be used across different sites.
* Maxymiser: more expensive.
* Monetate: slightly better feature set, especially for personalisation or programmatic experiences, but would have required work to migrate datalayer and reconfigure tool - however, remains a contender for the future.
* ContentSquare: more focused on visual analytics and more limited in terms of personalisation.
  • We do not use Qubit as an end-to-end data management platform due to lack of flexibility and high cost.
We have used it to to create more complex segments, looking back in time, to deliver targeted experiences. We have not used it to generate customer insights as the tools/dashboard in the "basic" version of Qubit are too limited and the advanced features are overly expensive - we are instead invested in dedicated data platforms.
Well suited when used by an engineering team to build test or complex personalisation experiences, including with complex segmentation / trigger rules. Not suited to be used as DIY tool by marketers with limited/no technical knowledge. Not suited for server-side testing, including pricing tests. Not suited for complex A/B or MVT tests, due to limited control over test parameters.

Qubit Support

Qubit's technology is pretty good but support doesn't follow. New features are often introduced with limited documentation, no example or use cases. Frequently, our contacts at Qubit do not know how to answer questions about new features or give incorrect information.
Requests to fix issues, look into bugs or support implementation take too long to be answered.
Qubit is best thought of as a self-service tool rather than a service-augmented SaaS.

Using Qubit

Overall, the interface is quite simple to use for marketers and developers alike to configure basic experiences.
However, more complex experiences - especially when using segments and exclusions between different experiences - are much harder to configure and require to use workarounds.
Documentation and self-help is also very limited, making it hard to understand how to use advanced features.

Qubit Reliability

Technology is good for A/B testing and personalisation - allowing any team with a dedicated developer to create test relatively easily and to report/analyse them in a fair amount of details. Some advanced features, especially on the set up of test cells, are dearly missing.
Unfortunately, new features are often not free of bugs...
Also, support is sub-par, which means new features are realised without proper documentation, example or training (but of our Qubit counterparts and internally).

Relationship with Qubit

Working with Qubit after the sale proved relatively easy - the team is approchable and available to answer questions or take feedback.
However, due to lack of visibility on Qubit's roadmap, it is impossible to say whether feedback is actually taken into account or not.
Also, the Qubit team may take a while to answer simple questions, as the primary contacts usually do not have the skills to answer them directly and have to escalate them to the engineering team.