• Proxy
  • Pricing
Live demo
Datasense

Cookieless analytics with live visitors, console errors and exports, served from your own domain.

Product

  • Features
  • Error tracking
  • AI crawler tracking
  • Revenue attribution
  • Ad-block proxy
  • Pricing
  • Live demo

Install

  • Add the script
  • Next.js & Vercel
  • Cloudflare Worker
  • Nginx

Compare

  • vs Google Analytics
  • vs Plausible
  • vs DataFast
  • vs Fathom
  • All alternatives

Company

  • FAQ
  • Terms
  • Privacy
  • Refunds
  • Cookies
  • DPA
© 2026 DatasenseNo cookies were set on this page.
  1. Features
  2. /
  3. Error tracking

Website analytics with JavaScript error tracking

Most analytics tools tell you how many people visited. They don't tell you the page broke for half of them. Datasense records JavaScript errors from real browsers with the same script that counts your visitors, so traffic and errors sit in one dashboard.

Try Datasense freeOpen the live demo

Free up to 5k events a month. No card.

What JavaScript error tracking records

Four kinds of errors

Uncaught exceptions, unhandled promise rejections, failed scripts, images and stylesheets, and console.error calls. You can filter the list by kind.

The details you need to fix it

Each error comes with its message, stack trace, page, browser, operating system, device and country. You see where it happened and for whom.

Grouped, with counts

The same error from many visitors shows up as one row. It tells you how many times it happened, how many visitors hit it, which pages and browsers, and when it was first and last seen.

Live, next to your traffic

New errors appear while the page is open, without a refresh. The same dashboard shows visitors, sources and revenue, so you can tell if a drop in sales lines up with a new error.

How to start tracking JavaScript errors

  1. Step 1

    Add the script

    Create a free account and paste one script tag into your site's <head>. It's under 3 KB.

  2. Step 2

    That's the setup

    Error tracking is on by default. There's no second SDK and no extra config. Errors start coming in with your first pageviews.

  3. Step 3

    Open the Errors page

    Click an error to see its stack trace and each time it happened. Export the list as CSV if you want to share it.

What it doesn't do

So you know before you sign up.

  • It keeps the latest 100 errors per site, not your full history.
  • It only sees errors in the browser. Server errors need a server-side tool.
  • It doesn't send alerts by email or Slack, and it doesn't read source maps or track releases. If you need those, keep a tool like Sentry and use Datasense to see errors next to traffic.

Questions people ask

Uncaught exceptions, unhandled promise rejections, failed scripts, images and stylesheets, and console.error calls. Each comes with its stack trace when the browser reports one.

More from Datasense

  • AI crawler tracking
  • Revenue attribution

Or see how Datasense compares to other analytics tools.

See it on your own site

Add one script tag and your first numbers show up in seconds. The free plan is enough to try it.

Add your siteOpen the live demo
Sign in