Never heard of the service before, but this is something that would be extremely helpful. I'm curious to know the client-side performance overhead. Can you say anything in regards to that?
taasaa
· 6 months ago
Didn't see any effect on client side performance. We have couple of our clients use it on production sites for about half a year now, and it looks pretty solid and performant.
It does bring clicktale javascripts, that are about 2.5K in size. Which is reasonable, if you ask me.
Anonymous
· 6 months ago
Awesome plugin!
I don't wanna sound like a dick but could we replicate Clicktale's JS functionality as well so all the data captured resides on our own servers? I have an issue with giving my users' browsing habits to a third-party site.
taasaa
· 6 months ago
You welcome to replicate their service. I would assume that it's not that easy, they work on it for couple of years now.
I don't know much about the inner works of clicktale service, just made an integration of their stuff into rails.
Guilherme Garnier
· 6 months ago
Isn´t this a little too obtrusive?
taasaa
· 6 months ago
I personally don't think so, although i agree that it somewhat borderline.
You still collect all the info you can about the user in your database, probably you have some local app statistics as well, to show user engagement with you app, you have google analytics and other 3 parties gathering statistics about your users etc.
And if you already have access to all the info user provided you, like his names/phones/what have you, access to _how_ this was entered is less obtrusive.
All Comments
It does bring clicktale javascripts, that are about 2.5K in size. Which is reasonable, if you ask me.
I don't wanna sound like a dick but could we replicate Clicktale's JS functionality as well so all the data captured resides on our own servers? I have an issue with giving my users' browsing habits to a third-party site.
I don't know much about the inner works of clicktale service, just made an integration of their stuff into rails.
You still collect all the info you can about the user in your database, probably you have some local app statistics as well, to show user engagement with you app, you have google analytics and other 3 parties gathering statistics about your users etc.
And if you already have access to all the info user provided you, like his names/phones/what have you, access to _how_ this was entered is less obtrusive.