Qubit Reviews

Qubit is used within the e-commerce team to serve targeted functionality, segment live visitors and test UI and UX theories. Currently, it is being used widely to improve international personalisation.

The Digital Commerce team used Qubit to conduct multiple split tests and targeting campaigns on our website. We used the tool to implement both data driven testing initiatives and to provide personalized or custom content in specific scenarios. Qubit's professional services helped us overcome bandwidth limitations in designing and implementing multiple campaigns.

We use Qubit to gather user feedback, analyse user behaviour, form hypothesis and build MVT and A/B tests and finally, monitor the results. The platform is predominately used within the eCommerce department however test results are shared throughout the organisation and ideas are encouraged from all staff.

Using Qubit allows us to quickly test new ideas; helps us make important design decisions; gives us a better understanding of what influences buying behaviour, helps steer our development roadmap and most importantly, improves overall conversion.

We currently use Qubit in the ECommerce department. We use this to A/B test hypothesised theories on our website. We have been able to make solid design and UX based decisions on the development of our site because of Qubit.

Qubit is used by a wide variety of departments within the company and in many different ways. My first experience with Qubit was when I had been tasked to change one of the tracking tags on our website. Due to the seamlessness that Qubit delivers these tags I didn’t even realise that we had a tag manager and was amazed to find out exactly how powerful and useful Qubit was. These days I use the Qubit services on a daily basis to create and deploy A/B tests to our website to improve customer experience and increase conversion rates.

We use qubit on a daily basis both for A/B testing and content delivery. Implementing new functionality in qubit is much faster than asking developers to made some changes (and we actually measure the impact of those changes!). We also use qubit for personalisation and delivering "hand-picked" offers for selected segments and groups of customers.

1. CRO development
2. A/B build and reporting
3. Implementing onsite content / merchandising where we cannot access via our CMS
4. Onsite personalisation experience management

We use Qubit solely within the Marketing department as this team is responsible for onsite content, UX and of course marketing/merchandising activity.

Qubit is used to enhance our websites across all of the business for CeX (but not for subsidiary Designer Exchange for contractual and cost reasons). It has been deployed on websites for all 12 CeX territory websites. The use of it is driven by members of IT (including myself) and Marketing. It allows us to try new ideas quickly without interrupting internal resources, therefore can respond quicker to certain things, we can a/b test those ideas, and use the data to determine if they are of benefit or not, putting an end to many conflicting opinions because multiple ideas can be tested. We can also personalise those tests and experiences using the data we pass to Qubit, which we are not currently able to do. That all applies to the Qubit Personalisation product along with Universal Variable. However we also use product recommendations which piggybacks of the previous mentioned products to produce something we would not be able to create in house at the same speed and quality. WIth the data we send Qubit, we and they can develop many more uses which alone we would struggle to build, such as personal and targeted email marketing and many other website enhancements.

Qubit is currently being used by our Omnichannel and Digital department to set up new experiences, test new experiences, understand trends and finally make an informed decision to go for a permanent solution on our website platform. It currently solves our key problem of lead time to have experiences set up and running on our website platform as it requires releases whereas Qubit provides a way of doing it almost immediately.

Qubit is used for A/B testing and conversion rate optimisation on our website.

We use Qubit for local messaging, A/B testing and product recommendations on the home and product pages. It is just used in the eCommerce department, it is a huge part of our website and on-going strategy.

Used for A/B testing as we have limited development resource and lead times. It's being used by the UK eCOMMERCE department only. It addresses the need to understand how to optimise the site to improve conversion, UX and CX. It also supports us with the ability to make faster changes to the site which is one of our largest restrictions.

We use Qubit at the ecommerce department for delivering new experiences to the users, going one step further through personalization and improving current user experience of the whole site - all with a powerful short time to market.

We are using Qubit primarily to create experiences and run our A/b and MVT test programme. As well as this, we utilise other products of theirs such as behavioural recommendations and also take part in beta programmes. We are aware of personalisation capabilities however, this is something we are only using in a limited capacity at the moment but plan to take more advantage of in the future.

By being able to test solutions to different problems that we identify, as wall as try out new ideas, Qubit helps us to minimise risk and ensure that we not only increase our profits but also, and more importantly, deliver the best experience for our customers.

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.

We currently use Qubit as a tool within our digital marketing team. With data-driven insights, we create A/B tests for several of our websites, with the main goal usually being to increase conversion. We also use Qubit to serve website content to our customers in order to help us promote current offers, and products.

Qubit is being used in multiple functions. Our company uses both the Opentag tagging function on the website and also the 'Discovery' function for CRO/UX and feedback collection on-site. Qubit usage is entirely held within the Digital Marketing team. It addresses the issue of providing a tag container onto the website and also providing A/B testing needed for CRO. It also serves as a mechanism to collect qualitative feedback online from customers.

We currently use Qubit in the optimisation section of the Digital department. It enables us to test out new functionality and/or things we think we solve problems customers are having before going forwards with the costly & timely process of implementing them on the site. We also have recently started using Qubit to segment our customers and serve them personalised content.

Qubit is primarily being used by Digital Product team to facilitate A/B testing and mitigate risk when rolling out new product features and designs.

Currently Qubit is being used primarily by our Digital Product Management team. Our Product Manager is managing the tool as well as our relationship with Qubit. The eCommerce Merchandising team provides input as to what types of test we run, but for the most part it is used by my team (Digital Product Management). We're primarily using the tool for A/B tests, experiences, as well as data analysis. The Qubit suite provides in depth analytics that we'd love to dive into even deeper, but with limited head count it's been challenging to dive in as deep as we'd like. We hope to broaden the team in the coming months and devote more time to analyzing our results and rich data that we've been collecting to tailor future tests and experiences.

It is used by the e-commerce department to improve site UX, A/B split tests and implement new features such as social proofing. It enables us to test things before we commit to a permanent change in addition to building bespoke customer experiences for key marketing events like Christmas and Valentine's Day.

Qubit is used by few departments: BI, marketing, and product. The whole organization is participating in the process of A/B testing and is feeding into it. We test new features, improve basket and registration flows and test UX improvements. Qubit is also used for quick feature solution for marketing team when they need a pop-up or a countdown.

We use Qubit within our e-commerce department, specifically across our three e-commerce sites. Qubit not only helps us to optimize from a conversion rate and revenue perspective, but it also enables us to really enhance and personalize the site experience for our different customer segments.

Mainly used by marketing but also across IT, Qubit allows quick and easy A/B testing of potential features to feed into the software development cycle, saving us time wasting development resource on features that customers do not want. We have also used Qubit to get very quick "mini features" out which are required as a result of legislation or poor customer experience and feedback.

Qubit is being used by the whole company to support various requests but only implemented by the UX department. A/B testing is its primary application but it also supports business requirements for rolling out quick changes that would normally have to go through a much more convoluted internal process of releasing updates.