Name: Workshop: Configuring Fullstory to Maximize Insights
Uploaded: 2024-10-03T17:32:51.870Z
Duration: 1 h 40 s
Description: Workshop: Configuring Fullstory to Maximize Insights

Transcript for "Workshop: Configuring Fullstory to Maximize Insights": Hello. Hello. Welcome, everybody. I see we have some folks dialing in. Thanks for joining, and and we are excited to get started here. We have a, an agenda that is very full. So, in order to make the most use of time, we are gonna go ahead and start once we hit 1201. Like, I'm gonna I'm gonna be right on the money, but I will give folks a minute to get dialed in here. And, yeah, as you're joining, thanks for joining, and we're excited to get started. And awesome. Yep. I'm seeing that attendees number jumping up, which is a good thing. That means we have folks dialing in. So for folks who are just joining, thank you for joining. I was just saying we are gonna try and get started right on time here since we have a packed agenda, but, I guess the folks who haven't joined yet won't see this. But we'll we'll just get started with the intros, and and so hopefully more folks are able to dial in by the time we actually get into things. So without further ado, I I'm gonna go ahead and kick us off. So, yeah, 1st and foremost, like I just said, welcome, everybody. We're super excited that you're here for our workshop. So as the name states, configuring FullStory to maximize insights, that's what we're gonna be focused on today is, for folks using FullStory on the website, how you can best maximize your web configuration so that you and your team are getting the most value out of FullStory. So we'll remind you later, but I'm gonna ask you to log in to your FullStory account as we go and and truly wanna treat this as a workshop. But, yeah, we'll do a quick introduction before we actually get started with our content today. So wanted to start with introducing our team, in terms of who is presenting here today. I will go first, but I'm I'm joined with a couple awesome folks on our team. So my name is Brent. I'm a program manager here at FullStory. I've been here for over 6 years, though, and I've gotten to work on a few different teams, including our customer success and customer onboarding team. So very, very, experienced in working with our customers and a lot of the things we'll be talking about today. But, Van, I will let you introduce yourself as well. Sounds good. Thanks, Brent. I'm Van. I haven't been here as long as Brent, but it's 5 years this week. I'm currently director of customer innovation. But prior to that, I co created led our consulting services team for about 3 years. So I've been in the the seat of an architect for one of that, and then I managed the architects thereafter. So during that time, I I had, my team, myself develop a lot of the best practices, the techniques, full story implementation and configuration. So you'll hear me kinda sprinkle the conversation today with some anecdotes and best practices that we picked up along the way. Awesome. Thanks, man. And then I'll pass it over to Tim. Hi, everyone. My name is Tim. I work on our support team here at FullStory, and I oversee our community. I have only been here three and a half years, which doesn't seem like very long compared to Brent and Van. Awesome. Thank you both, for the introductions. And yeah. So before we get started with the content too, I'm gonna go over the, a few of the logistics today. So, a couple of things to keep in mind. We have a q and a feature in Goldcast. So You should see that in the top right of your screen. We wanna be answering your questions as we go. So we're gonna take some intentional pauses throughout each section to get to some of those questions. Tim's gonna be keeping an eye on those questions as they come through. So no need to wait until those pauses. Send those questions as you have them and, that'll that'll we're we're gonna try and get to as many of those as possible. We will also you'll see that request to follow-up button. We may use that if if we're digging into a topic and it and it feels like we're not quite getting through your questions, feel free to hit that button and someone from our team will follow-up with you afterwards. The last thing I'll note, we're recording this session, so we're gonna make it available afterwards. You'll you'll get an email about that, and and then we'll also post that on our event hub. So, yeah, those are the, meeting logistics. And without further ado, let's get started. So first and foremost, let's let's take a step back. Why are we talking about this? I don't wanna belabor this point and and share too many slides, but I think it's always important to talk about why we pick this topic, especially with a word like configuration. Not the most fun world word in the world. But if you're an admin in FullStory, you may already understand this. But but it's a it's a really important topic on Full story. I'll show one example here just as a quick visual that I to me, I think this this paints the picture. If you're jumping in to do full story analysis and you see dimensionality cards like the one I'm showing here on my screen, or or maybe you're trying to build a click event to to do an analysis. Or maybe this isn't you. Maybe this is a teammate. I think even if you're a developer, if you're looking at your screen and you're seeing what I'm showing here, it it's hard to understand this. It's hard to get up to speed quickly, understand the data, and it's hard to move quickly. You also run the risk that maybe your teammates are using full story a little bit differently, not using the same definitions for for each of these things. So this is just an example of elements and CSS selectors, but there's areas like this all throughout full story. What we want to do today is talk about getting your FullStory account and org into a place where your data is accessible. It is, you have a predetermined definition that's the same across all of your users. So that way you can get your teams activated in full story. They can start digging in, doing analysis, and finding insights. So this element's example, it's a small example, a quick visual. But to me, I think this in in and of itself, just looking at this quickly, the difference between all those CSS selectors and these defined elements, it makes it really clear. When you have your full story configured correctly, you're able to extract so much more value out of the platform. But if you're an admin, you may be saying, hey, that's great. I'm bought into that mission, but it's not that simple. And maybe you're hearing things from your teammates like, I'm having a hard time finding the data in full story. We're using different definitions. And then you as an admin, this last one hurts us a lot to hear, but we've heard it. I've been tasked with figuring this out and I'm not sure where to get started. That is exactly what we want to address today. It's something that Van and the professional services team work with our customers a lot to do this very thing. And so that takes us yeah. Yeah. Sorry. Go ahead. And I was gonna say we have these playbooks, we have best practices. What we're gonna do today is kinda give you a different way of looking at some of your settings. And we're gonna do that in the form of a dashboard. You may have used dashboards to look at insights or metrics to investigate, troubleshoot things. We're going to try and flip the playbook a bit and then use those same metrics and dashboard cards to just nudge in the right direction for some of the configuration that we'd like you to do. Awesome. Yeah. What led up to this workshop today, Van and I actually took a template that Van and the professional services team built. We worked with our products team to take that template, put it into full story, the app, and make it available to you. And like Van said, we'll get into the details, but the idea is let's use your actual data to inform where you are configuring your FullStory account. With the why being knocked out, here's our agenda for today. It's pretty simple. We're gonna start with teaching everyone how to save that web configuration guide. That's the the what I mentioned earlier of go ahead and log into your full story account because we want you to follow along. And then we're gonna be going through 3 of the 5 sections. We're gonna be talking about data capture, element configuration, and lastly, page configuration. So we're gonna try and pack a lot of info into this session. So, yeah, without further ado, we can now get started. So I'm intentionally having this slide here to say, seriously, I've said it a couple of times, but seriously, we want you to log in. We want you to follow on with us. So pause, take a moment, log into your FullStory account. And we we will truly give about 30 seconds to a minute here. Now while you're doing that, instead of making everyone sit here in awkward silence, I will explain as background music, if you will, what org we will be using, what FullStory account we'll be showing today as we walk through examples just to give that some context. We have a demo environment here at FullStory called Cargo. It is a a fake car rental experience where you can either list a car if you wanna list it or you can rent a car if you wanna rent it. Instead of a typical demo environment where everything's built out and it looks amazing, and that is helpful for painting the picture of where we need to go, we are doing the opposite. We have a demo environment that has not been configured correctly. The reason we did this is we want to do something that matches what our admins are actually experience experiencing. So if you're someone who doesn't have a full story account that's super set up, you should see some similarities with the examples I'm showing today. So that's what we're gonna be using for our time today. And, yeah, hopefully, that was some good background music, was was me talking about this demo environment. So there's your 30 seconds to a minute. Hopefully, you've logged into your FullStory account, and we will move on to the first part of our agenda, which is how to actually get this template saved in your account. I'll also just say from here on out, I'm gonna be sharing my screen from within this demo environment. No more slides. So, this is where we will be camping out for the the rest of our time here. So I have this template already as you can obviously see. But if you're logging into FullStory, there's a few different ways to add this template. The first one is if you click on the home button, which this side menu may be open for you, you can open and close it. But if you click on home, you will actually see our template menu right here across the top. And luckily, since this is a brand new template, we we can see the web configuration guide right here in the middle of our screen. But if you are viewing maybe this recording in a few months and and this is no longer here, I I do wanna call out that we have a template gallery that you can access here on the home screen. Or if you click this Create button on the left hand side menu, above all of your FullStory objects, there's an option to Create with templates. If you click this button, this is going to open up our template gallery here. Now we're going to be jumping into web configuration guide, but it would be a wasted opportunity if I did not shout out these filters here on the left. If you see a role that aligns to your role or if you see a use case that that makes sense to something you're working on, I would totally encourage you to check these out and explore here. There's a lot of awesome templates in here that make getting value out of FullStory happen so much faster. But today, what we're doing is configuring FullStory. I'm actually going to click on this web configuration guide. Now, if you're following along and doing this, the first thing I'll call out is it doesn't automatically save. If you can do your future self a favor and go ahead and save this template, that'll put this inside of your library in FullStory so that in the future, you can jump in and jump right to this template. Go ahead and click Save there. While you are doing that and giving it a name, I'm actually going to go back to my library and I'm gonna open up my saved template here, the web configuration guide with my initials. Awesome. Okay. So, that is that's how to save this template. While you're you're you're looking at at the at your template and you're probably seeing it for the first time, Van, I'd love for you to just provide, like, a, hey. Welcome to this template. Here's how we use it, and here's how this is a little different than your typical full story dashboard. Thanks, Brian. Yeah. We set it up to be something like an at a glance overview of the effects of how you've configured full story so far. As an example, you've all probably deployed full story, you may be already capturing various websites. If you go and create a metric and then you group it by URL host, you might notice that there's a website missing. You may notice that there's capture volume that's either higher or lower than expected. So what we're really doing here is just kind of spot checking things and trying to understand, you know, about your website, your existing capture given all the metrics and data that we're collecting. We've also taken some common keywords like error, warning, loading, CSS selectors that we've seen, and we've we've seeded some of the metrics on that dashboard, all of which is to kind of give you a nudge in the right direction for candidates that can be configured. Awesome. Thanks, Fan. Thanks for sort of the overview there. So, awesome. Like I said, the meat of our agenda is diving into this this dashboard. I just opened up a quick poll. Would love if you could let us know, are you able to save this guide and your full story account? And, honestly, if we're seeing a significant amount of no's there, that's where we wanna take a second to say what's going on. But I'm I'm looking at the yeses come in and looks like no no's. So what I will say is if you're not able to save this template, drop us a note in the q and a because we'd love to address that problem. But, I'm seeing no yeses, so I'm gonna close out this poll. And like I said, if you can't save the template, drop us a note in the, in the q and a section because we definitely wanna address that. Okay. Part 1 of the agenda, data capture. So this is a great place to start. It's it's usually where teams start when they're implementing for the full story full story for the first time. So I'm gonna scroll down to data capture setup here. And this section is all about understanding if your data capture settings have been set up correctly. So I'm actually gonna take us down to our 2nd row here, the data capture trend line and the by domain. Essentially, this is the best first place to start to see, do I see the right amount of sessions coming into my FullStory account, and do I see the right URL host coming in here? So that's what you're checking for here. If this looks as you were expected, that's great, but there's a chance that it doesn't. And and, man, I'd love if you could share maybe some of the gotchas that you have seen here from working with our customers. Right. I think most customers probably start with capturing all domains. That is the default configuration. In services, what we try to do is pivot early to just a more intentional capture. And so I kind of alluded to it, so did you, Brent, that when you look at that, trend line, are you seeing staging, QA, development domains that you may not need to capture? You may not need developer sessions, for example. So you can block those easily in settings. Really, we advocate that for 2 benefits. 1 is, you know, fewer sessions just means that your full story quota goes that much farther. But also when you mix production and non production data, it can tend to skew an analysis or worst case might send someone down the wrong path. So we just start out very early. If you've got production and nonproduction data, try and separate the 2. That's one way to do it with domain blocking. But if you've got, if you're an enterprise customer and you've got like an umbrella account, you can just create a entirely separate org and send that non prod traffic to it. Awesome. Thanks, Van. The other thing I'll call out too, we're not going to be going into details on taking action on every single one of the things we're talking about today, but that's why this template is so awesome. Inside of each one of these metric cards, you'll notice there is a link. In this, for instance, like capturing data by domains, if you're like, okay. I need to get some of these blocked or there's one missing here. How do I do that? If you click on that link and then click on open, it'll take you right to our knowledge base and right to the KB article. And the good news is something like this. It's it's a simple toggle on settings. So, thanks, Van, for that overview. And, yeah, that's that's, that's that's our first place to start is do we have the right data coming through and the right amount of data? So let's scroll back up to that first row here, and and let's talk about, what we're seeing here in these single metric cards. So the first two, identified users and analytic events. Simply put, this is showing you how many identified users you have and how many custom analytic events you have. And these come in through using our API. Now the thing to look at here is 1, is it 0? If it's 0 like it is for me, that means my team has not set this up. And this would be a good reason to go talk to my team and say, hey. Should we be sending in some custom user properties, for instance? If you are seeing data here, the next question would be, does this match what I'm seeing or expecting to see? Right? Like, if I'm seeing this many users in GA, am I am I seeing a similar number here? So we have a lot of, there's a lot of detailed documentation on our APIs. Van, is there anything you wanna add about these first two identifying users and analytics events? Yeah. I think just kind of sending in additional metadata to full story just begins to unlock some certain use cases. For example, we've got Tim on the line. You know, we might wanna associate a support ticket with that user session, and you can do that really simply by sending the email address or maybe the user's ID to full story, and Tim could just look that up when, he receives a ticket, for example. Another benefit, if you start identifying users, you can use the across any number of sessions option when you build a segment. And that gives you the ability to see, like, that user's journey across multiple websites that you might be capturing. Love it. And I I love your perspective, from some of those use cases you got to do with our customers and professional services. Keeping it moving here to console data capture, network data capture, these two cards are used in the exact same way as these 2 just for different things. We're checking to see, is this number 0 for either one of these? And if it is, that means this has not been enabled in settings. So console data capture, super important to get more context when you're when you're digging into an issue with a customer. We can actually see the logs in the console and get better context around, around what's going on if there is a problem. And I know, Van, you mentioned, I think we recently changed our default settings here. Right? So so we did. And a lot of that was because these 2, they're just simple toggles in your settings, but they were often overlooked. So if you're a legacy org, you may just wanna check on it, check to see if that's 0. The reason that we check to see if the console capture is 0 is because that ultimately affects the error click signal. So error clicks are dependent on the console. And we've had situations at some customer sites where they have, like, an another analytics library or some security tooling that intercepts those console messages. And if we don't get them, the error click signal doesn't work, and that's a pretty big one that tells you the website is either healthy or not. And then the exact same thing instead of network capture. Like, if it's 0, you have an immaculate website with no errors, and typically, we don't see that. So if it's 0, it could be that that setting is simply off or something's impacting it, and that's something that we'd wanna investigate in support or services. Totally. Thanks, Van. Important call out too. If you're on this webinar and you're taking a look at your data capture settings and you're not seeing zeros here, that's great. The purpose of this dashboard is to take a look at your data and ensure it has been configured correctly. Now Now on the flip side, if you're seeing things that are zeros or or not what you expected, that's what this is for. Right? Like, the purpose is take a look at what's coming into your FullStory account, assess where where you may need to go a little further, or have the peace of mind that, hey. This has been set up correctly. Yeah. And I think, Van, I'd be curious your perspective too on that. Like, is this something from working with customers? Is that something that customers typically build this dashboard once, never look at it again, or is it something they might wanna monitor over time? Yeah. I was gonna say, like, a general tip is kind of these are overall health metrics you might think of as, like, kind of the the efficacy of of capture. It's it it is worth monitoring. So you could either return to it, as frequently as you'd like, expand that time range, and if something looks off, kind of look at the historicals. For enterprise and advanced customers, this is where we we have a technique called canaries in the coal mine. We wanna set these up as metric alerts where there's a threshold so that when we have sudden drops or when we have sudden upticks, we know about it. Because we've heard more than a few times that, you know, from our customers, well, we accidentally remove full story, we didn't realize it, or we went live with the new part of the site. It had more traffic and didn't have sampling. So all of this, the alerts really just help mitigate that time delay in finding out that something is higher or lower. Then ultimately, if it's gone higher, it might inadvertently affect your session quota. Yep. That is a great tip, Ben. Thank you. Like Ben said, that is an enterprise or advanced feature. So if you don't have access to alerts and and that sounds like it would be helpful, we'd be happy to set you up with your account manager to to talk through, how to explore that. Van, I'm keeping an eye on time. I will say I I think I know there are some other cards here. I think it makes sense to keep moving though because I wanna I know we have some other things to get through. I'll call out at the bottom of this section. We have, some cards that will help you block unwanted traffic, like user agents that could be associated with bots or IP addresses. There's some really helpful knowledge based articles here, so I would encourage everyone to explore those and see if there's some opportunities to block some unwanted traffic here. Okay. But even though we're moving quickly for the sake of time, truly the spirit of this, we want it to feel like a workshop, and we want to answer your questions. So, Tim, I'll check-in with you. It looks like I don't see that any questions have flown through, but, yeah, we'll we'll we'll go ahead and and solicit some questions. So have there have there been any questions or anything you have noticed so far, that would be helpful to talk through? Maybe something that's confusing or or, yeah, any any helpful questions that we can chat through now before we move on to elements? Oh, I do see a question that that came in here from Brad. Can you share a bit about what FullStory is using to identify suspected bot traffic? Van and Tim, do y'all know the answer off the top of your head? I'm assuming it is the user agent, but I don't wanna speak incorrectly. Yeah. Yeah. That's the the gist of it. So we have, usually, bots will identify themselves in the user agent itself, and so we have some things on the back end to look for particular identifiers, that that we know are associated with a bot. Other times, though, it's just a bit of digging on our end, related to just knowing where, like, a a bot is located, where, like, a data center is located. So if you get a bunch of traffic from Ashburn, there's an Amazon data center there. And so often that can be associated with, bot sessions. But right now, if you go to, like, your data capture settings and block the popular bot UAs, those are just some, like, preconfigured, user agent strings that we know are associated with very common bots. And so, that can just help us kind of weed out those, sessions. Does that help, Ren? And and, Tim, I'll add. So you have 20 or so popular ones like Facebook and Google and likes web scrapers. That card, which unfortunately just doesn't have any any bots located in, it's looking for the robot signal that you'll find in full story so you can kind of look at how the metric is is constructed. That may pick up something that is a non popular bot, but for whatever reason is hitting your site. So you do wanna look at, like, where there's high amounts of traffic and then follow the article that's listed in the in the metric in the metric itself. It'll tell you how you can kind of, look at that user agent and then begin to kind of pull out a part of it that you block the the bot's future visits with. Awesome. Thank you both. I also opened up a poll. Let us know if you're finding things that you wanna take immediate action on. I'm seeing it looks like most folks are saying yes. But, yeah, we will, again, for the second time, we have a lot to get through, so I will move on to elements here. And a reminder, drop questions as we go. You don't have to wait until we pause for questions at the end of the section. If you see something as we're talking about elements, let us know along the way, and and we will, make sure to get to that. Oops. Hey, Axel. I apologize. I just hit the wrong button. Let me reshare my entire screen here. Sorry about that. Without further ado, let's get into elements. Elements, super important and helpful and valuable in full story. I used an element example at the top of this call. The the reason elements are so helpful is it makes your full story data accessible across your teams, standardized across your teams. And we've seen and heard from so many customers that once they get elements defined, their full story users are are able to explore so much more easily, which, of course, is gonna lead to to discovering more insights. So, what we are doing here is we have a a few cards in this section that are all aimed at helping you as an admin prioritize, where should I if I if I wanna do better at elements, where should I get started? And, Van, I know there's some context you wanted to add to since this is one piece of the element approach, but you obviously have done this a ton in in working with customers. Yeah. We we spend a lot of time on creation of elements and services. I mean, really the the purpose there is that we wanna produce a selector and a name that's validated for business use. And once it exists, you know, it it acts as a model for other users. So like when they see a dashboard and they say, that's interesting, I wanna go deeper, it gives them confidence that they can duplicate it, create their own. I also think of like element creation as it's a process. Like, your website is going to change over time. There will be new. There will be deprecated elements. So don't necessarily think of it as having to be exhaustive on day 1, but you do wanna look for those most important elements. Usually, those are the ones that are most interacted with. And I kinda just go back to there's an adage. You know, if it's important, it should be measured. In this case, if it's high volume, it probably starts with naming it because it is important. The other thing I I do wanna touch on because it comes up quite a bit these days is that topic of AI. So if you're not already seeing it, you may soon see it. There's a feature called element suggestions that's rolling out, and you'll find a generate suggestions button on the settings page. And that's gonna automatically find those high volume, clicked elements, for example. It's gonna suggest a name, and then what you can do is either accept or reject it, and then just repeat that process. So the the process that we're gonna show you is more or less the human led version of that. It may be helpful if you wanna name some areas of the site or elements on, you know, kind of a less trafficked part of the site that maybe not percolating to the top of those AI generated suggestions. Totally. That context, I think, is helpful. What we're doing here is on that human side of the house, how can we get the most bang for our buck in terms of building these elements? Obviously, starting with the most popular elements is a great place to start. Let's dig in here. So this dashboard, name top text elements. Essentially, what we're doing here with this card is we are grouping the the top clicks on your site and saying, of those elements with text, where are all those clicks happening? I think it's hopefully pretty self explanatory. Right? Like, the idea being if these elements are being interacted with a lot, they should be your top priority in terms of which element should you define first. But not necessarily all of these are gonna be good candidates. I I know, you know, Van, you wanna talk a little bit about when you're looking at this list, the types of things you're looking for? Yeah. There's still a little bit of judgment. Like, not everything is literal here, so you wouldn't wanna name, like, a, quote, unquote, $50 element. That element probably is something more like a a claim or a transfer or maybe it's it's buying. So you might name it based on the purpose, like that's the buy button. As a small aside, there's a a new feature called extracted properties and you can actually take out that 50 amount and associate it with the click. And so doing that, you might say, you know, show me all sessions in which users clicked something greater than $50 or sum up all the transactions for a day using a metric and kind of that extracted property. The other one that that's in this list is next, the next button. It's a good one to name because when you name something, you'll see at the bottom, there's some options to ignore rage and dead clicks. And so as you might imagine for a next button, people probably, like, click click click through to get to the page that they want that could produce a false positive rage click. It's one that we just know early on to be on the lookout for and ignore when we do the naming. Awesome. The context is super helpful. I'm the admin here. If I was sitting down to take a look at this list and say, hey, where should I start? Like Van said, the $50 one could be a good candidate to name even if we don't name the $50 element specifically. Maybe it's a pricing input. I I do know that it will be, but let's dig in. So if if I was an admin, I'm gonna start with the top. This is the one that's the most popular by far. So if I scroll down to the bottom, here's how we can go about naming this element. We filter by dimension. We can choose which text that we wanna see a session replay for. So I'm gonna grab the $50. Another small little full story trick, you can take out those online sessions, which I just find helpful to know I'm getting a a complete session that's that's already completed here. I'm gonna press play, and I'm expecting this to take me right to the moment in time where we see this click on the element and boom, there it is. I'm going to hit pause here and there's where the user clicks on that button. Now from here, now that we can see this element in session replay, I'm going to do 2 clicks. I'm going to click on Page Insights at the top and then Inspect Mode in the top right. From here, I now have the ability to zoom in on a specific element. I'm going to grab this $50 element, which you can see it will suggest a selector here. But if you scroll down on this tab, so again, you went Page Insights, Inspect Mode, we clicked on the element. If you scroll down on this right hand column here, there's an element section. If you are an admin and you found your element, you'll look for element and just click on Create element here. This will take you into Data Studio and this is where we will actually name our element. This is an awesome new part of FullStory, the app that didn't exist a year ago. Then could you talk us through when we jump into Data Studio from this point, where you would recommend starting and going about naming this element? The first call out is that selector that's a long string of text. That's how we've historically represented selectors. Below that, you can see a better visualization of the actual structure of that selector and shout out to Irv on the consulting team who pioneered kind of that visual indication. So that's gonna help someone that is maybe a little more savvy with a little metadata about the actual depth in the structure of that CSS. For those that are less savvy, but maybe those that still are, they will appreciate this too. We have an AI trim feature. So that's that trim button. And, Brent, if you wanna go and hit that, it's gonna automatically adjust the selector based on some of the best practices that we've learned about, some of the AI fine tuning that the engineering team did. And you can see what it did was select a it picked a selector that's very deep, so it's very specific to that element on the page. It's also picking the ID selector, which that's what a developer would have assigned. And as you might imagine, an ID is gonna hopefully uniquely identify that selector on the page. So, in my years of doing the architect role, this is like a 10 out of 10 selector and it did the right thing. And then the other thing you see at the bottom, Brent, if you scroll down to the options is there is the rage and dead click frustration signals that you can ignore as well. Awesome. Thanks, Van. Thanks for that overview. And I I like that because if you're someone who is a CSS selector wizard, obviously, there are tons of options to, customize this. And if you're not, you can just use that trim button and and, set you up very well. So the next step is giving this a name. You can add a description too to get some context, but I am just going to go ahead and click save here because that's all we needed to do. Now under element, under our session replay, you can see car rental price input exactly as I just named it right here. Moving forward, this element is named. Alright. Okay. Back to our the web configuration guide. Right? Just big picture process because that's really what we wanna help you out with. So if you're an admin, I would suggest going through this name top text elements list, try and identify those elements that are commonly interacted with giving those human readable names. I'm gonna make a quick call out to this this ARIA section here as well. ARIA elements are it's it's a common web spec, and and what we have done here with this card is we have actually grouped some of those, common attributes that are associated with this. So the thing to know here is is this is another way of prioritizing elements that are popularly interacted with and and could be really easy to name. I I won't belabor this point just for the sake of time, but I'll also say we're showing both elements in CSS selectors here instead of the text, which goes back to that example of the importance of naming them that I showed at the beginning of the call. The cool thing about this is as you name these elements, if you go through this card, you'll start to see if if they've been named, it'll actually show up on this list as the named element instead of that long CSS selector. So I I named this drop down menu element ahead of the column. We can obviously see that here. So these two cards in terms of elements is a great place to start to make sure you're naming elements that are really popular, to help get your team, like using full story really easily. Let's jump down to the next section though, and also friendly reminder, send us questions as we go. If you're trying to name elements and running to any hiccups, drop us a q and a, and we'll we'll get that here when we break at the end of the section. The next section on this dashboard is watched elements. Now I will say just before I dive into this, this is an enterprise or advanced feature. So if you don't have that plan, you won't have access to this. But like I said, like, of course, like, please reach out to your account manager if you're interested in exploring it. The reason we wanna show this is it's a really important part of FullStory that allows you to track not only when a user clicks on an element, but when that element appears. So really common example would be an error message. Some of your users will click on that error message, but a lot of times we hear from teams, I don't just wanna see the people who clicked on it. I wanna know any time it even appeared on the screen. That's where setting up a watched element will come into play here. And really good news, the in terms of how to set up a watched element, if you can name an element like we just did, it's just one extra click. So I'll go ahead and show y'all, how to do that. But let's start with this first card, which is watch top error elements. Essentially, what we've done here, Van and the team I say we. It was Van and our professional services team. They put together a lot of really common words, either the display text or CSS selector attributes that would be associated with an error message. This is a really creative way of saying, okay. For some of those users who did click on that error message, let's show those sessions, and then we can name elements from there. Now we can get the understanding of every time it loaded, even if a user didn't click on it. And, Vanna, I I'm gonna dive into maybe the uh-oh option and and start getting to the point where we can name this element. But but while I'm doing that, maybe you could chat a little bit about this list of, this this particular card and and how to use it. Yeah. And so it's it's not perfect, but it's intended to nudge you in the right direction. So you'll kind of do the process that Brent's showing. I think this watched element feature is one of our go to features and services because there's a lot of times where we have had technical problems on customer sites, and they have existing application performance monitoring. And for whatever reason, it didn't catch it. Either it didn't come through or it wasn't the right volume to catch the attention of, like, a site reliability team. But what we find is that back end issues, third party APIs, etcetera, they tend to show up as an error dialogue, kind of birds of a feather flock together. We've even had one quick serve restaurant that was operating in India. We'd see these spikes of oops, something went wrong dialogues, and we were able to track that back to, there was a back end issue where it was related to demand. So they would run these deals and their back end cloud provider just couldn't keep up. And what we saw were the errors on the front end. Yep. I love that example. And and, yeah, I think I think just really does a great job of painting the importance of of setting this up. And as I've been building this over here, one thing I wanted to call out, as I typed error, we usually have some suggestions of of some common elements to name. And if you type something, we will suggest based on what you're typing. And in this case, this is the error notification. And so if you see a suggestion pop up that aligns to what you're building, go ahead and choose that, we call it a role. We're building a lot of awesome things in FullStory, the product, to take full advantage of that, and dashboards and templates and things like that. So, a quick call out to that, but then as I'm building this element so I've done all the building. Underneath the name is that capture options, and all I'm gonna do this time is click that button for watch this element, and it is as simple as that. If I click save, we now have a saved element, and, yeah, we've also watched it. So, alright. I know, I'm I'm keeping an eye on time, and what I'll say is I wanna jump to questions. Van, do you wanna just give some quick context to to, like, watch the element errors and and why we have that down here? I know this one is important. Yep. And while the questions queue up. So, just a reminder that, like, you wanna watch the elements that really appear either infrequently or under important circumstances. So that's why we have that card there to show you where you're hitting rate limiting on a watched element. That would be your indication that maybe that element that you thought was infrequent is on lot more pages, and it may be worth adjusting that selector to be more specific or page specific. If you see something there, it's all about just watching the session, trying to get context, and then making the right adjustment. Awesome. Thanks, Van. Yeah. And, I open a poll as well too. Let us know if you're finding things that are helpful. And, Tim, I have been distracted with sharing my screen over here. Do we have any questions that we should address about element configuration? We have a lot of wonderful questions. I'm trying to keep up, everyone. Sorry. You're asking such good questions. I just have to make sure I'm answering you correctly. But we have one from Tony that I was just doing some research on to make sure I answer correctly. But Tony was asking about, using the sort of, like so in CSS selector searches, you can do some, special rules for, like, attribute starts with or something like that. And Tony is asking if you can use those same rules to create, like, a named element or define an element in full story. I want to say, as I'm looking into this, I I don't think the answer is yes, but I'm going to keep looking into it unless Van or Brent, do you know this off the top of your head? Van would know better for me. I I, Mike, I think I have come upon this question before, and I think the answer is that there isn't complete parity there, Van. Do you know? It's it's not complete parity. So there are there we support a subset of CSS, and I I too have to go back to the KB article just to kinda remember it. But, I mean, if it's in there, then my understanding, Tim, in my experience is that that usually works just fine whether you're naming an element and then also kinda translates equally well to to that element being watched as well. Awesome. So it sounds like, Tony, the answer to your question is sorta. So sometimes, it'll work. And this is a good call out for us to get some more clarity there on which one which rules will work in defining an element and which ones might not work, or might only work when searching for CSS. So love it. Awesome. Thanks both. Are there any other questions, like quick hitter questions we could get to now? Good news. I'm seeing yeses flow through around the question of did you find something to take action on? All yeses. So that's great. Hopefully, y'all can use these cards to name some of the most important elements and and make it easier for your teammates to jump in the full story. But, Tim, anything else before we move on to pages? We had another great question from Kelly asking about, our named elements. Are they when we create an export, so, like, a data export, do we see the name of that element in the API, export? Again, I was doing some testing on this as you all were just to make sure my answer was correct. So far, it looks like it's a no. But, again, I will defer and let Brent and Van, do you have do you have answers? Go ahead, Van. Well, so data export, no. You'll get the full selector as part of that. For customers that are on data direct, which is a new plan feature, there that data is included. So we will, include the ID of the named element itself. That information will go into your data warehouse, or there's even like a, get session or get session events API that exists on our developer documentation that likewise should include that ID. So not for not for the legacy data export, but for data direct and its, APIs that are coming out, in in beta right now. Yes. Awesome. Great. Well, for the sake of time, and I think we'll still have some extra time at the end based on how long I expect the last section to go, let's move on to pages. Our our 3rd and final, section of the web configuration guide that we're gonna dive into. But keep submitting questions. And if you have more elements questions, like, keep submitting those. The spirit of this, like, we really want to address whatever is top of mind and and what's blocking you from getting started here. So, pages. Let's shift gears. So pages is another really important topic. When you think about pages in full story, there's a few different reasons why it would be valuable to name pages. And when we are talking about pages, we are talking about defining patterns of your URLs. Now if you're not fully up to speed with what that means or you could use a refresher, I did wanna shout out something that one of my team members, a webinar that one of my team members led called Admin Academy. It's available on our our vent hub that goes deep into what a page really is and how to think about it. So we're gonna assume for for this session that you know what a page is, but that's available afterwards if you wanna dig further. The thing to know about pages here in terms of why it's valuable is, 1, if you define a page, you're hopefully adding a human readable name that, again, is gonna make it super easy for your team to run run searches in full story and and and dive into finding insights. The other big advantage though is if you're grouping those similar URLs together as one page, maybe all of your product detail pages, the advantage is you can start to use some really cool features, like our dimensionality cards or our journeys or page flow cards using pages and and unlock some really cool insights by viewing those URLs as groups of URLs, patterns. So pages are super, super helpful. Now I'll call out when you're building pages in full story. There's a few different ways to do it. We use machine learning in full story to to cluster similar pages, but we also have an API that you can use as well as user defined pages. So, Ben, I'd love to hear your perspective on the overall process of page definition, especially from consulting services? Because I know, like I said, there's a few different ways to build pages in full story. Yeah. You touched on some of them. I mean, I I go back to, like, the machine learning, which is the out of the box feature. It really does try to figure out the type of page. Don't think like title, but like the purpose of a page. We find that like sufficiently large websites, multilingual sites, or content diverse sites, Sometimes there's enough differences that it's the same page, but it will throw off the the clustering algorithm. So I kinda fall back to if you're seeing 100 of machine learn pages and that doesn't feel right, it could be a sign that for whatever reason the algorithm is just confused. Services, we kinda fall back to just more traditional methods. We we've used site maps. We've exported we talked about data export. We've exported URLs, and then just put those into a Google Sheet or your Excel sheet and and kind of sorted them to find clusters. If you've got an existing analytics library or past page naming convention, the easy button is really just to use our pages API to send that to us. This is also one of those areas where, like suggested elements, the team is looking at, you know, if we have the page pattern, if we know something about the page, can we just figure out what starting point for the the page name should be using something like AI? So one less thing to worry about hopefully in the future. Awesome. Thanks, Van. And, yeah, I mean, obviously, like like Van just said, there's a lot that goes into your page's strategy, and and it it is a little bit of an iterative process. Right? Like making sure that it is defined well, in full story. But what we're doing with this dashboard here, back to orienting around this dashboard and how to use it if I'm an admin, this is about prioritizing the pages and URLs that are most important and and making sure, like I said earlier, it's the most bang for your buck. So let's talk about these cards, what we're actually showing here, and how to use them. So if I scroll down in this section, the first card is top pages. It's exactly what it sounds like. These are the most popular pages in terms of page definitions and full story and in terms of page visits. So we're just going to stack rank those here. Now a few things to consider as you are jumping into this. So first off, if you see not defined at the top of your list, that means you have a lot of URLs that have not been given a page definition yet. Let's put that to the side. I think it's probably decently common, maybe not to be this high of a percentage, but you may be seeing this and we actually have a card, that's where we're going next to to address that. Let's talk about the other pages you may see here. The other thing is if you see human readable names here, that's great. That probably means someone has gone in and done some work to pages already. Maybe that was you. But I think what's really common for our customers is to see a lot of pages that look just like URLs, maybe with some extra wildcards throw in or asterisks thrown in. Something like this where you're seeing pages, but you're not entirely sure what this means. What that means is these are machine learned pages. We have built a machine learned rule. The name of the page is just that URL rule, but there's an opportunity to give that some more context, a human readable name, also to validate that it looks correct. If I was an admin and I am in this case, I'm trying to prioritize my work here, what I would suggest at this point is, and you can either just jump into settings, but what I like to do is actually I like to duplicate the tab, which Van reminded me yesterday of this too. Right? Like, when you're doing multiple full story tabs at once, if you do make a change, be sure and refresh the other tab to make sure it's up to speed. But I like to duplicate the tab and then jump into settings. The reason I like that is once I jump into settings, if I go under data management and then pages, this is where I can see my list of pages. So you can see what type of page it is. Now I will say we were having some trouble getting machine learning pages into our org, so I created some other pages here, that look like machine learning pages in terms of how they would look visually. But, if if you're trying to get get up to speed in terms of what these pages are, you would either see machine learning here to represent machine learning pages, user pages to represent if you created it, or API if your team has used that. But you can also sort these pages over here and you can sort it based on the 30 day volume, which will allow you to do some of that prioritization that we're doing in the dashboard of, let me knock out these most important pages first. What I would do here is essentially go through this list. If you click on a page, it will actually take you into Data Studio, but for pages. Then from here you can see the name, you can see a preview of what this looks like. There's a ton of things that you can do within this list. But if this definition looks appropriate to you, if you jump down to the URL rules and you're like, this is a good page rule, this is our search page, maybe come up here and redo this name, call it the search page instead, and then click save. That will allow you to have a better page definition so that moving forward, your pages will be under that, verbiage or new page rules. Yeah. And and, Van, I know you have some perspective of taking a look at this top pages list. Right? Like, in terms of how folks should prioritize these pages? Yeah. I think I think more specifically, kind of a a caveat on how we did things in the past and how we do them today. In the past, I think we were overly specific with pages, and that was more of like a point in time feature function gap. For example, we wanted to know, well, how many people were going from the tops page to the Jeans page in a journey, and we ended up naming a tops page and a Jeans page specifically. So pages are really all about the type of page. Like, this is a product detail page. These are product landing pages, which tops and jeans are. So now what we do is we advise that we want you to use page properties, and then you can kind of group those pages within the journey itself. You can also, like, create more granular steps by starting on the PLP page when it's the genes. All this to say, if you find yourself naming lots of pages and they have the same purpose but slightly different content, you're probably more likely need of a page property and not a separate page definition. The other thing, Brent, that kinda as you were going through the the data studio, is that pages have a a matching algorithm and the more specific page wins. So you are using like a star, and so that tends to group things. But if you ever have a reason, like and the star could exist in in the path too, like / search slash star slash something else. If you ever ever need to very specifically, I need just this page all by itself, use the full path. In that way, hopefully, the matching algorithm matches that full path explicitly, and then that page will kind of stand out from all the other ones that are gonna be grouped together. Totally. Yeah. And let's let's in fact, Van, let's dig into that example, because I I think there's probably a good example here within these URLs without pages where we can show you how to get more or less specific as as you're going. Obviously, what Vin was just talking about that would be if you already have the page definition and you wanna get more specific, and this might be the opposite if you're coming in with an idea of, hey. I need this page defined. So, the next card on our dashboard, top URLs without pages. Really, what we're doing here is we're taking the not defined pages. We're grouping those by URL path, which is how you make your rules, so that you can see of my pages that aren't defined, what are the most popular ones? And this is really a great way because I think what we hear from teams is like, hey. I don't have time to work on all of these pages. Well, if you only have a limited amount of time, this would be a great way to prioritize. Are there pages that are missing definitions that I can prioritize and and impact a lot of sessions? So, the way to use this would be if you identify a set of URL paths maybe that you think could use a a page definition. And, you know, here's an example of, like, host sign up Maserati model type. I'm gonna control c. I'm gonna copy that because I see Audi as another option here. If I go under settings and if I do create page, so again, this is within settings, data management, pages, and now within pages, if I do create page, I can actually paste that URL path here, select a host name, which I can select a specific host or domain or a more generic one. Then as soon as you do that, we'll show you a preview of this over here on the right. Now to Van's point, if I really cared about Maseratis and I was like, hey, Maserati model type page, I could take this approach. But if I wanted to be more generic, because really all these pages are the same, it's just different brands of cars, We can add in that wild card here, which we actually had suggested. And then now this is no longer the Maserati model type page, this is the car model type page, which is more generic. And this will allow me to do things in journeys to better understand across all of our customers and across all of our car brands, how are folks coming and going from these pages. I'm going to go ahead and save this. Van, is there any more context we should add here before we dive into questions? No. I think that was a perfect example of what I was saying. The last thing is just pages aren't retroactive, so they're a go forward type motion. Just keep that in mind when you start creating new pages and start wondering why some of the old historical traffic isn't attributed. It's gonna be a go forward manner. Totally. Yeah. That's that's a, that that comes up a lot with customers is they'll do something like this. They'll start knocking out these URLs without pages, and they come back to the dashboard and it's still here. At this point, you may wanna use a global time filter if you've already knocked a few of these out to say, hey, maybe in the past day, what are our top undefined pages? And you'll start to see those disappear. Awesome. Okay. We have about 5 minutes left. I I know that Van and I are also willing to stick around and answer questions, but I'll say, let's open it up here. Like, we'd love to hear what questions you have, whether it came up in pages. I I know there's typically a lot of, like, common, hey. This is specific to my page definitions. Like, let us know, like, what questions do you have about taking action here? Did you see something in your data that was surprising? Or maybe it has nothing to do with pages. It it's a it's a leftover question from earlier. So we'll open it up. And and, Tim, I'll I'll start with you. Is there any questions you see right now that we can get to? There have been amazing questions. I believe they are all answered at this moment. But if anyone has any last minute questions or if the answer you got doesn't quite capture what you're asking, again, there's that request follow-up button if he wants to follow-up with you after. Or you can always reach out to support at full story.com. We'll help you out, get your questions answered. But, we have a bit of time, I believe, for a few last maybe a last question, if anyone wants to hop in there. Yeah. Thanks, Tim. And, totally, drop us some questions. If folks are also I know we're close to the top of the hour here. So I one thing I'm going to do is I'm gonna go ahead and in case folks are leaving, I'm gonna open up a survey because we'd love your feedback, especially if, you have suggestions of where we could go. And and, yeah, like Tim said, what what questions do y'all have? We'd we'd love to get those answered. There's an interesting one in the chat about, buttons across the site being on different pages and how do you kind of home in on a particular button on a page. So just remember, like, elements are gonna be a thing that could exist across your site. I'd say that's probably where you might wanna use a defined event. So you'd have the element. You clicked an element, and then you can select net dependent criteria, either the URL or the page, and then you've got a defined event that's maybe the, you know, clicked buy button on checkout, clicked buy button on quick checkout, really depends on your your use case. But defined events, are kind of really really powerful way to sort of group together either different I would say, different events or just give an existing event a little bit more qualification. Awesome. Vanna, it looks like I saw a chat turned question come through that I think is gonna make you pretty happy about the AI the AI CSS stuff. We're working on it. AI, all the things, but, we we we gotta have a job to do. The services team needs to do something, but I think we're doing some really, really interesting stuff. And I think we've applied a lot of the AI to configuring your full story. Hopefully, we can do that more so you do less, but I can't wait to figure out how we do AI to help build metrics and all the other great things that we can do in full story today. Awesome. Yeah. Glad to glad to hear that. Responding to the the tree view is amazing on the CSS. Alright. Since we have a minute left, I am gonna launch the survey because we'd love y'all's feedback on on our webinar here today. But feel free and keep dropping questions or notes in the chat. Tim, please interrupt me if, we have a question come through. I I was just gonna note that, if you want access to this recording afterwards, we will send you an email. But if you, I'm gonna show our event hub, which is a really good place to see all of our on demand content, including this session eventually and some other amazing upcoming sessions. So we can send this in the chat. Yeah. There's a question. It's a great question. That's any other hands on webinars in the pipeline that like this covering other aspects of FullStory? So perfect timing, Brent. Love it. We do have some webinars in the pipeline, but no nothing that specifically mirrors this specifically right now. So we'd love feedback if there's specific topics that would be the most helpful. So, So, yeah, drop us a drop us a comment in that survey, and we'd love to hear the topics that would be most helpful to cover in a setting like this. And I'll add one more thing. If you see something that you just need more help with and you, would like FullStory to take a look at, use the feedback button in app. We do monitor those. I'll keep an eye on it for the next couple of days. But if it's related to configuration, you're just like, oh, this would be so much easier if only this, let us know. Awesome. We are at time. So unless there's any burning questions right now, I think I'm gonna go ahead and close this out. So thanks so much to everyone for joining. Thanks, Van and Tim, for all of your help, and I'm I'm glad to hear that this was helpful. And, stay on the lookout for this, recording on demand. Thanks, everyone. Thank you.