Why track JavaScript errors like this...
TypeError: e is undefined, scripts.js, line 1

When you can {Track:js} like this...

Mobile error detail screen
Icon

Telemetry Timeline

More than just errors.

See the user, network, and console events that preceded an error; laid out in chronological order. Recreate your customers steps and fix errors.

Icon

Application Context

In JavaScript, context matters.

{Track:js} provides a complete snapshot of the application, browser, operating system, and javascript libraries that were present to the error.

Icon

Tracked Console

Ship your console.logs.

{Track:js} captures your console messages in a rolling appender and includes them in the Telemetry Timeline when an error occurs. Print-line debugging in the browser.

Let's get started

Track Errors, Fix Bugs,
Delight Customers.

Error timeline

Replay what happened in the network, the console, and what the user was doing right up to the error.

Error Timeline

Dashboard

See a snapshot of your application health. Be aware of spikes and changes in error rates and how errors are affecting your users.

Latest browsers, devices, and Libraries change fast.
Do you know when the cloud is storming?

You depend on the cloud

Do you know when it's storming? When it goes down? When it changes? {Track:js} tracks the errors that impact your customer.

The web is changing fast

Make sure your web app runs great when new browsers, devices and libraries get released.

Latest browsers, devices, and Libraries change fast.

Let's get started

Track Errors, Fix Bugs,
Delight Customers.