4 ms·
A question, since I have the ear of an individual who chose to add tracking to their small website: what exactly do you hope to get from these trackers? Do you
by ken 7y ago
A question, since I have the ear of an individual who chose to add tracking to their small website: what exactly do you hope to get from these trackers? Do you think there could be some critical piece of information which could be gleaned from these logs which could help?
I associate trackers with megacorps where they're essentially playing Telephone between management and the boots on the ground doing the work ("we need tracking!" "ok, next on the work checklist is tracking, and here's a service that says it does that...").
- bbaumgar 7y agoWe make a large, enterprise-targeted app at my startup. Fullstory has accelerated our search for product-market fit by allowing us to make some significant discoveries in how users use our app. We could have made all these discoveries by properly instrumenting our code with our own tracking framework. That said, Fullstory provided us a big bang for our buck in [time spent : value provided]; half-day implementation led to all the usage info we could need. We've gone as far as creating a recurring "Game Tape Friday" meeting where the whole development team sits down and watches 5-10 user sessions together to record bugs and possible UX improvements. We're not a small website so this anecdote may be of limited value to you, but I would personally give up syntax highlighting before I would give up Fullstory.
- bucket2015 7y agoFullstory basically lets me sit behind the shoulder of every user and e.g. watch them use the app in a way I didn't think of, or stumble over the features that I thought were obvious but turns out are very counter-intuitive. It's totally a game changer for UX design. Heap, Google Analytics, etc are actually not as useful; I find the app's DB and server logs provide more relevant data. So I don't think I'll add them back.