Qbaka to introduce Bounce Tracking. Tells exactly why users leave website.

You can measure revenue losses caused by broken user experience

25 APRIL 2014, THE NEXT WEB CONFERENCE, AMSTERDAM, NETHERLANDS
Summary
When 85% of users leave the website after a JavaScript error on billing page this must be a big issue. Today we introduce a new major direction for Qbaka: user-centric problem analytics. It starts with new breakthrough Bounce Tracking feature. With Bounce Tracking not only we can tell what are the problems on website, who experienced them and how you can reproduce errors, we can now tell you how big of a problem a particular error is for your business. Bounce Tracking tells you how many users left your web service after they experienced an error. When possible, Qbaka also provides information on who exactly bounced, so you will be able to contact users and make them sure you fixed an error. You can finally measure how harmful particular errors are for your company.

Our path to user-centric problem analytics

Since we started building Qbaka in 2012, we've always been committed to helping solve technical and business problems from the client-side point of view. It's always hard to know your customers' UI troubles after you release a feature update, when everything seems good. It's even harder to get technical details or steps to reproduce the problem from your users. In Qbaka we are focusing on delivering maximum of valuable information about user problems without any actual user interaction. Having started with frontend error monitoring, we've been moving to extend our product to get more details from client-side tracking: we've launched user actions tracking (shows what user did before error occurred) and impact monitoring (shows how many users and who exactly experienced an error).

New direction, introducing Bounce Tracking

Today we introduce the major new focus of our company: user-centric problem analytics. We start it with a big user analytics feature which no one else have: bounce tracking that shows the reason why users bounced. Now not only we can tell what are the problems on your website, who experienced them and how you can reproduce the error, but you can finally measure how big of a problem a particular error is for your business. Bounce tracking tells you how many users left your web service after they experienced an error. When many users leave the website after a JavaScript error on billing page this gotta be a really big issue. When possible, Qbaka also provides information on who exactly bounced, so you will be able to contact users and make them sure you fixed an error. The special dashboard where you can see errors, causing most bounces, will give you insights on which errors are the most harmful.

The future of Qbaka

This is a first big step for Qbaka to become what we've always dreamed about: a client-side solution for users' problems. With a variety of marketing user analytics available, no one really tells you why users have bad experience and which problems stop them from buying stuff on company's web service. We cannot track a whistling teapot, distracting user for browsing, but we can monitor and analyze all measurable data to bring you the information about problematic user behaviour and recommend how you can fix user experience. Much more is to be expected this year.

Bounce tracking is available on an invite basis in order to stress-test a new feature and deliver best quality. Existing and new customers can request an invite at qbaka.com/bounce, new users can register for Qbaka at qbaka.com.

There is a 30% discount for the first 3 months of Qbaka with coupon TNW2014

Videos
About Qbaka

Qbaka’s end goal is making web a better place by helping companies provide great user experience. We are in love with simple, intuitive and interactive interfaces. By building a tool that monitors and analyses users' problems, we bring developers and businesses a lovely way to make their web services great.