G2

Yusup E.

Frontend Developer

Computer Software

Mid-Market (51-1000 emp.)

9/1/2026

"Less screenshot chasing and faster frontend debugging"

4.5/5

Describe the project or task LogRocket helped with:

N/A Review collected by and hosted on G2.com.

What do you like best about LogRocket?

LogRocket is most useful for us when a problem only makes sense after we’ve seen the exact sequence of state changes that led up to it. Being able to record Redux state and actions gives us that missing context, and pairing it with Frontend Performance Monitoring, heatmaps, clickmaps, rage clicks, and dead clicks helps us uncover issues that never throw a JavaScript exception. A page can return 200 on every request and still feel broken if a button looks clickable but does nothing, or if the interface takes too long to become usable. Because LogRocket captures performance, network activity, console logs, and user behavior through the same SDK, we can usually tell pretty quickly whether we’re dealing with a technical failure, a usability problem, or simply a confusing interaction. Product Analytics adds another helpful layer when the issue shows up inside a funnel: we can spot the drop-off, isolate the sessions that didn’t convert, and jump straight into replay instead of comparing dashboards across tools and then manually hunting down the same users. Review collected by and hosted on G2.com.

What do you dislike about LogRocket?

One downside is that LogRocket can surface more information than you realistically know what to do with. If the team starts opening random replays just hoping to “find something,” it quickly becomes a very expensive way to watch people use the product. We’ve seen much better results when we begin with a concrete signal—an error, a funnel drop, an affected user, or a Galileo insight—and then use the session replay as supporting evidence, rather than treating the replay itself as the investigation. Review collected by and hosted on G2.com.

Recommendations to others considering LogRocket:

N/A Review collected by and hosted on G2.com.

What problems is LogRocket solving and how is that benefiting you?

After a checkout change, support started getting reports that the payment button “did nothing.” Our automated tests were still green and there was no obvious exception, so the issue felt frustratingly vague at first. We filtered LogRocket sessions by the checkout URL and network failures, and quickly spotted users clicking the button over and over while one request was returning a 409 because the cart state had gone stale. In LogRocket’s Network Logs we could see the response clearly, and the timeline made it obvious how that network behavior lined up with our frontend state: Redux had left a loading flag stuck on, so the component never returned to an interactive state. From the user’s perspective, it really did look like a dead button. We fixed the reducer, added a more specific error message, and then reviewed the same funnel again to confirm the rage clicking had actually disappeared. LogRocket saved us from having to ask the customer for yet another screen recording, connected network activity and frontend state in one place, and let us validate the fix using real sessions instead of calling it done just because it worked locally. Review collected by and hosted on G2.com.