User Journeys
We are evolving fast pace. Spectry tracks already more data than we have features to support. Today we released new feature User Journeys that is familiar from other tracking tools such as GA. Development effort was low as this required zero changes to database and analytics tracking. Data was already collected and now displayed in meaningful way.
Join to open beta and try Specry without limits for free!
Sign up now at https://spectry.io/beta
The gap between 'what happened' and 'why it happened' is something I've been running into firsthand as a new SaaS founder.
I launched Crestfolio a couple weeks ago — a personal finance platform — and I can see in my basic analytics that people are landing on the pricing page and leaving. But I have no idea if they're leaving because the pricing is wrong, the page is confusing, the value proposition isn't clear, or something is broken on mobile. That's exactly the diagnostic gap you're describing.
The funnel-to-replay connection you describe in step 2 is the feature I'd find most valuable — being able to click directly from a drop-off point into actual session recordings of users who abandoned. That would have saved me a lot of guessing over the past two weeks.
One question: for a very early stage product with low traffic — say under 500 sessions a month — is behavior analytics actually useful or do you need volume before the patterns become meaningful? I've always assumed heatmaps and session replays need a certain sample size before they tell you anything reliable. At what point does it become worth setting up?