Fullstory Reviews and Ratings

Use Cases and Deployment Scope

We use Fullstory in our organization to identify pain points our customers are having, technical problems within the platform, and to track custom events like clicks and page views. The most helpful feature we utilize is the session replay where we can replay individual user interactions to see how they navigate our website, and then we can make suggestions to our engineering teams

Likelihood to Recommend

Fullstory is well suited for any tech platform that wants insights into how their users are using the website. Sharing a fullstory link via integrations or through URL links makes it easier for our product and engineering teams to identify common issues and implement solutions more quickly. It is not suitable for org's that handle highly sensitive customer information unless there are strict controls within the organization.

Use Cases and Deployment Scope

We use it to diagnose user problems

Likelihood to Recommend

Helpful if you have diverse users and corner cases to try and track down, where just having server logs isnt enough

Use Cases and Deployment Scope

We use FullStory to understand how customers interact with our product, as well as to investigate technical issues that some customers face. We also use it to detect users' rage clicking and other customer behaviors that are important for us to optimize our happy flow, as well as edge cases.

Likelihood to Recommend

It's a great solution, but their pricing options need improvement, especially when free options exist. Great integration with Segment and similar tools.

Use Cases and Deployment Scope

Describe how you use FullStory in your organization. To troubleshoot CX support issues. What are the business problems the product addresses, and what is the scope of your use case? We are a technical support team, and being able to assess agents' interactions with our SaaS platform really helps us to get to the bottom of issues more swiftly.

Likelihood to Recommend

FullStory is the best support tool I know of.

Use Cases and Deployment Scope

Helps understand edge cases and bad product behavior for our end users. Also assists in recreating temporary complaints and gaining useful metadata around them. Very specifically when users encounter different errors with system inputs and therefore results in apparent user behavior (multiple refreshes, rage clicks, trying to navigate to different screens, etc.)

Likelihood to Recommend

Great for identifying end-user behavior trends and bugs. We use it to track specific user journeys from sign-in to set-up problems where they claim to see a certain problem, but we don't see it in our system logs - so FS helps us determine a certain level of truth. This is especially helpful with getting timestamps of certain issues we can correlate internally.

Use Cases and Deployment Scope

We're Kitty Poo Club! Our most common use for Full story is the segment tool. The developer console and css selectors within the segment allow me to troubleshoot where errors on the site are occurring. This is especially important to catch errors that block customer experience, particularly with checkout. We also use it for it's ability to hone in a specific set of customers who take actions on the site, which is helpful to inform metrics over a given period of time.

Likelihood to Recommend

Full story is very well equipped to handle debugging on the go, as I can set an alert for customer Segments to bring attention to any site issues that may occur. It also is used by our customer support team to help customers troubleshoot issues with their account and subscription. It's less applicable towards metrics that rely on a third party referral source, such as Facebook or Instagram. That tunnel can be hard to follow.

Use Cases and Deployment Scope

In our industry, the business is seasonal hence some quarters are heavier than the others. We love full story as it scales across all the features seamlessly and enables cross-functional teams to see the process, measure the outcomes, and narrow down the user behavior in a super simplified way. I led the FullStory implementation at my previous company and brought it to my team at a new company based on my delightful experience.

Likelihood to Recommend

Fulltstory is greatly suited for the product teams that are growing and have web or mobile apps. The biggest challenge that it solved for us is that we don't have to worry about creating customer events tags and embedding those inside the code to measure the user behavior. And the complexity of scaling the analytics as more and more feature experimentations are done is hugely simplified.

Use Cases and Deployment Scope

We use FullStory for both analytics and debugging.

FullStory lets us build interactive dashboard that capture users' actions, events, and other data for business/product analysis.

Their Session Replay features lets us watch users' browsing activities for debugging purposes

Likelihood to Recommend

FullStory is an excellent tool that helps debugging. However, it might sometimes be blocked by adblockers that some sessions are not recorded.

Use Cases and Deployment Scope

FullStory is an essential part of our Marketing, and Product tech stack. We use it to look at data, funnel conversion rates, feature adoption, and much more because we all know it's hard to get the job done, without the FullStory.

Likelihood to Recommend

If someone is using their site to monetize, and or have a product/software, then FullStory can be tremendously helpful. It's also helpful to understanding an overall customer experience.

Use Cases and Deployment Scope

I use this to track how users interact with our product. It helps us to see how users actually use our product vs what we anticipated they would do and helps us to improve our offerings and update our products to be more intuitive and useful, as well as identifying bugs or things that don't work as they should.

Likelihood to Recommend

It was extremely useful in identifying places in our product where things weren't functioning, or where it looked like action was available to the end user but in reality, it was not and therefore caused lots of confusion. It doesn't help as much in other scenarios to see what catches a user's Eye or where they go if they leave our application as well as an actual in-person interview would help with eye-tracking software.