Tips & Tricks
Discover strategies that help you make the most of FullStory.
- 28 Topics
- 36 Replies
Group office hours are here and available for signup! I’ve been really enjoying getting to use these sessions to dive into your questions about using FullStory. For inspiration, I wanted to share a few of the topics that we’ve discussed so far:Searching for sessions: we discussed how to find a user or session using specific event filters in FullStory. Specifically, we discussed finding users who have clicked by searching for the text or CSS selector of the element. This article goes into more details if you’d like to learn more about how to run these searches. Searching by URLs: building an event filter by URL is a powerful way to segment your users or build metrics to track KPIs. There are lots of ways to utilize this event filter in FullStory. This article talks through each of the components you need to create the right URL event filter. Finding friction points: one customer asked about how to find friction points easily, even in session replays where the site is masked due to priva
Today, in the product management dashboard session for product managers, I learned that I have the ability to compare trends to the past. This is super helpful when you’re trying to see if usage is going up or down. If you’re implementing a change and want to see the impact it has you can compare it to the past. For me, I am going to use if to see how many customers click into my product time over time, using it as a health indicator. Super excited about this feature!
We recently consolidated our login experience from two pages into one. We created a segment as we wanted to gather metrics on those who were going to the old experience and then onto the new experience*. We were able to set up an alert on this segment and send it into a slack channel. This was super helpful in helping us monitor the new user experience and was also so valuable in alerting us to the clients who were facing challenges logging in! *we couldn’t retire our old login experience until all clients were migrated to the new
What is FullStory Fridays?FullStory Fridays is a knowledge-sharing initiative designed to empower your team with valuable insights from the FullStory platform. Here's what you need to know: 🗓️ When: FullStory Fridays is held every Friday (or at a cadence that suits your team's needs). It's a perfect way to wrap up the week with actionable insights. 🧠 Who: The session is led by a FullStory subject matter expert (SME) who focuses on a specific area or product within your business or team. They are experts in extracting invaluable insights from FullStory. 🎯 Objective: The primary goal of FullStory Fridays is to share recent findings and observations with the entire team. It ensures everyone is on the same page regarding what's happening within their specific areas, thanks to the digital experience insights provided through FullStory. Why You Should Host FullStory Fridays:Data-Driven Decision Making: Uncover powerful data-driven insights that enable your team to make informed decisions.
Loved the explaination and detail about adding an Operator to multiple Metrics to get a % of total.ie: Rage Clicks / Total Clicks You can set different operators - division, multiplication, addition, subtraction.Format can be a number or percentage with 0, 1, or 2 decimal places; duration or currency. From
Our fantastic Customer Success team who’s worked with plenty of new users has curated an essential FullStory checklist just for you! They have found the following steps can help make the most out of your experience by maximizing the benefits of FullStory’s features. Dive into the checklist below to begin unlocking the power of FullStory!Value Method Benefit Who-Where Identify your users Uniquely identify a user with FS.identify API or FS.setUserVars Easily track users, even across domains and see their entire journey so you can access personalized user insights and optimize your customer experience. Engineer - your codebase or tag manager Utilize existing data Send over and utilize packaged events and properties about your users with FS.event API Capture detailed information Focus on key events Integrate with your CDP Enhance user insights Gain a unified view of user behaviour and experiences Engineer - your codebase or tag manager Al
Hi All,My team and I had the chance to hear from Barbara and Anna from the FullStory team about some new functionality they were launching around improving data quality that looked really exciting.I thought I would take the chance to share a quick implementation tip from one of my colleagues that we have found really helpful in tackling that same problem.We found that this issue tends to most commonly show up with clients who are using various Single Page Application frameworks such as React and Vue etc but also was very common on clients who were using frameworks such as Tailwind etc.The problem itself is that often you want to identify a particular element on the page for some kind of analytics purposes such as how often does, someone click this button but in order to do that you need to tell the tool (FullStory, Google Analytics, some tag management solution etc) what particular element it should be paying attention to.Quite often in those frameworks I mentioned above (but it is by
Ready to take your FullStory usage to the next level? FullStory Success Manager @casper shares expert advice and pro-tips for using 3 essential features in the videos below. 1) Search, Segments and Session ReplayLearn about the power and simplicity of using Segments with Search and Session Replay.Knowledge Boosters:🚀 Familiarize yourself with the filters available.🧑🚀 Create segments for groups of users you care about.🛰️ Find a point of frustration and watch the session to gain insight and empathy.Resources: User Segments, 6 custom segments for SaaS-y FullStorians 2) Metrics Set up metrics to track specific and vital interactions that are meaningful to your business.Knowledge Boosters:🧐 Start simple. Find a point of frustration or an action you’re curious about.🌌 Turn a star into a universe. Change the metric’s count or format to explore your data through a different lens. 📚 Build a library you and your business will want to keep coming back to.Resources: Introductio
Hi Folks!As you probably know, Conversions is one of FullStory’s most powerful features, as it can help you identify (and quantify) friction that’s getting in the way of your desired user flows.To make Conversions even more powerful, and to include performance (e.g. slow FCP times) as a signal, be sure to follow this advice from our Knowledge Base: But what’s advice without an example? Let’s look at a sample checkout Funnel that’s based on Page visits, Clicked text, and a Custom Event: When clicking the “Analyze” button or viewing a Conversion analysis for this Funnel, we can see two types of user friction that are opportunities for improvement: The Dead Click and Error Click pointed out in the analysis are good callouts, but since URL visits aren’t part of the original Funnel, page performance isn’t being taken into account as a signal. Here’s where small differences can make big changes! Below are two versions of this checkout Funnel that include “Visited URL” in the steps:This Funn
I am digging into various areas of our sites page loads and dead clicks. One thing I am wanting to see after seeing a couple of sessions showing a potential issue is how long a certain pop-up takes to trigger and how frequently the said pop-up is shown to determine potential impact. We have a loyalty program, and you always have to have at least one item in the loyalty order. If a user tries to remove the last item in this loyalty template a pop-up triggers to show that they need to have at least one item at all times on the order. But I can’t seem to figure out how to set something up to see when a user sees that pop-up and a bit of time before the pop-up triggers to see how long it is taking as well as the frequency of it.
During a recent training call we had a client ask, “when do I use a Funnel vs. Journey in FullStory?” and although a rather simple question, I found my rather complex and overly verbose answer worth sharing with the FullStory Community. I also welcome others to jump in with their take on how to answer this too. In short, Funnels are for defined user flows, i.e. we list out the known steps that a user takes, and Journeys are for undefined users flows, i.e. they start or end with a page or event but all the middle bits are unknown. Funnels = Defined FlowsWhen building a funnel, you’re going to be explicitly defining out the actions, visits, or events that your users are doing throughout the funnel. Users could be doing a number of things before, between, or after these steps as well – we only care about the success of defined criteria that is including them in our funnel. In the below funnel, we see three defined events, but people could have clicked Add to Cart multiple times, visited c
On the hunt for potential user frustration in FullStory? Great! You probably jump into some of the frustration signals that are out of the box in FullStory like Dead Clicks and Rage Clicks to laser in on these Sessions. And you might be tempted to build a Segment with something like the following:However, what you’ve build above is users who are experiencing Dead Clicks AND Rage Clicks AND Error Clicks in a session. Yikes! Although these would be super interesting and likely super frustrating sessions, you may have a very tight scope of sessions that appear in this Segment. The Filters in FullStory are in a way dependent events wherein users have to experience everything within the Segment, Funnel, or Metric in order to be included in the list. What is much more likely is users experiencing some frustration but maybe not all 3 of 3 of those filter criteria. Therefore, you might want to use [OR] logic to build out independent events, which will increase your scope and help you throw a
UX research is integral to building products and services that users love. It allows you to understand and dive deep into your users’ behaviors and needs and employ them to improve the overall user experience. Therefore, it is crucial to ensure that user research is done effectively for maximum impact.However, it can be difficult to implement all your user research findings, given the lack of time and resources. So, it is important to prioritize your findings so that you implement those that align with the business objectives and are the most pressing. We know given the sheer volume of research findings; this could be a challenge. Especially, when you have to communicate these decisions back to the respective stakeholders.Another reason why prioritization could be a challenge is that different stakeholders have different priorities. The priorities of a product owner would be different from those of the developers, for instance. It is important to not get lost amidst these internal prio
Server Side Events is an incredible feature that allows you to gain insight into interactions that happen outside of the FullStory recording script. You can find out what navigation steps lead up to or ended at a server event in your visualization. This provides a more complete dataset allowing you to better understand a user’s experience with your brand and not just the online experience. For example, you can find out information such as:Whether a customer created a support ticket during their journey on your website, or whether an interaction with support lead them to complete a purchase. If a customer made an in-store purchase after looking at your site online. If your marketing efforts resulted in customer acquisition such as email opens or clicks leading to an online interaction.If you’re not using this feature, you could be missing out on some crucial data. More info on it in our Knowledge Base article here and our blog post here!
I attended the How to Build Dashboards for Customer Support webinar. It was a great session! I immediately put into use a tip on how to quickly find your own session in FullStory to support an investigation:Open developer tools Access the Console tab. Type: FS.getCurrentSessionURL() The URL string that is returned as a response will direct you to the session for further review.
Has this happened to you? You’re trying to include multiple substring values for a custom event but cap out at 3 options. Then you have to create an “or” event to add additional values and everything starts to get messy. What if told you there was a better way? Now this doesn’t work for every “substring” event (e.g. Visited URL has substring), but it does work for custom events. If you start creating an “is” event and include all of your values, you’ll then be able to change “is” to “has substring” and retain all the values under a single event. You can even simplify this into a custom event. Say goodbye to messy “or” events that go halfway down the page!
One of the things that I think can be hard when skilling up with FullStory is sometimes knowing WHEN to use which type of card... “For X situation: is it better to use a Metric or a Metric Trend, will a Funnel be the best way to capture what I’m looking for or something else?” This “difficulty”/”learning curve” seems not uncommon, especially because in the absence of practice it’s easy for abstract ideas to blur together.With that in mind, I took all the Card Types, the Card Names, Dashboard Names and put onto a spreadsheet so I could see, at a glance, what were the most common card types, what type of dashboards they lived on etc -- and really, any general patterns.The thought/goal was that if I’m unsure of the “how”, I may more easily be able to identify where the thing I’m trying to do seems to fit in a more general pattern… and then, focus my approach. To see the forest and then determine what tree to look at.The attachment is that document, easily sortable, and also each item l
I joined the “How to Build Dashboards for Product Managers” webinar today and the item that stuck out the most was the use of text fields to better explain the dashboard’s metrics. I didn’t even realize the text fields could fit that much text, much less be able to include items like OKRs right in the Dashboard, to make the goals visible to all and help provide a focus to build your dashboard around. I can see the rest of my company utilizing the text fields more to better show strategic goals, desired outcomes, and other related items, to list alongside the data.
🎶 It’s the most wonderful time of the year 🎶 As you’re gearing up for Black Friday and Cyber Monday, there’s a lot to consider when it comes to FullStory and your DXI strategy! Have you prepped for an increase in volume? Is your FullStory setup ready to go? Do you have an internal action plan?We’re here to help make sure your holiday plans go off without a hitch. The Holiday Preparedness Checklist attached to this post has recommended resources, level of effort, and anticipated value assigned to help you prioritize each action item. Have any other tips for this time of year? Share additional ways you prepare below!
“Exclude people who performed these events” is one of the most powerful search tools in FullStory. Why? It makes it so simple to test your hypotheses. For example, let’s say you’re interested in seeing how conversions compare for users who clicked on a special offer vs. users who didn’t. To do this, you’ll need three things in FullStory: A segment of users who clicked on the special offer Another segment of users who didn’t click on the special offer And a funnel that defines the steps in your conversion workflow The exclude functionality lets you create both of your segments super fast. Create your first segment, then use the drag-and-drop to quickly save the inverse. Watch below as we change our segment from users who clicked the special offer to users who didn’t. Drag and drop to exclude events from your segment Now, we have two segments ready to go. Load up the funnel and choose “Compare users” to see how they perform side-by-side. We can now see exactly how effective our spe
Often times when setting up FullStory or onboarding new team members it becomes clear than a unified naming convention 📖 can be reaaallly useful to reduce confusion and increase speed to insights. Here are a few of our tips and takeaways: [Noun]+[Verb]It’s knee jerk for some to want to create Segments called something like “Clicked the Add to Bag Button” but if you make enough of these you’ll soon realize you have a growing list of “Clicked the...” Segments that become tough to scan. We recommend starting with a noun or the thing people are clicking or place people are going: “Add to Bag Button” or “Confirmation Page” and following it with your verb, like:Add to Bag Button Clicks Confirmation Page VisitsYou could take it a step further and add [Audience] to the front of that too, like:Prod - Confirmation Page Visits Paid Media - Add to Bag Button ClicksBut that might be overkill for you and your team, so to encourage adoption try to K.I.S.S. – Keep It Simple, Sillypants. 👖 “Funnel” f
Login to the community
Login with SSOLogin with FullStory
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.