Video: Admin Academy: Create Data Harmony for Your Team | Duration: 3620s | Summary: Admin Academy: Create Data Harmony for Your Team

Transcript for "Admin Academy: Create Data Harmony for Your Team": Hey, everybody. Thanks for joining. We're gonna get started in just a second. Welcome. Welcome. Just gonna give it a minute for everybody to join, and then I'll I'll kick things off, but thanks for being on time. Hey, everybody. Thanks for joining. Looks like we got a good group, so I'm too excited to to wait any longer. So I'm just gonna go ahead and kick things off today. And, and yeah. Thanks, thanks for joining. Welcome to Admin Academy. We're super excited to have you here today and guide you through data management best practices so that you can help you and your team analyze your data easier and faster. So my name is Chrissy. I'm joined today by Djanay. We're both on the customer success team here at FullStory. D'Janae is going to be helping out with the the chat and the q and a, sending resources to you all. And then if you have questions throughout, we we want you to feel comfortable and confident. So the minute you think of them, feel free to enter them into the q and a tab, and then will will help respond. We may answer some questions out loud and then we'll definitely make sure that we leave time at the end for any questions as well. Lastly, this session is being recorded and, you will be sent a copy of the recording, a link to the recording 24 hours after today. So you'll get it emailed to you tomorrow. You also be able to access it if you go to our event hub. So, today, you know, really just focus on, less of the the clicks, but more of like the conceptual, what we're going to cover in terms of best practices because you can always go back to that recording and watch the clicks. And then is also gonna provide some additional resources. So, you know, you can always go to our help center and and get more of those, you know, exact how to's as well. So this this session, was built with you in mind as full story administrators and architects, and here's what we're going to cover today. So we'll talk about data management and then how it can help you and your team better utilize FullStory. I'll walk you through our data management tools known as Data Studio and Data Recommendations. Those were rolled out this year and they're going to help you define your CSS with confidence by seeing what you're actually defining. So you don't need a a developer to do this. You don't need any developer experience to do it. If I can do it, US can do it too. And you're going to be able to assign more readable names to your data within FullStory so that your team can unlock value faster. And this, as I mentioned, this is for architects and administrators. It's not my intention to be exclusive here, but the reason is because of the access level that you have. You're gonna need that that level in order to do most of what I'm gonna show you today. So if you're not, you can either request it through, you know, your account owner or you're welcome to just hang out and observe some of what we're covering today too. So let's dive into what you may be currently experiencing, why you may have joined today, and, you know, curious to see if you all have experienced any of these questions. Maybe you've asked them yourself or maybe your team has come to you with them. And it's, you know, how do I track click activity on a button without text? Our product page is a series of URLs. How can I find insights about the activities across them? And it's time consuming to use the event filters for a common activity each time I create a new analysis. So I keep saying, you know, what you and your team may be experiencing. Right? And that's because with the access level that you have, you have more power than the rest of your team. So if you implement the best practices that we're gonna provide today and then utilize the tools that I'm I'm gonna show you, Your team will thank you for making their their lives easier, and I'll show you some of how that, applies to what they go and create in full story. But really, it's gonna help you be, you know, the data hero that your team needs. And, you know, it's gonna help you and your team as a whole measure your analytics at scale, increase data accuracy and consistency, and apply semantic meaning to code. And really the name of the game here is today is not an overly technical session. I gonna walk you through what you can do on FullStory with tools that we rolled out so that you can do this in a very no code or low code way. Okay. But first of all, if if you are unfamiliar or even if you are, I wanna just quickly talk for a second about some, some, you know, terms that we're gonna use today, and that is page, elements, and event. So I just wanted to orient ourselves before we jump into full story and dive deeper into these. But whenever I'm I'm saying page, what I'm really referring to is a defined URL or a group of URLs across your site, like a homepage or a search page. When I'm referring to an element, that's the yellow you'll see on the screen, these are just some examples. I'm using our, our demo site. It's a car rental site that our engineers built, which I'll be using for our examples today. But you can see an element is a CSS selector that you essentially give a name to. The easiest way to describe these is you can think of them as the nouns on your site, like button or a search field. You could see there's there's the search icon that become a host. And the reason why it's helpful to name these is because, as I mentioned, that the buttons may not always have text. Right? So it's it's essential to name these so that we can more easily find these later. And then lastly, an event is a behavior like a click or a visit that your users are performing across your site. Any questions about what these terms mean? I wanna make sure these make sense before we go, But I will talk about each of these in more detail, as we go for the next, 40 minutes or so. But any questions so far on on these? None yet, but I'm sure there'll be more. You're good. Let's dive into what I think is the easiest concept because everybody knows what a website is. Right? So let's talk a little bit more about pages. And like I was mentioning, we're going to use our car rental demo site as an example. So you know, what you're seeing here is our homepage. And if I were to, run an analysis, right, I could just use the the link here, the the home page link, but I could also define it as a a single page. Right? And I could just name it something. And I'm gonna show you how to do that in full story, but I wanna talk about the 2 use cases for pages here, right, which is a single URL. But it could also be helpful when you're defining multiple URLs. So if you have something like this is considered our our product page. So whenever you go to rent a car, you're gonna land on this this booking page, this product page. Every time you click on a different car, you're served up a different link, in terms of the the end of the link being a different numbers. That's how we differentiate between which car our customer is choosing. But, you know, it may be helpful for me to track behavior across all of these sites rather than just each site individually. And a great use case for this is heat maps. So let me show you what I mean by that. Let me jump into full story and go ahead and create a heat map. And heatmaps are our page driven insights, right? They are used to analyze total click or scroll behavior aggregated on a single URL or across a series of URLs. So you can essentially see, once I select the site I want to look at, it's going to get populated below and we'll see all of that behavior. But I'm required to choose either a URL or a page. And if I wanted to, you know, look at that product page with the you remember that slash search slash number, this is how I would be required to enter it. So I would need to say urlmatches/search/ and then I need to put an asterisk there, because one sec. Let's see. It's a little bit, it's even a little bit wonky for me. But what this asterisk is doing is acting as a wild card. So it tells full story that anytime there's a number, any any, anything that occurs after that slash, you know, pull in all the sites that basically match that. That's what that asterisk is doing as a wildcard. So I would need that knowledge either as you or somebody on my team if I wanted to access information for click behavior across all of those different sites. And you could see here, right, you see like the number after the URL here. If I click get a new image, I'm gonna see another one. So this is telling me that there are on this element, you know, car price, there's 9,200 clicks across, all of these different sites. So that might be helpful for me to validate, you know, what's going on with my my site. So let me show you how much easier it is though if you were to define this as a product page. Now we've already predefined it here, so I'm going to find it using page. And it's it's called the product page. So that's all I need to do is just search for it, find it, and I'm done. And if we all refer are referring to this as a product page, it's gonna be super easy for, for people to find it. Not only that, but if I'm not super confident with using wildcards or URL patterns or I mean, you even saw the the struggle that I had and I use full story every day. It just makes it a little bit more challenging, and I think, it it may be, you know, maybe these folks won't be as confident that they've selected the right page. So if you set this up ahead of time, it's gonna make it a lot easier for everybody. Okay. Now, I want to jump in and show you how to actually create that. So give me one second here. Okay. What I'm going to do is go to settings. So I'm going to do that by hopefully you can see my mouse here, but I'm going to click in the top left and I'm gonna click on settings. And if I scroll down, this data management section is where we're gonna spend a lot of our time. That's why we keep talking about data it's, it's in this section, right? So we're going to go right to pages and I'm going to see a list of all the pages that have been defined. But to create a new one, I'll click this create page button. So let's go ahead and click create page. I'm immediately brought into Data Studio. This is a tool we recently rolled out and it's going to make it easier to define your data. And that's because this is it kind of acts as a WYSIWYG, right? If you've ever used a tool where, you know, instead of having to like, you know, create a site from scratch, you can use WYSIWYG. So it allows you to visually see the data that you're defining so you can feel confident about your data quality and that you're choosing the right page. So here's what I'm gonna do. I'm gonna look up the the route to the URL, which is that's technically my home page. And then I'm gonna type in that path right with the wild card in it because this is exactly how I want to define, that page. And you could see there this is the product page. This is exactly what we want. So I'm immediately gaining confidence. I'm in the right place. And if I click get a new image, I should be served up a different product page. Right? Different car. I mean, I would love to, rent that car, but this is not real. And, another way to gain confidence is on the left here. If you click this drop down, you can see the 7 day volume. So you can actually see the the click behavior. I can also see the URL paths that people went to. So I'm really getting confidence here that I've defined this correctly. I can see that it's the right page and I know that, I'm good to go. So you know what I would do is name this the product page and then I would go ahead and click save. Now we've already defined this so you can see I'm actually, alerted that it's already been created. And if I click save, I, you know, I'm gonna get I'm gonna get this error. So this is also helpful because we've built these tools so that, you know, they're essentially foolproof where you you can't accidentally create multiple definitions for the same thing. And, you know, from here, if if I wasn't sure what this was called, like, a cheat code is if you click this group by and you click page, you're gonna see that I've already defined it as the product page. So then, you know, anytime you perform an analysis, you could say, okay. This was predefined. Either you can go in and edit this and rename it or this is the one that you know you're gonna wanna perform analysis on. Okay. I just covered a lot, but Data Studio is such a powerful tool. I'm gonna show it it to you a couple more times for examples going forward, but any questions you have about Data Studio or defining pages? No questions yet. I've thrown a couple of resources on pages and heat maps and, Data Studio, in the chat. So feel free to, click those links and save them as bookmarks for later. But you're good to go, Chrissy. Thank you, Dijanae. And, you know, keep the questions coming, type them into the q and a. We'll make sure we we stop and and answer them. I don't wanna go, you know, speed through this and not answer your questions. We actually just got a question, from, Bohan. I hope I'm pronouncing your your name correctly. The question is if we're already passing through, page names through, variables and and properties, is there a documentation on how to capture those in a full story? So, Chrissy, you if you wanna go ahead and grab that one, or I can jump in. Yeah. Go for it, Tishanae. So if you are already passing that information in full story, then it'll actually live in the section where Chrissy, was just in. So if we are if it's a page, then it'll be in this list. So the name will be there, and any references will also be there. If it's not coming through, if the page names are coming through as a different kind of, custom like, if it's an event as opposed to, you know, a page, then that's a little different. But if you're if you wanna make sure that that page is coming through, then you can go to your settings, go to pages, and you should see it in that list there the same way, we're seeing it here. Thank you, Dijanae. Yeah. I I'm not gonna delve too far into this in this session, but, you know, if you were to scroll down, you'll see machine learning is is automatically turned on. You you can turn it off, but if you've got it on, you know, you'll see in your filter by, you can see the, machine learning pages. You could see all the ones that have been generated through that machine learning, or you could see all the ones that were defined by a user. So something that you or another administrator created. And then if you have the the API, that can also pull insights for you too. And I think I saw one more question which is, is it important to always click get a new image to make sure it's the accurate page? I would say yes. I think that's a that's a best practice that I would adopt. You could do it 2 or 3 times probably, and that should give you, enough confidence. And then Chris, let's see, slash search asterisk won't include slash search slash asterisk URLs. Right? I believe that's right. Can you put a wild card after? Do you see that question, Dijanae? Yes. Yes. So you can put a wild card right after, and that will just capture anything that comes after that, including, if if there's more than one backslash or not. So it will actually include, anything that comes after. So that that search, with the backslash and then the wild card would also be included. Great. Thank you. Mhmm. Okay. We got one more. You wanna answer this one too? Is the one about Data Studio? Let's see. There's one more. Is it not the other way around, /search/asterisk would not include slash search, wild card. It's not the other way around. Yes. Yeah. So when we put the backslash and then we put a an asterisk, what we're saying is that there there has to be like, we're following this format. Right? So when there's a backslash and then the wild card, anything that comes after the wild card will be included. But when you put that, that the, asterisk right after, that means everything after that. So that's queries. That's anything. So it's just a little bit more general. So, the formatting is important and it's highlighted in that article, as well. So I would take a close look at that because I can't tell you how many times, a search, you're you're building something and it it just comes down to the syntax. So search would not include no. It would not, Veronica. It wouldn't. Exactly right. Awesome. Thanks. And then the last one is a good tee up, which is can you use Data Studio to name and visualize watched elements as well? Yes. And I'm gonna show you how to do that next for both of those. Awesome. Great questions. Keep them coming while we're going. I'm gonna pass the mic back to you, Chrissy. Thank you. Okay. Let's see. Let me get oriented real quick. If you're not sure where to start with pages, if you're curious about, you know, the the highest visited undefined pages, I'm gonna show you how to do this at the end. And for now, I just wanna show you a a quick shortcut to get started. This is another tool that we rolled out this year. If you go to your settings and you head down to data management, it's called data recommendations. And, essentially, what this is is a a list of commonly occurring pages, that also includes elements as well, which we'll talk about in a sec. But it's the commonly occurring pages across all digital experiences. We also have them for ecommerce. So if you're in retail or ecommerce, you could check these out too and, see here. So if you're not sure where to get started, this is a great place to be like at minimum, you know, this is kind of a checklist. This is the minimum recommend recommended pages. And, what it does is once you name a page, you can then assign it to this this role. So I would go in here and we've already defined the 404 page, so I would go and find that. If it wasn't, I could click create page, go make a definition for it, apply it to this 404 page label. And what that does is you'll see it in a second, but it basically helps to prioritize these these pages as well so that when you're performing analysis, the four zero four, the homepage, the sign in page, those are gonna appear first on my list. So instead of, like, having to search for it, it'll be easier to to find it. So it's extremely helpful for all industries, but I will say especially for ecommerce companies, and especially because if you if you assign enough of these roles, I won't tell you exactly which ones, but there's help center articles on it. But if you sign certain pages and elements, it actually unlocks more insights for you. It unlocks, templates, and it unlocks conversion signals too. So this is a great way to get started. And yeah, any questions about data recommendations? One more thing I'll say is that because you can use this as a checklist, if something isn't relevant to you, you don't have a four zero four page or a sign in page, you could just click the skip button and you could see this percentage goes up. So if you treat it like a checklist, then, you know, you can try to get this to a 100% by either defining a page, clicking it here, or, clicking skip until you get to a 100%. I'm gonna show you one more use cases, use case where pages comes in. And I'm gonna jump back to the home page because I don't think a lot of people know about this, but I'm a huge fan of templates. So if you click on templates here, all templates, this one is especially helpful for product management. It's a product management dashboard. You click on product management, you will find the product manager dashboard. And this one focuses on page level insights. It it's prebuilt. Anybody can access this. And you can see there's there's 9 plus metrics built for user engagement, for frustration signals, and this is all at the page level. Right now, what it's doing is it's analyzing my home page. You could save this, right, and then save it to to your library and make it super easy, for your product managers to save time. Because once you define some of those whatever is a commonly occurring page for you, then they'd be able to go in here and click. Right? And let's say I wanted to analyze that product page to see how it was performing, I would just click it and check it out. All of these insights just automatically update. It just makes it super easy to just, you know, use this to to to update the analysis across, all of this for the product page. Okay. We we talked a lot about the benefits. Let's just, you know, round it out. So, you know, naming your pages is going to intentionally group similar pages together, which is going to promote accuracy and features like heat maps and and journeys. We didn't talk about journeys, but it's huge in journeys as well. More user friendly because it does not require URL path structure, which nontechnical users may find difficult to use in filters. And then, it promotes user discovery by providing a more curated list of pages that folks can easily find. Okay. So now we're we're oriented to how to use data recommendations and data studio. So I'm going to walk you through now how to use these tools with naming elements and watched elements. So as you may recall, an element is a CSS selector on your site that you give a name to. The CSS selector is code that your developers use to help, bring visualizations to your site. But it's what we use at FullStory to help define activities that are happening on your site. And, as I was saying, you could think of these as as the nouns on your site. Right? Like a button or a search field. That's probably what you want to track activity for. Right? So when your CSS selectors on full story are unnamed, right, so you haven't named them as an element, your data starts to look like on the bottom right. Right? So if you were to perform an analysis and that's what you're served up, this is the the top clicked elements. I might be like, what am I even looking at? I don't know what this is. But if you name them, then you can see the more readable names on the top left. So it doesn't just come in handy when you're using it to for, you know, speed speed to choose the analysis you wanna perform. It's also super helpful because it pops up in a number of places. Right? We saw it on on heat maps on the right hand side. We we haven't seen it, but it comes into play with journeys and and session replays. And, it just makes it really difficult to paint a clear picture of what's happening when you have unnamed elements. So that's really where the power of naming elements comes in. It makes your analysis more repeatable and scalable. Now I showed you data recommendations. You can use data recommendations, to also find a a starting point. If I head there, so you can see it for digital experience and then also for ecommerce companies like an add to cart button, a checkout button. So, you know, I'm gonna walk you through an example of how to in Data Studio, name our checkout button. So first, let me show you where it is on our site because knowing where it exists on your site is important because that's how you're going to use Data Studio to find it. So if I go to my car rental site, and I click on one of these cars, I am brought to the the product page. Right? And, the checkout button that I want to name is on the product page. So that's where I'm gonna look. So let's keep that in our minds for a sec. Go back to our settings and let's go straight to this elements, Data Studio. And that's where I'm going to click create element and go find it. So I could use the URL. Right? I very well could put in that that URL with the wildcard and find it there, but I already made it easy. I've already I already labeled it a page, so we might as well go find it on the product page. So, I page was because I can actually choose the button. So you can see, like, as I'm moving around, it's it's trying to figure out, like, which one do I wanna click on, which one do I want to name. And if I click the checkout button, it's gonna happen really fast, but look on the left. AI trim automatically happens. We just rolled this out last month, I think. It's called AI trim, and essentially what it does is it trims down the definition of that CSS selector. So it was this super long, CSS selector before, but it just trimmed it down to make it easier. And why does that matter? Because your code may change over time. And if you choose an extremely long definition for your selector, it's more easy to quote break. And what we want is we want high quality, less brittle, more semantic definitions for elements because that way it's gonna hold up over time so that my analysis will hold up over time. And I'm not having to go in here and redefine this every time my site changes. And that is the purpose of AI trim, because you don't need to know all the best practices, for, you know, which CSS selector to choose. So you can have confidence, that you select selected the right button with with AI trim because you can select this drop down here and see just like, we did with naming pages. You can see this element has been interacted with 1 and a half 1000 times across 1 page, which is what I'm expecting. I'm expecting it to only be on the product page. That's that's great. I could also click here and look at text. It's only the checkout. That's exactly what I wanna see. We'll go a little bit further. Right? You can click on element, and I can actually see this was already named, the checkout button. But if it wasn't, like, you would see the CSS selector here if it was and and yeah. So and another thing I can do is click this preview button for what it currently is and make sure that this is the right checkout button. So there's just there's so much to do in here to validate that this is, the right button that I'm or the right CSS selector, but I'm feeling really good about this. I wish for the demo, I had unnamed, you know, elements that I could show you but essentially you would, you know, name the checkout button here, click save. If you wanted to, assign it to a role in that data recommendations list, I would just find it here, click checkout button, hit save, boom it would automatically appear on that list. So that is how to find not we're going to get into watched elements in a second but this is elements that are, being interacted with. Okay, so that's that's how you would create that. I'm just gonna take a pause real quick and see if there's any questions about how I just used data studio to do that. Yes. So we've got quite a few questions. I have been sending, some responses, but we just got a question just as you asked from, Bohan about, CSS selector. So he says, what if the CSS selector is slightly different on mobile web view versus desktop? Will the AI be able to account for those to generalize to that button? Did did you know the answer to that? Great question. So, you what you can do is actually create, put the 2 different codes in there. So you can have it one name that that is, associated with 2 different CSS selectors. So if you're creating an element, you grab that selector and the same way we just did. And if you scroll down, I'm sorry, on in the left side panel underneath create element. Mhmm. We can actually add a selector. You see, like, underneath where it says platform, you can add a selector and specify whether it's web or on your mobile app. So you can have the same button. It's the same name. Right? It's gonna register as the same same click or the same interaction because it's gonna have that name, but it's actually gonna be different selectors. So, great question, Bohan. Thank you. And am I right that you would you would find the selector by clicking device type to narrow down here too? Oh, absolutely. Yeah. If you if you don't have it already, feel free to throw in the u the the URL, the page, or the screen to find it. Thanks, Yeah. Of course. Okay. So let's let's go through a use case to show you. Right now, you know how to name elements. Let's see where elements come into play. I think a good example I wanna show you is, creating a funnel. So if I were to go and click create and click create, a new funnel so if you're not familiar, a a funnel is essentially tracking, behavior that's performed in a particular order. I think conversion is really the name of the game here in identifying how many of my users are converting or completing all of these steps in this order. So because funnels often require many steps, it's 2 at minimum, but it's helpful to use elements here because I wanna track, let's say I wanna do visited page is I wanna start with the home page. And let's say the next thing I wanna see is that they're visiting that that product page. And then my final, let's say success criteria is that they are clicking element and it is the checkout button. Remember I was telling you that if you once you define elements and you assign them to the data recommendations, they appear at the top. This is what I mean. You're gonna have this list. It's gonna appear under digital experience or ecommerce. So I don't have to keep scrolling or search for it. It's just gonna, like, serve you up the the data recommendation assigned roles. So I'll click the checkout button here, and you can see this is so much easier than having to go through, right, visited URL, CSS selector, go find the CSS selector, copy it and paste it. It just makes it a lot easier for for anybody to perform these tasks. So if I were to scroll down, I would see, you know, the the number of people that are going from step to step over time. I'm gonna move on to when I move on to the next example, I'm gonna bring this back, and we're actually gonna use this to a b test something. But let me just save it right now. I think this is a good time, to pause and see if there's any questions about elements when it comes to defining them in data studio or, you know, using them for analysis like interacting with them. Let's just save this real quick. No questions yet. I think we're good. K. And anytime you save a a data, analysis and or product analytics at full story, We did roll out a feature recently. If you haven't seen that, you can actually make them private. So if you don't want folks to see similar to when you open up a Google doc and you're just figuring things out, you can make it private so it only appears to you. I'm just gonna go ahead and make this public and then save it so that, you know, D'Janae or other people on my team can access it. Okay. Any more questions? Are we feeling good? Yeah. We did get a question, about elements, but I think I'm gonna just answer that one in the chat because I don't wanna derail you. Okay. Okay. Yep. Alright. Let's let's tack on to the knowledge of elements here, and talk about what a watched element is. So, basically, a watched element is something that your user is just seeing. And so this can be like an error message or a promo pop up. So it's it's something that they're seeing, in their viewport, but it's not something that they're necessarily clicking on. So let's say I'm curious if a is seeing like a promo pop up or promo code on our car rental site. And I I'm going to show you how to create it as a watched element because I wanna know how seeing that promo code is influencing this funnel, this conversion. So that's a great use case. Let's jump into the car rental site so you can see. I'm gonna go back to the home page. This is our our promo window that pops up. As you can imagine, it might be a little bit more difficult to find this than an element because you can see the URL at the top. It's the home page. So if I were to go to the homepage, I might click get a new image a bunch of times until I'm able to see it pop up for somebody's experience. I think the best case, the best way to find these in my opinion is by looking at text that's in this promo code. And, you know, one thing, I will say is that I don't think there there are other pop ups that happen on our site. Let's try to search for text using this close. So let me show you what I mean. Let's jump back to our settings and go back into elements. That's where you're going to create watched elements. Click create element and I'm actually just going to search for text here and I'm going to search for that close that I saw. So let's see what happens. So I don't need to enter a URL here. I can if I wanted to further refine this, but it popped up. So I think somebody was asking this quest question. Yep. You absolutely can use Data Studio to to find watch elements and check out how easy this is. I'm just gonna go ahead and wait till the blue box. It's kinda hard to see, but it's it's highlighting over my entire, promo code window. I'm gonna click it. AI trim is gonna get to work, make this super easy. If you're smarter than the AI, which I don't know that I am, but if you feel like you wanted to play around with the definitions, you could also click here to unselect and reselect, and you could see here by actually removing that div, it it doesn't, impact the the volume. So because I wanna make this as short as possible, I feel pretty good about this. I can see here the promo code's only appearing on my home page, which I know to be true. And let's see the text that it pulls in. I think it's gonna pull all the text, from here. Yeah. It's gonna pull all the text that's that's on that. So I could have actually searched for, you know, this Fireworks 30 and that would have pulled it in too. So I'm feeling really good that this is the right selector so that I can go ahead and name this, this element. But there's one more thing I'm gonna do to make this a watched element and that is this capture options drop down because I want to select that it is a watch, I'm going to watch this. So I'm going to click watch this element. And that's the difference between creating an element that you can look at click analysis for versus watching. Thanks for the shout out, Jenny. Okay. I am now I predefined everything, so this is not very fun. But just imagine a world where I named this the promo modal and I clicked save. And before I forget to tell you you all this, I don't wanna excite you too much, but when you create, when you name pages, you name elements, it's not retroactive. So you can always look at your your analysis for URLs, etcetera. But when you name something, it's not retroactive. Meaning, if I were to go, show you what I'm gonna show you, which is this this watch element and how it applies to the, the the funnel. If you do this today, you're gonna see, like, 0, right, or whatever today's volume was until it starts tracking it. So but if you do it today, it's it's better to do it now versus later because you just wait a few weeks and that data is gonna start coming in and, you're gonna be able to start start using the definitions that you created. But I just wanted you to know if you you if you do this today, you may not see volume today, and that's that's why it's not retroactive. And happy to answer any more questions on that. But now that we've named this, promo, let's go back and hang with me for a sec because whenever I create AB tests, I think segments because I wanna create 2 segments. I wanna create a segment for folks that did see the promo model and then a segment for folks that did not see the promo model. And then I wanna, like, compare those 2 on this funnel. So let's go ahead and click create. I'm gonna create a segment, and let's do the event filters. Now instead of clicked, I'm gonna choose watched element and then element and see. I think I named it. Yeah. Promo promo modal. So this is anybody, that has watched the promo modal in the last 30 days. Let's save this. Promo model, yours. I always put my initials in here, and let's save and make it public and then save. Now watch how easy this is because I'm just going to do the inverse of this and I'm going to drag. I'm going to drag this event filter down to the exclude section. So now this is the inverse. Right? This is all the people that did not watch this element. Now let's go ahead and save as promo mode. Let's just this is, like, very uncreative, but they're non viewers and make it public and save. Okay. I've got my 2 segments. Let's go let's go back to the library to go find my funnel, and there it is. Okay. Check this out. So I'm gonna scroll down to the analysis, and this compare users area. I'll click here and uncheck the everyone. That's what it defaults to, but I wanna find these promo people. Do this, do this, hit apply, and boom. Now this visual may not be like oh, wait. Hold on a sec. This doesn't look right. No. Wait. I wanna see sorry. I I created this before this demo. I wanna see promo modal non viewers and there we go. Okay. These are now different segments. Okay. So you can see that, this volume, like, this number may not be helpful. I think I wanna see percentages for each step. So let's click this expand button here. The users that completed all three steps of the funnel when they did not see the promo is 27%. Folks that did see the promo model were more likely to complete the checkout funnel and they're at 34%. So this is a great way to validate, you know, what's happening with certain pop ups, whether it's like error codes, whether it's a promo model, You can create different segments and AB test them and immediately start to understand what is happening and get this, like, why behind what is happening. I think when we we talk about why, we talk about session replay a lot, but I didn't show session replay a single time today. And you can start to see, you know, the why in terms of numbers by using some of these, you know, naming elements, watched elements. There's a lot of power behind this. Any questions on elements or watched elements? Yes. Actually, we do have a question from Deborah. I'm gonna read it out loud. This is this, maybe a basic question, but when it says watched, does that verbiage mean that the user watched it but did not interact with it? Or does it mean that our team is watching this element? Which I love this question. Yeah. Great question. It means that for the user, it appeared in their viewport. So, like, for example, if it appeared at the bottom of the site and they went to that link and they didn't scroll down to see it, it doesn't count as watched. But the minute they scroll to it, as long as it's in their window essentially, no matter how big their window is like, right now, when I scroll down, boom, this dead click is now in my view part view port. If we were tracking this as a watched element, it would track that as a as a watch, and that would be like count 1. Yes. I also love it because kind of both are true because we are watching the like, we are this is something that we've named and said that we wanna know when this happens, when it when this is rendered on the viewport. And, typically, you wouldn't use it for that dead click because that's something that's probably going to be there. But, you'll most likely wanna use that for, a a form validation error or some kind of error on your screen, something that might indicate frustration, something was missed, something went wrong in their experience. And so you'll wanna track that because even though they don't click on it or interact with it, it might indicate, you know, an opportunity for, improving the experience in some way. That that was just a great question. Yeah. Thank you. We're watching what? We're watching Yes. We're watching. They're seeing it. I'll throw a link in here too. I think that's that's it for, watched elements unless more questions come. Yep. I did wanna show you I think I told you that I was gonna show you, how to create a a list. If if you wanna go further than what's on data recommendations, you can find out what is your top, your top undefined pages and your top undefined, top clicked elements. So let me show you how to do that real quick. And then I'm curious. Do you folks want to see me, show you how to define events too? That is gonna be pretty quick and you you don't have to use Data Studio for it, but you can. But if anybody's curious about that, maybe I'll just put like I don't have a poll, but does anyone want to see defined events in the chat? And just, like, throw an emoji in there, if you're curious. And if we get a few, I'll show you at the end. But, okay. I'm gonna show you how to create a list of, first, your undefined pages, your top undefined pages. So you're gonna click there's a lot of clicks here. So just maybe just watch and you can see the recording on how to do this, but, you click create a metric. Oops. Didn't save that funnel. That's okay. Click create metric. I'm gonna click, let's do events, and I'm gonna do visited page is. And if you actually Wait. Cannot define yeah. Chrissy, can I can I ask you to do a favor? Yeah. There was actually a question that was on this, that came in. And I answered it, but I think it'd be good to show it. So the question, was actually hold on. So if basically, the question was, if you have the same, CSS selector, but they're on different pages and so you wanna track it separately, how can you do that? So the best answer, the first answer is to have like, you have your click event as your main event, and then you refine that criteria right with the with the page. So if you're building a metric where you're saying, I wanna know the number of clicks on this element when the page is by adding that refined that dependent criteria, you can do that. But I also mentioned in my response that if it was really that important to you, you could actually create a defined event based on that. So where it's a click, right, where and but the refined criteria is on a specific page. So maybe it'll be helpful to show. Yeah. Let's do that. It looks like there's a lot of interest. I'll change gears. I'll come back to this list in a second, but let's do that. So, this is how you do it. Clicked. Let's say that we want that clicked element is checkout. I know it only, it pops up on one page, but let's say it popped up on on 2. You know, you could do a clicked element or you could even do click text is checkout. You just type in checkout, and then you could do refine event by. And then, page is product page. This is what DJ and A was saying that when the criteria. And what I could do is just click these three dots here and click define event. Boom. And it takes me into data studio. I can go ahead and name this, and then if I wanted to find it again let's see. Now the way I put you wow. That was cool. I didn't even know it did that. But, when you go to find it again, you would just go to custom event and then, you know, what you named it. Here we go. And I think it defines it on the right here for you too. So if you're not sure what the defined amount was, it just quickly gives you a definition. That's it. That was perfect. Thank you, Chrissy. Yeah. And you can add I will say for defined event, defining events, you can use an or feature too. So, like, let's say I wanted to track, like, rage clicked anything. I could do this or event here, if I wanted to do, like, rage click error clicked anything or dead clicked anything. I could save this whole thing as an event too, like an Uber rage event. And now I could use that so that I don't have to, like, do the or or every single time. If I wanted to see, you know, this Uber rage event, pretty quickly, I could just go ahead and then I think we may even have it saved to custom event, and then you just find it, Uber rage event. Boom. So, yeah, it's great if you're using refined by criteria or the or, statements so that you don't have to do it each time. Okay. Let's do, how to create a list for undefined pages. So if you do visited page is not defined, everybody should be able to to run this. And you scroll down and you click on dimensionality here, this bar chart. This is you need to group by. So if you group by page oh, no. Not page. Sorry. URL. You can see all of the URLs, in order of most clicked that are not defined. Did I do that right, or would you do this URL path? Either one, honestly. But, yes, it's exactly that. Yeah. Okay. That's how you find your your top, undefined pages, and you can scroll through the list here. You can also export it as a CSV. Highly recommend doing that. And then basically just, like, using that as a checklist and deciding which ones you wanna define. You would just grab the URL, go define it in Data Studio, and immediately, you know, be able to start gaining insights. To do the elements is a little bit different, but you're gonna do it in a metric, and it's gonna be, let's see, clicked anything. I'm gonna say, you're gonna scroll down and I'll type in CSS, and then there we go. These are my top top clicked elements or CSS selectors. And you can see I have it named all of them. If you're not sure what this is, you could just hover over this, go watch a session with that CSS selector in it, or you could copy that CSS selector. Oops. Pause this. You could copy that CSS selector, go put it into data studio, and it'll also show you what it is. But that happened really fast. But if I do events matching your search It's that click. Was it this one? Yeah. No. The one that's pink. The one that says daily input. It is this. Okay. Okay. I thought it was named but it's unnamed. Okay. There it is. Okay. I wanna make sure we've got through a a fair amount of questions, so keep them coming. I wanna answer them all, but let's just, like, wrap this up real quick, and that is, like, what to do next. So feel free to go to data go to data recommendations or create a list like I just showed you how to do with a metric and start, naming your pages and your elements. You can start defining your events too. And then, you can always learn more through our help center, full story learn, and we also offer group office hours 3 times a week. If you go to our, event hub, D'Janae, if you could drop the link there, that'd be awesome. That's where you can sign up for those group office hours and Dijanae or myself will likely be there to answer any questions that you have. You could also reach out to our support team by emailing them, support at full story dot com, and they can help you with, if you have specific, you know, specific examples on your site you need help with. That's it for me. I am gonna launch a survey. For folks that do wanna drop, Please, feel free to take a second to fill out the survey. It helps us advocate for, you know, future programs like this, but also would love to know how to make this better in the future, whether you loved it or you have constructive feedback. But I will launch that now. Feel free to fill it out now, or you can hang out for 4 minutes, and we'll answer any more questions that we have. But thank you so much for attending. This was a great turnout, and I really appreciate everybody's, questions that you had today. Yes. Did you did you launch the survey? I did. I did. Oh, thank you. Thanks for doing that. Of course. No more questions. There haven't been questions in the last, 13 minutes or so. So, thanks so much for everyone for joining for all the great questions. There will be some resources that Chrissy is gonna put in your follow-up, with everything that you need to know to get started with, data management and recommendations. But excellent questions. But if there's more, we're sticking around for the next 4 minutes. We will be here. We're not going anywhere. Yeah. We're gonna watch you watch us. We're we're the watched elements now. You are the watched. I love that. It was inception with the watch television. That was so cool. Excellent questions, everybody. Thanks again. Crawford, any other exciting product updates coming soon that you all can talk about? I don't know. Can we? Hi, Crawford. Not that we we are sworn to secrecy. Nothing Crawford is an old friend. Yeah. Nothing that we can that comes, like, top of mind that we can talk about. But when we do, we have some fun stuff that's rolling out very soon. So we might have, you know, more of these kinds of sessions where we will be talking about things that are on the horizon. So stay tuned because it's coming. Yeah. I will say that there was something rolled out that we didn't talk about that was rolled out Oh, yeah. Weeks ago, but it is very relevant to what we were talking about. There's been a lot of time spent on, you know, the the data the data management area, which is great to see, especially for nontechnical people like myself, but, it's extracted properties. There is a help center article on that. We didn't quite have the time to get to it today, but that is a pretty exciting thing if you're interested in Yes. Data management to delve into. Sending that right over. Yeah. This is pretty cool, actually. Pretty cool use case for extracted properties. So, yes, definitely come a long way. Yeah. We're we're working on some pretty cool stuff. So love the excitement. I just threw that link in there. And again, for anyone who's still on the call, thank you so much for your feedback. These surveys really help us out a lot. And if you have questions, burning questions that you wanna get to, ask us, we are in group office hours several times a week. So use that link again. I'm gonna pin that to the top for, group office hours where you can, interface with us, ask questions if you need to. Have a great week. Amazing job, Chrissy. Thank you. Alright. Bye, everybody. Thanks so much again. Appreciate it, and hope you have a good day.