TrackJS Reviews

TrackJS does exactly what you hope it would do. And a lot more of stuff that you didnt know you needed.

In our case I would have liked more notifications switched on by default. It would have saved a lot of money! (yes, I know we created the errors in the first place)

We have a third party JS app installed on E-Commerce sites. JS is helping us in tracking our JS Errors on many different environments.

Track rate of errors, most common errors, new errors. Tight integration to Slack that includes friendly warnings and notifications. It also has a good summary of errors and tracking of state during errors.

Opted in for event rate summary but doesn't appear to have worked.

Great tool for tracking client side errors, integration to Slack for monitoring, and for tracking rate and frequency of errors.

Track front end errors that would otherwise be lost, identify most common errors to fix, also identify issues that users aren't raising (most!).

Very easy to implement. Simply include a script tag at the top of your index.html, and TrackJS takes care of everything else.

Reporting is excellent. It includes all the information you need to track exactly what happened.

TrackJS sends a daily email containing view count and errors. If your site isn't used on a particular day, this email indicates that there is a fault with your connection, which isn't the case.

Discovering errors in the clients web browser helps improve my application. TrackJS daily reporting raises awareness of problems so they can be fixed quickly.

It is quiet simple to get additional tracking for your spa by adding a few lines of code and it does not disturb the performance of the app.

There are many things you can set, so you have to view multiple pages to set up everything right, but is that really a dislike?

We early see problems with the app used by various browsers and can react on those.

The user interface and log capturing is wonderful

As far as what's currently available I don't have much I dislike. Filtering takes a little bit to learn but for the most part it's pretty good

It is a great alternative for front end monitoring.

We were using sumo logic and decided to try track to save on costs. It does the job better and with more detail in the logs. It was also much easier to set up and use,.

visibility of client side errors with convenient filters and data regarding other events that occurred around the time of the error

I can't trace the error down to the line in my source code. I know there is a source map feature, but I have not been able to get this to work with my app. Most of the stack trace info is from the framework that I am using rather than my code.

I checked out the alerting feature - it could be more robust with better support of filters.

it's awesome. use it.

Detecting & fixing errors in production. Once I fix the bug, I can see in the graph that the incidence has gone down, soI know I fixed it.

Also, after a production upload, I closely monitor trackjs to make sure there are no surprises. This gives me peace of mind.

With trackJS, the focus is on errors occurring on the browser. The tooling is well geared for this task. Filtering is second to none, and the quick views of trending errors are helpful in digging past the 3rd party script noise. The error grouping is effective. It's helps filter down to the core issues.

In addition, trackjs added node support for our next.js based sites. That was amazingly helpful.

We also like how we're able to have an unlimited number of named users.

When setting up new users, the email that trackjs sends is often trapped in spam filters due to the work "track" :-)

We're able to quickly triage customer facing issues. Compared to some of our other tooling, trackjs is much better focused on dealing with the browser error issues. It provides some context beyond just the error message. For example, it captures what was happening before and after the error occurred.

Provides great visibility into web apps & PWAs. Allows better decisions & info (e.g. a release introduces or fixes a specific bug). Quick and easy to integrate, the dashboard is easy to use, and the data provided is complete and actionable. Support has also been fantastic whenever we've had any questions. The ability to track product version is really fantastic and makes it easy to tie issues to specific code.

At this point the only thing I would like to see is longer data retention so that we can track specific error trends over a longer period of time. There have been a few cases where we have asked for specific functionality or changes, but these have always been added to the product eventually.

Be sure to keep `console` statements in your code when using TrackJS and use the different logging levels (debug, info, warn, error) for maximum effect. Definitely include the product version and tie to specific user accounts to save yourself trouble in handling user issues.

We're able to track every error our customers experience along with sufficient data to be able to quickly identify and resolve these issues. We've been able to resolve issues we probably would never have known about without using TrackJS. As a result this has helped us improve user adoption and revenue besides. We're currently implementing the new Node.js agent on our Google Cloud Functions to provide better error tracking and insights into our serverless environment.

It has a very organized user interface and is clear analytics so you can prioritize your debugging. Pricing is very reasonable. Simple to implement. Not a large overhead for the user to load during a pageview (this was very important to me). Support is very quick.

Nothing at all! I can't think of anything else I would need out of it since it does its job well.

I would say go for it. You also have a trial version that you can use and they are very flexible with it in terms of how many domains you can implement it on. They also provide discounts to those who work for educational organizations.

Since we specialize in front end development, we can't realistically setup machines with various combinations of OSes and browser versions. Therefore, this enables us to see whether or not our users are experiencing js issues and how to closely recreate those scenarios for debugging.

Easy to integrate; helpful error details with replication info; monthly summary

early stage of using this and don't see any downside as such

Client errors do not go unreported; plus this really helps with the issue details to understand the use case, replication steps and definitely helps in overall issue resolution