What is Inspectlet and what are its top alternatives?
Inspectlet alternatives & related posts
related Hotjar posts
We needed to look more into how user interact with certain pages (scroll, click, move the mouse around) so we had to decide between Crazy Egg and Hotjar . I've used both solution in the past so I was familiar with the features for each, but each one has a unique set of data sets and so it will fit diffrently for each case. At #stackshare we've decided to go with Crazy Egg mainly because of the click maps as we can see where people are clicking on certain elements, buttons and clicks and we can spot bottle necks. A very good feature that Hotjar is missing is also the source of the traffic for the clicks. As there are large diffrences between diurect, organic, social and referral traffic as far as user behaivor.
I've always been passionate about knowing more about how #UX the products that I'm building and have used a bunch of session replay tools in the past, tools like Crazy Egg Hotjar Mixpanel but i am developing affinity for FullStory. I find searching for events to be effective and fast. i live the ability to see when users are frustrated and also skip inactivity, it's pretty intuitive.
I also feel that the creating funnels could be improved (like Mixpanel ) and also give recommendations about using your data tier more efficiently.
related FullStory posts
We chose Webflow to build up websites faster and to make possible for particular employees to fix some misspellings or add an easy element to the page on their own - it is like Adobe Photoshop. To work with the incoming traffic we use our own product, that I can't pin here. It helps to make nurture visitors from the first session into the signing up and further activation into the product. In addition to @Carrrot we use Google Analytics to traffic source awareness, to monitor customers inside the product FullStory helps is a lot with its fury clicking and abandoned links. Activation and retention are done by our own product through the pop-ups, live chat, and emails that all based on customer behavior.
For any project that anyone creates these days (myself included) you want to see how many visitors your site gets, where they come from, what they clicked etc. The easiest and cheapest way to do this is obviously Google Analytics I think that 99% of websites out there have Google Analytics embedded into their code.
I am no different, I wanted to see how the users were getting to my site, what they clicked, how long they were on there for etc. etc. So I added Google Analytics to my site too... Which was really cool and free, but the longer I used Google Analytics I felt that I wanted more insight. Like what if I could actually see how users interacted with my site.
I came across FullStory and this is exactly what I wanted, it will record all your user sessions and you get to replay them in full. So you can see exactly how a user uses your site, what they click, and see if your site might benefit from some A/B tests or changes. - I am on the free plan, so it doesn't need to cost you a fortune.
Both Google Analytics and FullStory allow you to login with your G Suite account which helps you keep your accounts all linked.
With FullStory and Google Analytics I feel that I have the perfect insight into how the users are using my site, and all the analytics around how they get there. Its a perfect combo
related LogRocket posts
I had narrowed it down to two tools LogRocket and Sentry (I also tried Bugsnag but it did not make the final two). Before I get into this I want to say that both of these tools are amazing and whichever you choose will suit your needs well.
I firstly decided to go with LogRocket the fact that they had a recorded screen capture of what the user was doing when the bug happened was amazing... I could go back and rewatch what the user did to replicate that error, this was fantastic. It was also very easy to setup and get going. They had options for React and Redux.js so you can track all your Redux.js actions. I had a fairly large Redux.js store, this was ended up being a issue, it killed the processing power on my machine, Chrome ended up using 2-4gb of ram, so I quickly disabled the Redux.js option.
After using LogRocket for a month or so I decided to switch to Sentry. I noticed that Sentry was openSorce and everyone was talking about Sentry so I thought I may as well give it a test drive. Setting it up was so easy, I had everything up and running within seconds. It also gives you the option to wrap an errorBoundry in React so get more specific errors. The simplicity of Sentry was a breath of fresh air, it allowed me find the bug that was shown to the user and fix that very simply. The UI for Sentry is beautiful and just really clean to look at, and their emails are also just perfect.
I have decided to stick with Sentry for the long run, I tested pretty much all the JS error loggers and I find Sentry the best.