Queue up for Qubit!
Updated December 12, 2017
Queue up for Qubit!
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Qubit
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.
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.
- Being able to inject content into the exact places you want, and further target segments/devices etc. easily.
- Now that we've got our UV setup correctly, it's very powerful in its ability to target users, and pinpoint experiences without limitation.
- Capturing exit survey content and details in one place is very useful.
- Reporting could be improved, providing more stats such as projected value calculation, clicks, impact from other experiences live etc.
- Content production should be a hybrid of Basic (full GUI view) and Expert (only code view). We should be able to access the HTML/CSS and write this ourselves, letting the system manage the JS. Also, content production should be responsive - allowing us to build experiences for Mobile and Desktop in one experience.
- Qubit engineering and QA takes a long time to turn around. We should be looking at days rather than weeks.
- Setting a go-live and end dates to experiences would be really useful!