Convert & fix
Find the JavaScript errors that cost you sales
See the bugs real visitors hit, on which pages and browsers, next to your traffic and revenue.
3 min read
A broken checkout button doesn't show up in your traffic numbers. Visitors arrive, click, nothing happens, and they leave. Your revenue drops and the dashboard looks normal.
Why this matters
Front-end bugs often only happen in one browser, one device or one country's network. You won't see them on your machine, but your visitors will, and the cost shows up as lost conversions.
Why most analytics tools can't tell you
Analytics tools don't record errors, and error trackers don't know about traffic or revenue. You need two products, two scripts and two dashboards to connect a bug to its cost.
How Datasense does it
The same Datasense script that counts visitors records uncaught exceptions, promise rejections, failed scripts and images, and console.error. Errors are grouped with counts, affected visitors, pages and browsers, and each visitor's profile shows errors in their timeline next to their pageviews and payments.
How to do it
- 1Install the script; error tracking is on by default.
- 2Open the Errors page: each row is one error, with how often it happened and how many visitors it hit.
- 3Click an error for its stack trace and every occurrence, with page, browser and visitor.
- 4Open an affected visitor to see what they did before and after the error, and whether they paid.
Turn it into action
- Fix the errors that hit the most visitors on your pricing, signup and checkout pages first.
- An error in only one browser usually means a missing feature or polyfill there.
- After a deploy, check the Errors page live: new errors appear without a refresh.
Good to know
- Each site keeps its latest 100 errors: it's for noticing breakage, not a full error tracker with releases and source maps.
In the docs:JavaScript error tracking →