Qubit, now from Coveo (acquired October 2021) uses visitor history data to understand different user segments and serve personalized messages to segments using JavaScript. It is available as either a managed or self-service model. Data is collected using Qubit's own Universal Variable data model, or by integrating the user's existing model via our API. It combines quantitative data with qualitative visitor feedback to give Qubit users the ability to detect areas for optimization.
Using…
N/A
IBM API Connect
Score 8.8 out of 10
N/A
IBM API Connect is a scalable API solution that helps organizations implement a robust API strategy by creating, exposing, managing and monetizing an entire API ecosystem across multiple clouds. As businesses embrace their digital transformation journey, APIs become critical to unlock the value of business data and assets. With increasing adoption of APIs, consistency and governance are needed across the enterprise. API Connect aims to help businesses…
In my previous company one of the brands was using Optimizely, while the brand I was working for was using Qubit. Qubit proved to be so much more than a multi-variant platform. It was much easier to use - we didn't have to rely on the tech team to implement tests. This way we …
Key points that keep us close to Qubit are its knowledgeable resources, presentation and UI, ease of getting trained, ease of use, low time to market, analytics and reports.
We're using Qubit as a fully managed testing platform, and their account management and level of service we've received from any other contact (technical, support, sales etc) was above any of their competitors. Integration and on-boarding was well done and we feel confident …
Having previously used Maxymiser around 3 years ago, I found their setup to be geared more away from faster moving retail. While tests would be thoroughly researched and built to a high standard, the length of time to turn around a single test was too long. Qubit has allowed us …
As alternatives to Qubit, we considered: * Optimizely: more limited personalisation options, more expensive to be used across different sites. * Maxymiser: more expensive.
We've chosen Qubit because of the data driven approach, ease of use and the offered support. We like the ability to build some tests externally with the Qubit help.
At the time of taking the product, we found no comparable alternatives. Since then, the product has only grown from strength to strength, so it still does not have any comparable competitors that offer both the technical product and business knowledge that Qubit can. Google …
We previously used Monetate but that was before my time so it's tough to specifically compare. However, I think the fact that we're no longer with Monetate proves that Qubit has been a better partner overall.
Simple usability is a controlled group testing only. Qubit on the other hand allows you to run a test on a live site with traffic ranging from 5% to 95%
Qubit has a nicer UI than Google Tag Manager and offers the A/B testing that GTM doesn't - but for script management, there's not a lot to choose between them.
Qubit is probably the most powerful tool that we reviewed. The challenge is that with the power comes a large responsibility to make sure you are doing it right and not having issues. With digital tools, power and complexity seem to go together so you have to make sure that you …
I was not directly involved in the decision-making process but understand that overall functionality, data integration, and UX testing weighed against the cost of the solution were the deciding factors.
Qubit was the first CRO tool we have used, and have stuck with it, even though we've tested other platforms on our other websites. I think it's a testament to Qubit and their staff that they are still implemented on our largest website.
Primarily the strength of Qubit's data layer and therefore the ability to personalise and create seamless user journeys for our different customer segments.
The decision to use Qubit was made based on the capacity to run a 3 month test before committing for a longer term and down to a recommendation from a sister company.
We were not aware of some of the other offerings from Qubit so I think this is an area that could be improved upon. For us, Qubit is seen as an A/B testing tool more than anything else so I would say that the promotion of additional tools offered by Qubit is certainty something …
Our company decided to choose Qubit due to its perceived similarly to optimizely and promise infinite integrations through open tag. Sadly it didn't live up to its promise. The integrations were not integrations as most people would understand it. It was all very manual and you …
We opted for Qubit due to their personalisation features compared to the other market offering, as we felt their Visitor Cloud was a USP in the industry. The Visitor Cloud allows further personalisations, such as social proofs, to complement internal data we have gathered and …
IBM API Connect can in some use cases, especially when customer requirements are highly security centric, provide a more robust approach to managing access, performance, and trust, in the IT estate. In many cases it boils down to customer preference and to some extent if the …
Our decision to adopt IBM API Connect was driven by its comprehensive end-to-end API lifecycle management, which proved to be exceptionally well-suited to our B2B, Open Banking, and multi-fintech integration requirements. When compared with other solutions, API Connect stood …
Prior to adopting IBM API Connect, there were two main competitors, MuleSoft. Although in the integration capabilities MuleSoft seemed to have an advantage, and regarding developer experience, IBM API Connect had a set of enterprise features for the API management.
Mulesoft seemed to take a lot longer to implement and reach any real ROI attribution. For the other competitors, I'd say they are easier to administrate, but this isn't as important to us as a business user. It was easier to explore APIs with IBM than it was with others.
There were multiple product we read and then shortlist were taken as POC against IBM API Connect. -Google Apigee : is good but in cross cloud there are concerns. Also, feature of reading & identifying the target system certificate was not available there.
It was organizational boundaries to use IBM API Connect but we have learnt so many think on this technology. Obviously, We have more experience on this it;s easy for us to configure and maintain the system.
IBM API Connect have more feature compared to other solutions like from one platform we can create APIs on the API Manager, we can publish the APIs to the products/portal server, we can secure the APIs using IBM DataPower Gateway, we can socalize the APIs using developer …
We use IBM Cloud, which works well with our hybrid cloud deployment. As a large firm, we are able to scale as required once the initial setup is complete.
Coveo Qubit is a very helpful platform mainly for organizations that need to provide a solid business model before carrying out any implementation or new functionality. In addition, it is a very good tool to generate changes and show different content to different types of clients, with their personalization and segmentation criteria.It is ideal for simultaneous testing and customization, only one of these activities individually is not recommended.
Overall, it can be stated that IBM API Connect has many benefits and can easily manage complicated integrations. The platform performs best in large environments, especially where microservices and processing of multiple API dependencies are required. On average, we have processed thousands of API calls within a second with good response time.
The testing platform itself is continually evolving. This means that we are always able to try new ideas as well as quickly and efficiently put others into practice.
The beta programme and the additional functionality products are both exciting to see as well as ensuring we can cherry pick the functionality we need. This means that we don't end up paying for functionality we don't need
Some of the reporting within Qubit has been overly simplified in the past, a point they are continually addressing.
At times the syntax of experience (test) creation can be specific to Qubit and so there is a slight learning curve for developers.
Unless developers have much time to allocate to creating tests in Qubit, marketers may potentially find simple tests limited. I would recommend having someone in-house as we do.
That being stated, every thing you own will have both positive and negative aspects to its use. It can be perplexing at times, particularly when navigating between different functions.
However, based on my usage of this application up until this point, I've discovered that the only time it lags is when it's downloading updates. Otherwise, it's excellent to utilise for all other customs.
Qubit helps out immensely and lays out in plain English the profitability of each of our A-B tests. Say Qubit has provided us overall with a 5% profit increase this year (that is a completely arbitrary figure for illustration only), then if we didn't renew it could be seen as us taking a 5% loss as Qubit wouldn't be there. The results of our tests are showing no slowing down and as Qubit and Toast grow to understand each other better we can only see our performance getting better as the years go on.
Overall navigation on Qubit is very user friendly and requires a minimal training to be up and running. Be it reviewing existing experiences or setting up new experiences, the process is pretty simple for business user. Add some basic development skills to your kitty, you can do magic with Qubit and make your website do wonders!
IBM API Connect may be less appropriate for small-scale projects with minimal API management requirements, where simpler and more cost-effective solutions suffice. Organizations lacking the necessary technical expertise or resources to harness its full potential may face implementation challenges. In static environments with infrequent API changes or limited developer engagement, the platform's comprehensive features may be excessive for the task at hand.
I would say that the Qubit account managers are always available for any request. We have a lot of different promotions that could always do with last minute optimizing or changes and Qubit can be relied on to get this changes up and running in an impressive amount of time, so that we don't need to patch live or wait for the next IT sprint. Invaluable to our business.
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).
Qubit are supportive and flexible in providing support. They are happy working out of usual hours, even on weekends and if I have any doubts about the set up of an experience they’re quick to respond and willing to check my work. On particularly big revenue days they monitor our account and they’re quick to identify and problem solve any issues.
The training was great, but would be great to have a script or PDF with some explanations of the qubit JS layer. Without the script you can just try to learn on your own, so the training is not as powerfull as it could be. On the other hand - would be great to have training related to reading statistics or personalisation.
Implementation couldn't be easier. All we needed to do was insert the tag. (easy) and set up the data layer. (dev required) This was pretty smooth in comparison to some of the other tools we use on our site, and was done in less than a day. Note : Data needs to be collected for a set period of time before you can accurately rely on the data that you are receiving. This is normal though with everyone else that we have used
We're using Qubit as a fully managed testing platform, and their account management and level of service we've received from any other contact (technical, support, sales etc) was above any of their competitors. Integration and on-boarding was well done and we feel confident that the campaigns are developed and tested thoroughly.
Our decision to adopt IBM API Connect was driven by its comprehensive end-to-end API lifecycle management, which proved to be exceptionally well-suited to our B2B, Open Banking, and multi-fintech integration requirements. When compared with other solutions, API Connect stood out for its ability to externalize and govern APIs at scale, while offering enterprise-grade capabilities critical for our regulated environment. IBM App Connect serves as our internal integration middleware, focused on backend orchestration and data transformation. IBM watsonx acts as a complementary AI and data platform for exposing intelligent services especially with the code assistant functionality, it is API Connect that provides the crucial layer for external API exposure, management, and monetization. IBM DataPower is an incredibly secure and performant runtime, and lacks key enterprise features such as developer engagement, full API governance, and analytics. API Connect fills that gap seamlessly, offering a unified, secure, and scalable API management experience.
Our requirements change throughout the year like most E Commerce retailers. At Christmas and Peak we're dealing with around ten times the usual traffic on the site. Qubit had no problems with this at all, tests continued to fire, and stats were still reported accurately. I don't think that it is the most server intensive .js anyway, but we have seen no issues at all.