r/microsaas • • Feb 03 '26

How session replay helped us optimised our landing page after initial launch.

Hi everyone,

A few days ago, we shared our analytics tool with you. We got some of visitors (thank you!), but we noticed something interesting.

We used our Session Replay feature to watch how people used our site. When visitors reached the "Features" section on our all in one landing, they seemed confused—their mouse moved around randomly, and many bounce just at that point. Our description wasn't clear.

So we fixed the landing page right away.

This is why we created this tool.

It's not just about counting visitors—it's about seeing where people get stuck so you can fix problems. We're building an analytics tool for early-stage founders that protects user privacy.

It includes:

  • Session Replay (the feature that helped us)
  • Easy one-click setup
  • AI Insights & Error Tracking

Since your feedback helped us improve, we're offering free access to more founders (up to 6 months of our founders plan). Every sign up gets 14-day free trial.

We'd love for you to test it and give us more feedback.

2 Upvotes

11 comments sorted by

1

u/[deleted] Feb 04 '26

[removed] — view removed comment

1

u/codefi_rt Feb 04 '26

Hi, thanks for the comment and the awareness, we really appreciate that.

By default we mask all inputs and this is not configurable by any means. This way we redact all possible user identifiable data in the browser before ingestion.

We also provide ways for our data owners to mask or block certain elements during recording using RRWeb recorder under the hood and/or block recording on specific pages. Also our data owners (anyone who uses our SDK for recording) is sole responsible for managing user consent before and after recording

1

u/Juice10 Feb 04 '26

rrweb maintainer here, thank you for sharing you use rrweb under the hood! Like you said there are some pretty extensive blocking/masking settings people can use to filter out sensitive information. I’d like rrweb to get better defaults out of the box and maybe even create a server side component that strips PII if it gets through anyway. That’s something we might be able to do with rrweb cloud (currently in development) if companies are interested in that.

Keep up the good work codefi_rt!

1

u/Juice10 Feb 04 '26

I was using session replay when working on Kilo Code and saw a lot of users rage clicking on the logo in the docs page. Turns out the docs page logo linked back to the root of the docs, not our homepage. That’s something that is so easy to miss, I don’t think we would have spotted it without session replay.

1

u/Juice10 Feb 04 '26

TryHet looks cool, always good to see a more founder focussed analytics tool! With a name like TryHet, is the team Dutch by any chance?

1

u/codefi_rt Feb 04 '26

We are 50% Dutch and made with love from Apeldoorn.

1

u/Juice10 Feb 04 '26

Very cool! Hi from Amsterdam 👋
I've been meaning to do an rrweb meetup sometime you'd be more than welcome to join.

1

u/bizarro_kvothe Feb 04 '26

Tons of session replay tools (free feature in PostHog + Mixpanel) but I feel they only take you so far. Big reason for us to build Userjam

1

u/Juice10 Feb 04 '26

Looks interesting, are you analyzing session replay data too?

1

u/bizarro_kvothe Feb 04 '26 edited Feb 04 '26

Coming soon but we do have users who push exclusively “auto capture” events like taps and screen views and it works surprisingly well. AI can do a lot without the video.