We mainly use it for session replay, and it has become a crucial tool for finding issues that only happen in a specific state. Without full session replay, it would be very difficult to identify the root cause. The session replay UI looks like a normal browser, but it also includes a network logs tab, performance indicators, and details about the browser and operating system.

It also makes it much easier to spot UX problems—for example, by reviewing rage click events. When we release a new major feature, we check how users interact with it so we can fine-tune the experience. Sometimes we also receive incomplete issue reports from customer support, and then we can go back and see what actually happened for that user.

We built a solution around Logrocket that lets us track only users who have a repeated problem that we can’t reproduce. That way, if the issue happens again, we can replay their session and investigate with more context.

The platform’s performance has been really good, and we haven’t had any issues so far. I’ve also been in contact with their customer support, and they responded to my questions within a reasonable timeframe. Review collected by and hosted on G2.com.

I miss the feature that let me track only the users who are encountering an issue. Without it, we’re constantly struggling with our session recording quota. For a high-traffic web application, this can get expensive. Review collected by and hosted on G2.com.