How do I turn on error tracking?
Adddata-track-errors to your tracking snippet. It’s off by default because most sites want to opt in deliberately.
window.onerror) and unhandled promise rejections — the two ways errors normally escape your code — and sends each as an error event.
What does tinyanalytics record for each error?
Each captured error records the fields you need to reproduce it, all trimmed to safe limits:
Errors are captured with the same page context as any other event — the page, browser, OS, device, and country — so you can see where and for whom each error happens.
tinyanalytics filters out noise automatically. Benign
ResizeObserver loop warnings are dropped, and errors from cross-origin third-party scripts are ignored — only errors from your own site are recorded. Identical errors from the same visitor are de-duplicated within a 60-second window, so one broken loop doesn’t flood your report.How do I track an error manually?
To record an error you’ve caught yourself — in atry/catch, an error boundary, or a rejected request — call trackError:
How do I read the Errors report?
The Errors report lists one row per distinct error message, most frequent first. For each error you see:
Click an error to open its details and read every individual occurrence: the exact time, the visitor’s page, browser, OS, device, and country, the person (linked to their user profile), the full message, and the stack trace with a clickable
file:line:column reference.
The report honors your dashboard’s date range, filters, and segments — so you can narrow to errors on one page, one browser, or one release.
Common workflows
- Triage by impact. Sort by sessions, not occurrences, to fix the errors hurting the most people first.
- Confirm a fix. Watch an error’s trend sparkline drop to zero after you deploy.
- Scope a regression. Filter to a browser or country to see whether an error is universal or environment-specific.
Frequently asked questions
Why aren't my JavaScript errors showing up in tinyanalytics?
Why aren't my JavaScript errors showing up in tinyanalytics?
Error tracking is off by default. Add the
data-track-errors attribute to your tracking snippet and re-deploy, and tinyanalytics starts capturing uncaught exceptions and unhandled promise rejections as error events.What's the difference between automatic and manual error tracking?
What's the difference between automatic and manual error tracking?
Automatic capture records the errors that escape your code — uncaught exceptions (
window.onerror) and unhandled promise rejections — once data-track-errors is on. Manual tracking with window.tinyanalytics.trackError(err, { ... }) records errors you already catch yourself in a try/catch or error boundary, with optional metadata. Use both together.Does tinyanalytics capture errors from third-party scripts?
Does tinyanalytics capture errors from third-party scripts?
No. Errors from cross-origin third-party scripts are ignored, so only errors from your own site are recorded. tinyanalytics also drops benign
ResizeObserver loop warnings, and de-duplicates identical errors from the same visitor within a 60-second window.How do I tell how many people an error affects?
How do I tell how many people an error affects?
Read the Sessions column in the tinyanalytics Errors report — it counts the distinct sessions that hit the error, which is your blast radius. Sort by sessions rather than occurrences to fix the errors hurting the most people first.
Related
Configure the tracking script
The
data-track-errors attribute and every other option.Track custom events
Send named events and properties yourself.
Performance
Core Web Vitals — the other health signal.
Tracking API
The
error event type on the ingestion endpoint.