Overall Satisfaction with FullStory
We use Fullstory to monitor anonymized user sessions to identify any usability challenges that our customers might be facing. These challenges could be related to bugs or confusing design. Through these sessions, we are able to find out where customers are getting stuck and test and build improvements to streamline problematic parts of our site.
- Session monitoring
- Anonymized session recording
- Identifying specific pain points for customers
- We use Canvas JS in our app and it simply breaks FullStory. There are large portions of our app that are invisible in recording
- I would like for there to be better disclosure and opt-out options for customers
- Session recording
- Automated session tagging and identifying customer pain points
- Triage for front end bugs - FullStory can sometimes help you spot a bug in action much more quickly than trying to recreate it on your own
- Observing customers use new features and understanding why a new feature may be performing better or worse than expected
- Heap and Tableau Online
I chose Heap and Tableau as two potential competitors because these provide a similar type of insight (how are customers experiencing your app) but from a different angle. In general I find the large scale, less personal data from these type of analytics vendors to be more actionable than what I get from FullStory, but there are times when the session-level insight of FullStory is valuable.
Do you think Fullstory delivers good value for the price?
Yes
Are you happy with Fullstory's feature set?
Yes
Did Fullstory live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Fullstory go as expected?
Yes
Would you buy Fullstory again?
No