Oh, interesting. I think this is a bug related to me viewing the data as an admin. Thanks for the catch.
đ, still interested in otherâs view.
Yeah, you can think of what weâre measuring as âbounce rateâ. I was thinking of giving it a relatively âuninterpretedâ treatment (ie: leaving the data raw, rather than calculating bounce rate), but I think more interpretation combined with tooltips seems better.
4.5. Re âaverage timeâ, this turned out to be harder than I expected, so I decided to wait to see if anyone asked for it, but now I have my excuse to spend time figuring it out, mwahaha.
On #3, yeah Iâd be interested to hear otherâs views too.
On #4 and 4.5, ah I see. Personally I think # of reads (i.e. # of views where the user spent at least 50% of the time it takes to read the article) or average time spent would be more interesting to me than the bounce rate, although Iâm unsure.
Thanks! I think these updates are good. Some thoughts/âsuggestions:
Maybe instead of saying âunique clientsâ you can say âunique devicesâ in the note about the data collection issue.
Iâm unsure about how valuable or apt âViews by unique devices > 5 minutesâ because some Forum posts take less than 5 minutes to read. So that data point will be irrelevant for those points.
I think some people will not know what âBounce rateâ is, so maybe you still need an icon that people can click or hover on to explain what that means and/âor how itâs calculated. Maybe you can also say in that tooltip that âThe lower the bounce rate, the betterâ.
Yep.
Oh, interesting. I think this is a bug related to me viewing the data as an admin. Thanks for the catch.
đ, still interested in otherâs view.
Yeah, you can think of what weâre measuring as âbounce rateâ. I was thinking of giving it a relatively âuninterpretedâ treatment (ie: leaving the data raw, rather than calculating bounce rate), but I think more interpretation combined with tooltips seems better.
4.5. Re âaverage timeâ, this turned out to be harder than I expected, so I decided to wait to see if anyone asked for it, but now I have my excuse to spend time figuring it out, mwahaha.
On #3, yeah Iâd be interested to hear otherâs views too.
On #4 and 4.5, ah I see. Personally I think # of reads (i.e. # of views where the user spent at least 50% of the time it takes to read the article) or average time spent would be more interesting to me than the bounce rate, although Iâm unsure.
I made some updates that should address a lot of this. Let me know what you think!
Thanks! I think these updates are good. Some thoughts/âsuggestions:
Maybe instead of saying âunique clientsâ you can say âunique devicesâ in the note about the data collection issue.
Iâm unsure about how valuable or apt âViews by unique devices > 5 minutesâ because some Forum posts take less than 5 minutes to read. So that data point will be irrelevant for those points.
I think some people will not know what âBounce rateâ is, so maybe you still need an icon that people can click or hover on to explain what that means and/âor how itâs calculated. Maybe you can also say in that tooltip that âThe lower the bounce rate, the betterâ.