This is a guest post by Gary Gaspar, CEO at Marker.io, a visual bug reporting tool for websites. Their team has released an integration with FullStory to help developers tap into the power of user sessions recording on bugs reported by end-users and clients.
I love FullStory!
As a matter of fact, Marker.io has been a paid customer of FullStory for over 4 years. Here is proof of my very first invoice!
For us, the thing that makes FullStory infinitely valuable is how easy it is to understand and reproduce user bugs.
For example, when a user reports a bug, we can look for that user's Session Replay in FullStory and understand the exact steps that led to a bug.
Unlike other tools such as Google Analytics where you don’t know exactly what your user saw or experienced, FullStory gives you that power out of the box.
Finding the correct session recording
Thanks to the Marker.io integration with FullStory, helping your dev team find the exact FullStory session to look at has never been easier.
When someone reports a bug through the Marker.io web widget, it will connect with FullStory and record the exact moment on the FullStory timeline at which a user experiences a bug.
Let's see how it works.
1. Let users report bugs
The marker.io website widget allows users and internal team members to report visual bugs without leaving your web app or website.
You embed a snippet of code in your website, and people will be able to report bugs with visual annotations and a screenshot.
For example, imagine a user tries to purchase a plan for your SaaS app, but they get an error. With the marker.io widget installed, this is how easy it is for them to report that bug to you:
2. Receive the issue
That’s where the magic happens.
When you have the FullStory script installed on the same website as the Marker.io snippet code, we will automatically grab the FullStory user session and attach it as a quick link inside your issue.
Here is an example of that issue created by Marker.io inside Jira.
Marker.io will not only capture the correct FullStory user session, it will also send you to the exact moment the person reported the issue in the FullStory session timeline.
This way, when your developer clicks this link, they will instantly navigate to the precise timestamp on the FullStory timeline.
3. Closing the issue
Finally, when your developers have resolved the issue, they can close it inside their favorite project management tool. (In this example, that’s Jira.)
By doing so, Marker.io will automatically notify the reporter that the bug has been resolved. What a way to offer excellent customer support!
Thanks to this new integration, you can review user sessions to understand the steps that led to bugs, right from inside your favorite issue tracker.
And for your users and teammates, feedback reporting could not be more straightforward.
Find out how FullStory’s Digital Experience Intelligence platform makes bug prioritization and resolution easier.
Request your demo today.