Blaumaus
commented
10 months ago Hi @noone-silent, thanks for the detailed feedback!
I agree that the user flow is something that should be fixed and we will be working on it soon. My thoughts were to add filters to the user flow so that users could select some pages and only see the flow between those pages, which would make it much cleaner and easier to navigate.
As for the clickstream feature - it sounds really cool and is something that should not be too difficult for Swetrix to implement. I've created a ticket for this suggestion (https://github.com/Swetrix/roadmap/issues/178) and we'll be working on adding this to Swetrix soon.
I'll update you in this thread when this feature is done.
noone-silent
The user flow feature is nice, for a general overview of site usage. It is especially useful for websites for apps not so much. User flow also have disadvantages when a lot of url exists or data/time has been collected. For example look at the swetrix userflow of the last 12 months
Unreadable and completely useless.
For apps the interaction flow really needs to be attached to a session (doesn't need to be personal identified), to follow how the interaction with the website/app happened. To really identify bottlenecks in the navigation or click depth, surf logic.
OpenWebAnalytics has such session profiles and enables click stream tracking. It requires cookies and is multi session based, which is not needed most of the time.
Here I can click on any session profile and see what click journey / frontend experience this session had.
Why is this such an important feature?
For example, your app has a feature that allows to delete your account. You track this event via custom event or utm. Every week/month you look up this event/utm and want to know, why your users decided to delete their accounts. How can this be solved with swetrix? It's not possible. We have nice charts of pages, visits, entry and exit pages etc. but all this I can also get with webalizer or goaccess without even installing a single line of tracking code, managing possible ad/script blocks and such. It's just a bunch of collected data to make nice charts, but it is not useful to improve anything.
Another example: You have a funnel, but the funnel is not getting any attention or fails to convert. How to solve this problem with swetrix? You can't, because you can't see why this specific session lost the path or did not find the path at all. With a session profile you could identify the pages and SEE why this session has possible lost the path/interest or what ever. You also could use the pages to lead other customers correctly to your preferred goal.
How can this be implemented?
About privacy
Again, this feature doesn't need any personal data and is only to identify user journeys/interaction problems and how to solve them. It doesn't need any multi session tracking at all.
Final thoughts
I'm absolutely sure, this can be solved in a privacy friendly way and is an absolutely killer feature for everyone that needs to know more about a browser/app session, then what pages have been visited. No other of this privacy focused analytics has this feature and to be honest are mostly useless bunch of charts, that rely on JS Code and a tracking friendly environment.
I tried swetrix because of the user flow feature, but like stated above, it is not useful most of the time.
Why don't you use feature X then?
Please do not take anything of this personal, it is just honest feedback and I try to improve things.