What is Hotjar?
Who uses Hotjar?
Why developers like Hotjar?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Hotjar in their tech stack.
Segment has made it a no-brainer to integrate with third-party scripts and services, and has saved us from doing pointless redeploys just to change the It gives you the granularity to toggle services on different environments without having to make any code changes.
It's also a great platform for discovering SaaS products that you could add to your own – just by browsing their catalog, I've discovered tools we now currently use to augment our main product. Here are a few:
- Heap: We use Heap for our product analytics. Heap's philosophy is to gather events from multiple sources, and then organize and graph segments to form your own business insights. They have a few starter graphs like DAU and retention to help you get started.
- Hotjar: If a picture's worth a thousand words, than a video is worth 1000 * 30fps = 30k words per second. Hotjar gives us videos of user sessions so we can pinpoint problems that aren't necessarily JS exceptions – say, logical errors in a UX flow – that we'd otherwise miss.
- Bugsnag: Bugsnag has been a big help in catching run-time errors that our users encounter. Their Slack integration pings us when something goes wrong (which we can control if we want to notified on all bugs or just new bugs), and their source map uploader means that we don't have to debug minified code.
In order to fix this, we had to set up our own content delivery service. We chose Amazon CloudFront and Amazon S3 to do the job because it has a good synergy with Heroku PaaS we are already using.
Hotjar GitHub MailChimp Drift
When I started Checkly, I had no clear strategy on collection, managing and acting on customer feedback.
Over the last year, going from private beta to the first couple dozen customers I found my way in the jungle of customer feedback tooling and found something that worked for me and my company.
The linked post is a bit less technical than normally. The post goes into:
- Using Hotjar and how it sorta worked for me.
- Using Drift and why I was totally wrong about chat widget.
- Using GitHub as a public roadmap.
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.
To watch how users are interacting with the site in order to fix any issues they may be encountering (such as wrong size of image, broken links, not enough content on a page, etc.) Hotjar