Stop Guessing! Start Debugging With FullStory Session Replay
Reproduce Bugs and Solve Errors In Record Time
Reproducing and eliminating bugs is a frustrating and expensive part of software development. These tasks take up a whopping 21 to 50 percent of software developers' time costing as much as $65 billion on debugging each year.
You became a developer to build, so why is half your time spent deciphering bug reports, deconstructing code, and replicating bugs?
What if that time and money could be spent building new features and innovating on new products, rather than patching up what's already been shipped?
Bugs Thrive in the Dark—You Can't Fight What You Can't See
You launch your bug tracking tool, navigate to the most urgent issue, and begin attempting to reproduce the bug so you can figure out what's breaking.
But you're faced with two big problems.
First, your information is incomplete, inaccurate, or unclear, so your debugging process is filled with trial and error—often merely guessing. Frustrated after many lost hours of productivity, you often have no choice but to close the ticket:
Second, this isn’t your first codeo. You know how difficult it will be to reproduce the issue, and as much as you like a challenge, it’s hard to summon the motivation for a task with such a large time committment and low percentage of success.
Might there be a better way?
Less Tracking, More Debugging With FullStory
With FullStory, you no longer have to waste time hunting for the beetle in the haystack. No longer are you or your developers stuck trying to re-create the conditions that led to an error.
Now, when your users encounter a glitch, you can replay the session to reproduce the exact chain of events that led to the bug. You see exactly what your user saw—when and where the bug occured.
No more guesswork. No more asking for screenshots. No more headaches. It's as simple as pressing play.
Get all the details you need: FullStory captures and provides you with all the additional clues you need to crack the case: UserAgent data, time of incident, IP address, screen resolution, browser type and version, OS, and more.
Find every instance of the bug: Using FullStory's powerful search functionality, you can find all instances of the bug and use that data to prioritize a fix.
Muster maximum motivation: And here’s where things get fun. Armed with the complete, accurate information needed to squash the bug, and buoyed by feeling the pain of the user who experienced it, you suddenly find that you’re eager to go bug stomping.
The pain of debugging is replaced by the euphoria of making a real difference.
Bug Solving Success Stories
Moosejaw, an outdoor retailer acquired by Walmart in 2017, found that FullStory helps add certainty to the bug replicating process when before there was none:
Before FullStory, we had no idea how long it might take to locate an issue. Now, we know it will only take as long as the customer’s session took. Jerry Hoopfer
Project Manager, Moosejaw
For boutique e-commerce site thredUP, FullStory has helped solve perplexing mysteries, such as why some customers were entering discount codes that shouldn't have existed. Like CSI for your website, replay helped solve the mystery:
Through watching session replays we were able to move quickly and fix it. We might have been pulling our hair out for weeks had we not thought to use FullStory. Dan DeMeyere
VP Engineering, thredUP
Travel Syndication Technology shared how FullStory has improved engineer happiness and day-to-day operations:
Going from a screenshot and a brief description to a FullStory playback session has made our engineers and QA life much happier. FullStory has quickly become an indispensable tool. David Gili Casals
Travel Syndication Technology
Report Bugs: Integrate FullStory With Your Stack
Integrations for Debugging
FullStory is most powerful when it's integrated into your software developmenet lifecycle stack. Below are some popular integrations we offer for issue and bug tracking. Learn more about integrations.
Now each bug report, project card, or support ticket will automatically link to the customer's session recording, showing you the error in question giving you all the bug-banishing info you need.
What more, even without integration, sharing session metadata—things like UserAgent data, browser, page URL, Viewport, and more—is as easy as copy and paste.
Reclaim Dev Time for Your Team: Solve More Bug Reports Faster With FullStory
Imagine your developers were able to spend more of their time building and developing. By reducing the time spent debugging and understanding software errors, they can get back to doing what they do best: building great products.
One snippet placed in the header of your site or app is all you need to record every user action—no maintenance and no manual tagging.
Read more about what it takes to get started with FullStory →
FullStory will not slow down your site. The script (approximately 30k, gzipped) has been carefully constructed and measured to ensure that it has negligible impact on the performance of any page on which it is embedded. The script has been built to consider page rendering and interactivity, UI thread, upload bandwidth, and DOM and script interactions.Read more about the FullStory script and performance →
We often get asked whether FullStory will work with complex sites. The answer to this question is usually yes, as FullStory captures all the elements that make up the DOM (Document Object Model), as well as all changes to the DOM during the course of a user's session.
Below is a partial list of what FullStory can record:
- HTML and CSS (and all other basic web page and app elements)
- CSS animations
- Vector graphics in SVG (including animations)
- Hover cursors and effects
- Embedded, same-origin <iframe>s
- Script-modified input values
- Window resizing
- AJAX URL navigation
- HTML5 <audio> and <video> playback
- Multi-touch events (on mobile devices)
There are still a few things we can't do. These are the most commonly requested things FullStory can't (yet) record:
- Shadow DOM
- Plugins such as Flash, Java, Silverlight, etc.
- Web components
- Local resources (e.g., "blob" URLs, Cordova apps, and Chrome extensions)
Yes, you can blend your own application-specific data into the user sessions that FullStory automatically records. Adding custom data, such as user ID name, customer pricing plan, etc., gives you the ability to hone FullStory's powerful search and segmenting capabilities even further to find the exact sessions you're looking for.
Additionally, you can block the recording of unwanted sessions by IP address, domain name, or user agent string. You can also block the recording of sessions generated by bots, and block individual elements on any page of your site or app.Read more about custom variables in FullStory →
FullStory Pro is competitively priced and easily pays for itself in the monthly time you'll save the engineering team on debugging. And that's just the beginning of the benefits FullStory can have on your bottom line. See how we can help you support customers faster and optimize conversions.Read more about FullStory pricing →
FullStory helps you gain maximum insights to improve the customer experience while upholding the highest standards of respect for every user’s privacy and intent.
Safeguarding user privacy is paramount, and a joint responsibility between FullStory and our customers. We diligently ensure that each FullStory customer's user data is securely stored and accessible only to that customer.
Per our Acceptable Use Policy, we require our customers to exclude sensitive information from being recorded. We automatically exclude Passwords and all credit card data. Customers also will want to exclude other sensitive information from within the FullStory app or by adding the class .fs-hide to CSS selectors on their site.Read more about excluding elements →