Connect with, learn from, and get inspired by fellow DXI enthusiasts
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.
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!
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
🎶 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!
Hey FS Community,Had a great time at Spark last week; now back to work! As I’ve been reflecting on the inspiration and ideas to put to use, I’ve been thinking it would be nice to be able to connect with other DXI-minded individuals on the FS Community that are specific to our industry.We’re in the wine business, and have only been using FS on our site for a few months now. I’m enjoying the learning process and excited to see what else we can do—but we didn’t ever run into anyone else at Spark to network with in our industry. I noticed that there is a “Groups” section of the community, but no way to create anything new. Would love to be able to make a group solely for users from specific industries, or that use the same platforms with FS. (as opposed to going to the general section and prefacing each post with something to the tune of “any other wineries here do this?”)Is this a community feature that may come in the future?
Hello, hello to this week’s new Community members! We’re so excited that you’re here. I hope that you’ll find this space helpful as you ponder FullStory questions, brainstorm solutions to your latest challenge, and look for inspiring new connections in DXI.A few tips for getting started:Introduce yourself here - we’d love to learn more about you. Post a question - let us know what you’re working through, and we’ll share tips to help out. Discover insider alpha/beta opportunities - our Product Lounge has a few new ones for you to check out! Note that the Product Lounge is only visible to users with a Business or Enterprise plan. Connect with other community members - sign up for a Coffee Connect to meet each other 1:1. The coffee’s on us! ☕Happy exploring, and thanks for joining in! @Camila @Leonardo Santos @LetiPeuser @jpalawagapt @marisalevy @gloria @Michele_Hostfully @Jing @nmelo @ast0004 @turksavas @Gowri1505 @stujardine @Curlz @terrencef413 @Garrett
Warmest welcome to this week’s new members! We’re thrilled that you’ve joined the FullStory Community. I hope that you’ll find this space helpful as you ponder FullStory questions, brainstorm solutions to your latest challenge, and look for inspiring new connections in DXI.A few tips for getting started:Introduce yourself here - we’d love to learn more about you. Post a question - let us know what you’re working through, and we’ll share tips to help out. Discover insider alpha/beta opportunities - our Product Lounge has a few new ones for you to check out! Note that the Product Lounge is only visible to users with a Business or Enterprise plan. Connect with other community members - sign up for a Coffee Connect to meet each other 1:1. The coffee’s on us! ☕Happy exploring, and thanks for joining in! @JMoreno @SoryChan @KateOurPlace @alineataulo @Dante @gardn2jt @lauriem @danr @jtromblay @Jeremy Goodwin @Jeff Wright @mindy @jnlowe @mark @Tjacobsen @ShandaJHurst @Nancy PB UX
We’ve heard that many of you are interested in connecting with others in DXI to collaborate, build relationships, and share experiences. To help, we’re launching DX Coffee Connects!Here’s how it works:Sign up to be matched with another member of the FullStory community. We’ll introduce you via email and send you both a gift card for coffee (or tea, whatever floats your boat). You’ll schedule a 1:1 chat whenever it works best for your schedules.Use your chat to make new friends, discuss DX challenges, and share ideas–and come back anytime to sign up again and meet someone new.Happy connecting!
“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
I’m excited to welcome this week’s new members to the FullStory Community! I hope that you’ll find this space helpful as you ponder FullStory questions, brainstorm solutions to your latest challenge, and look for inspiring new connections in DXI.A few tips for getting started:Introduce yourself here - we’d love to learn more about you. Post a question - let us know what you’re working through, and we’ll share tips to help out. Discover insider alpha/beta opportunities - our Product Lounge has a particularly cool one pinned to the top of the page 😎 Note that the Product Lounge is only visible to users with a Business or Enterprise plan. Happy exploring, and thanks for joining in! @Tracey H. @kward @BookkeepProductTeam @phornby @kellycashin @laurenmay @bragur @Abraham @Ranjith Sundarrajan @parag.kulkarni @anna @Filman @Danny Sehr @annie @Alba-molina @astanfordhr @Shelly @kenlilly @clara.noom @Kayleb @slapaix @Alex W. @benchun @merc @MikeOren @lisag @Kim @tendoux @aaron.repowr @sabrina @
Happy Wednesday, folks! Thanks to everyone who has participated in our early access test of the FullStory Community so far. It has been so exciting to see new relationships form and questions asked and answered. This week, we’re slowly opening up access to larger groups of FullStory users. You can expect friendly new faces and more regular content from the FullStory team. 👋 Welcome to our new membersSpeaking of those friendly new faces, please give a warm welcome to our newest members! Thanks to all of you for joining us this week. Feel free to say hello over in our Introductions thread or create a topic to jump right in ask us your burning FullStory questions. We’re here to help! @ebarker @rob @Ben Bryant @genemorita @Chandler_Albrecht @chandramuralis @david e @rolmt07 @readychassis @dpham70 @jarlewis @pedro @David Mead @davidt0dd @FreshBooksAnnie @MFalley @rama.meenavilli @krobbins 🤗 Introducing our new Community ManagerYou’ll also notice another Community Manager, @lindsay, hangi
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
FullStory’s new Home experience provides a personal workspace for your own DX exploration. Right out of the box, you’ll see curated metrics that highlight what’s Happening Now, Engagement, Find & Fix Issues, and Performance Errors. These are designed to help get you started, but Home is yours to personalize as you see fit. Here’s how to make it your own! Add SectionsSections let you organize and label a group of cards. Create a new section by clicking the vertical ellipses on any existing section. You can also reorder, remove or duplicate sections. Name these in a way that makes sense to you and your personal workflow.Add or customize sectionsRearrange CardsAll cards are drag and drop. Simply click and move cards to add them wherever you’d like them to go within a section, or use the ellipses to remove them, duplicate them, or change the card format. Rearrange cardsThere are four formats to choose from–Small, Medium, Large, and Playlist–so you can view your data any way you like.V
Observation: We noticed for one of our clients an increase in traffic to the /logout page, but were suspicious that users were organically deciding to log out more. Hypotheses: H1 The increase in visits to the /logout page is not a direct result of user behavior and H2 this increase will results in a more negative user experience as it forces users to change states without their expressed intent. Findings: To understand if users were visiting this page by their own volition or were being sent there we used Exclusion Filters to find users who visited the page but didn’t click on any text “Log Out,” which is the CTA in product to get to this page.So What? For our client and their users’ privacy, we aren’t sharing anything specific, but we did confirmed a dramatic increase in visits to /logout, which was associated with a change their dev team made to the session time out threshold.For our second hypothesis, we won’t be able to validate this without qualitative work, but what we can do i
There’s a ton of great thought leadership on digital experience, and I thought it might be helpful to share a few of FullStory’s favorite reads, resources, and follows! Our Product Managers, Product Designers, and Product Marketers listed these sources as some of their favorites for staying sharp. Duarte’s DataStory: A book that helps you understand how to explain data through the lens of empathy to create persuasive narratives that drive action. Nielsen Norman Group’s UX & Usability Articles: Research-based articles about UX, interaction design, user testing, web usability, and more. Simon Späti's Data Engineering Blog: For genuine news on the data ecosystem, including data engineering, big data, Python, open source and ETL. Shreyas Doshi: A great follow for those interested in product, strategy, organizational psychology, and more. Lenny Rachitsky’s Weekly Advice Column: Lenny writes about product and growth–primarily for PMs and growth leaders. The New Gold Standard: While th
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.