The absolute worst message you can get from a user is "the checkout is broken" with zero additional context. no browser info, no console logs, nothing.
You end up staring at ga4 trying to figure out where the drop off happened but aggregate data is completely useless for debugging a frontend issue. you cant see if it was an api timeout, a hidden element or just a user doing something weird.
We were dealing with this exact headache a few weeks ago. we had users bouncing at the pricing page and no idea why.
Instead of guessing we started using session recordings combined with error tracking. we literally watched the playbacks of users getting stuck and saw exactly what was triggered. it turned out to be a clunky layout bug on specific mobile viewports that we missed. fixed it in 10 minutes and conversions went up.
This is exactly why we built zenovay. if you look at our sidebar we specifically put "Errors" and "Sessions" right next to each other. the goal was to stop switching between an analytics tool, a heatmap tool and an error monitoring tool.
We just wanted a simple dashboard where you see an error spike, click it and watch the exact session of the user who triggered it.
Right now we are a tiny bootstrapped team of developers trying to build an alternative to the massive google monopoly. it is really tough. we have fewer than 200 users and we are trying to get honest feedback from other devs.
We have a free tier that gives you the core tracking. if any of you are willing to drop our script into a side project and test out the error tracking and session replays, let me know. ill happily upgrade your account to the pro plan for a few months in exchange for some honest, constructive roasting of our ui and workflow.
This isnt about self promotion. its about taking on monopoly power and building a tool that actually saves developers time. we are grateful for any feedback.
Top comments (0)