Overall Satisfaction with FullStory
I use FullStory daily to keep an eye on who is using my app, monitor daily activity, and get a peek into unique user moments. When a new feature is launched, FullStory becomes my dashboard, allowing me to monitor whether it is working as tested and if people are adopting the tool.
- User experience dashboard
- User recording
- Custom event monitoring
- CSS selector tool can be finicky
- Dashboard not customizable
- Conversion rate testing
- Identifying bugs
- Testing benefit of new product releases
Implementation is stupid simple. FullStory integrates as a quick line of code. Most event tracking is done automatically, so we don't need to worry about how any new releases will impact its use (really is a set-it-and-forget-it sort of thing)! Be sure to take time and set up segments when you first start using the app--it really makes the experience a breeze.
I've only had one support experience with FullStory and it was resolved quickly and politely!
- Hotjar and Heap
FullStory stands head- and shoulders above the competition. It really has everything, and the user interface is a joy to use (my past experiences with Hotjar were a mess). Even better, pricing is stupid straightforward and not based on things like number of recordings or app usage like the competition (I've never felt like I've been forced to upgrade with FullStory).
Do you think FullStory delivers good value for the price?
Are you happy with FullStory's feature set?
Did FullStory live up to sales and marketing promises?
Did implementation of FullStory go as expected?
Would you buy FullStory again?
FullStory is a product manager or CS team members dream. It allows us to quickly tap in and see what exactly is going on in the app for a specific user. On launches, it helps us watch adoption happen live. And, of course, tools like frustration mapping are helpful to identify weak UX points.
5 - FullStory is generally used by two functions in our organization. Customer Success will use FullStory to help troubleshoot virtually when a user encounters an error. Oftentimes, a bug is actually just a user using our product in a way we don't expect, and recording tools on FullStory help our success team catch this. Product is the other functional user. In our day-to-day, we'll use FullStory to analyze user behaviour and key into experience issues and monitor who is using what.
1 - FullStory is very plug and play. It required one-time setup from our development team, but once done it requires essentially no maintenance or know-how. New users will quickly discover the apps recording capabilities and experienced users can dive deeper into event monitoring to key into specific use cases and frustration points.
- Viewing user recordings
- Monitoring trends in daily app use
- Measuring dead and error clicks
- Viewing user interactions with key product features
- Scorekeeping for our most active users
- Identifying frustrating user experiences
FullStory is the gold standard in user experience data collection. The app is extraordinarily powerful for experienced data ops teams while being wildly easy to use for new customer success users. Typically, it will be one of my first stops in the day to discover the latest user edxperiences.