PurePerformance - 059 A Deep Dive into Visual Replay: How it works and Why the World needs it!

Episode Date: April 9, 2018

Visual Replay gives you full film-like replay of your end users, including clicks, mouse moves swipes and scrolls. It helps you optimize user experience by addressing problems where end users struggle, e.g: not finding that button, an overlay dialog hiding critical elements or a 3rd party browser plugin that messes with your page. It also supports compliance use cases such as allowing you to proof what information you really showed to the end user when they conducted online business with you.To learn more about this use cases and the technical implementation details of visual replay technology we invited Simon Scheurer, Chief Software Architect at Dynatrace (https://www.linkedin.com/in/simonscheurer/), to this podcast. He educates us on the latest of this disruptive technology!And besides that we also learn about how awesome Simon’s hometown Barcelona, Spain is.

It's time for Pure Performance. Get your stopwatches ready. It's time for Pure Performance with Andy Grabner and Brian Wilson. Hello, hello, everybody. Welcome to another episode of Pure Performance. I'm Brian Wilson and on the line with me is Andy Grabner. I was going to say on the phone, Andy. I guess technically it's still kind of phone-ish, but not really. How are you doing today, Andy? I'm good. I'm good. Thanks. Still sitting in Boston here and I guess you don't want me to talk about the weather because I tried this in our first attempt to record and you said nobody's interested in talking about the weather. So we skipped that part. Let's talk about government instead. People love talking about weather, government and religion, right? So let's do that. So today, the episode today was triggered by an amazing amount of positive feedback that we have all received at Perform.

When I think he picked a little bit of a Swiss-Spanish-English accent on stage. So our own Simon, he went on stage at Perform at our conference end of January in Vegas. And he put a lot of energy. I think he's just a very energetic person. And I also witnessed this later on at the end of the show at the dance floor, which was fantastic. But on stage, Simon was the one who presented visual replay. And visual replay was something that I believe we can all agree for those that have seen it on the live stream or that read about it on the blogs, in the news announcements.

It's a very fantastic, it's an amazing, cool, new feature set that we're bringing in, opening up a lot of new use cases. Now, what are these use cases? And to discuss this, we actually brought Simon in and now I actually want to hear this spanish swiss german english accent so simon are you there i'm there hi andy hi brian actually i just wanted to say i would not want to add too much spanish or swiss german accent today so i'll try to to do it properly but yeah great to be here with you guys so so simon when and andy i guess I don't remember, on the dance floor, was that when I was doing my special brand of dancing or did Simon and I not cross paths?

I can't recall. I'm not sure if you've been on the dance floor at the same time, but I remember we had fun on the dance floor. I just don't know. I guess now that I don't have all the scotch in me, I'd be a little bit embarrassed if Simon saw me dancing, but it's out there for it to be. I just kind of let loose, Simon that I don't have all the scotch in me, I'd be a little bit embarrassed if Simon saw me dancing. But, you know, it's out there for it to be. I just kind of let loose, Simon.

I don't have any dancing, proper dancing skills. Hey, Simon, can you give us a little background about yourself, who you are, kind of what your role is within Dynatrace? And then let's dig into the topic. Yeah, sure. So I'm Simon. I'm, well, kind of this type of guy that you would probably call a serial entrepreneur. I had quite some companies that I funded and was building up. The last one was actually a session replay company. And then we got in touch with Dynatrace,

which ultimately led to us being bought by Dynatrace. And that brought me now into this new role that I have within Dynatrace, to being responsible for the Barcelona lab and building this up and bringing this technology to Dynatrace and also extending it then into user experience analytics and trying to push this entire user experience topic forward within the company and towards the customers. That's pretty cool. So now you said a serial entrepreneur

and the company you founded that we acquired was called Qamram. And can you fill us in, I know Visual Replay is something, if you just say the name Visual Replay, a lot of people have maybe different things in mind. So can you tell us what are the main use cases that you guys identified to actually start a startup

back in the days? Well, our original use cases, when we started it, was actually mostly to be able to prove what is going on. So when we got into the market, we had a lot of requirements from customers that wanted us to prove what their customers are doing in case of e-commerce, in case of e-banking applications and these are likes. But what then happened as soon as we started to develop this technology and as soon as

they've seen about how great experience is, how movie-like it is, what you can actually see and how much you can discover by literally looking over the shoulders of people, we got more and more into the area of user experience. So what we do now and what is the ultimate use case if we want for session replay is for us, it's kind of the utmost level of drill down that you can think of. So there is so much available in the market. There are so many analytics tools that tell you what customer segments are not successful or do not reach their goals. There are tools, well, you know, Dynatrace that tells you if

their error occurs, the performance is bad. There are customer complaints and all these kind of things. And you don't really understand what's going on. And in all that cases, session replay would just give you much more context because you can just see what is going on. And this is why session replay is really a successful addition to so many other products because you have the final view about what a customer was doing and you perfectly understand what has been going on. And I think if people want to actually see visual replay for themselves, I believe on the website, if you go to dynatrace.com and search for visual replay, there's a page, also a video.

Because you keep telling about this video. It's like you can actually replay visually what a user, an individual user, really did on their website, including, and correct me if I'm wrong, but including moving the mouse around, swiping, scrolling, pulling drop boxes down, doing things and interacting with the website. And I remember when you were on stage, and maybe you have to remind me now of the name of the user that you were actually analyzing. It was a lady. What was the name again? Ashley.

Ashley McCall. Ashley. Ashley McCall. Ashley, exactly. So you basically showed us Ashley, and she was trying to purchase something on an e-commerce site, and she tried multiple times to fill out these forms, but when dropping down a box or something, I think there was like an endless progress bar coming up or something failed. And obviously, with all the other tools that he mentioned earlier, even with

Dynatrace itself, without Dynatrace RAM, we would basically tell you which clicks Ashley would have done. But we would not be able to visually tell you what her experience was, like there was this particular weight symbol or this weight progress bar or visual error box on the screen that kept her from actually continuing her conversion journey. And I think this was really fantastic. Now, when we talk about visual replay, and I think we had this discussion before we started, you actually see what looks like a real movie. Now, can you go a little bit deeper before we explain other use cases? Can you go a little bit deeper technically? What are you actually capturing?

Are you actually capturing video screens and frames on the user's device? Or how does this work? No, we don't capture actual videos. That's also why I mostly talk about movie-like experience because it just really looks like a movie. So the quality is like watching a movie, but it is not. Technically spoken, if you're looking at a browser application, then everything that you visually see has its internal representation in the browser that we call the DOM, the document object model. And every time something changes visually on the screen, there is a change also in this document object model.

And what we do is we are kind of monitoring this document object model. And every time that a change happens, we see that. We capture the difference in between the former state and the current state. And this difference is what we actually store and save. And then in replay, we just do it the other way around. So we take the initial state and we reapply all these changes. And with that, we are able to recreate this entire visual experience the exact same way that the user has seen it. But it's still, of course, textual data. So we are not, you know, filling storage with movie files. And the other question that somebody

asked me once, and I know the answer to this, but I just wanted to put this out there because I think other people might have the same question,. Somebody asked, well, if somebody is filling out a form and they click submit, let's say, is the replay submitting that data of theirs again to the system? And, you know, my understanding is absolutely not. We're just recreating what it would look like. But I guess their concern was, you know, if the replay is going to log somebody in, is it actually going to log them into their account on the replay session? Yeah, no, absolutely not. So we're kind of a sandbox.

It's exactly as you say. We're just recreating the visual experience. It's not a simulation. It's a reproduction, which is also differentiated towards other tools that actually do, as you say, they try to reapply the events to make the application behave the same way and hope that this will recreate the kind of same experience, but typically it does not. But that's not what we do. It's really sandboxed. It's just a reproduction of what the user has seen without, let's say, an actual interaction with the original backend. And another thing that this makes me think of, when you guys were describing some of this earlier, and I think this applies to the use cases we're going to go through.

So I wanted to kind of put this in people's minds first, is with the idea of a replay. When you think about when there's a code problem on the backend, let's say there's an exception, right, Andy? What do the developers do? They look at the exception, they try to understand what caused it. Oftentimes then they'll pull up the code in their desktop or in their IDE

and they'll step through the code trying to recreate it and see exactly how they're going, how the code executions and the step through that triggers the error because they want to experience it. They want to see it when, now, if we take that idea and put it to front end web development, you know, the idea of stepping through the code from, you can only, if you have a JavaScript error, like we saw in the example that Simon showed at Perform, you see there is a JavaScript

error, but you don't really know what that means. And it's not like you can step through code in quite the same way. There is some ability to step through code right in your browser tools, but you're not going to be seeing it. So to me, I'm thinking replay of a way to visually step through the code execution so that when you do have that JavaScript error, you can step through the replay cases to the point where that occurs and actually see it visually and experience what that is. And I think it's just a different way of looking at it.

And I'm really excited about it. I just can't say enough about it. And I think, I mean, I've not developed that many web pages in my life, but I totally agree with what you just said, because if I get a JavaScript error and I cannot reproduce it on my machine, it may just mean I didn't move the mouse over a certain DOM element that it was triggering some other JavaScript that is then changing the state. And with Visual Replay, you guys are capturing all of these interactions with the DOM that actually change the state of the DOM and potentially execute JavaScript code that leads to problems. And that's what I find so fascinating

about this technology. And also the seamlessness and the easiness of enabling it. So Simon, can you quickly tell us, because I'm sure customers or anybody out there is wondering, how would you enable a technology like Visual Replay? How does this work? Do you have to install a browser plugin? Do you have to do some magic? How does this work? Well, it depends a little bit on the case, but the easiest case to make it work is if you already have, for example,

Dynatrace running and you already have a JavaScript agent that is happening to reside within your browser, then ultimately it's just taking a configuration that will work. What we do is injecting a JavaScript into the actual application. And this can, of course, happen by different means. It can happen with a tag manager like Telium, or it can happen if you have one agent installed, it will just happen through the one agent so you don't have to do anything

or change anything on your application. We just do that on the fly. And the only thing you have to do is basically, well, take a configuration box and you're done. That's pretty cool. So everything that you guys are capturing is really done through JavaScript that cool so everything that you guys are capturing is really done through javascript that gets injected on that page there's no native browser extension

that anybody needs it's just purely done through javascript and that's very powerful yes exactly the only the only situation where you would need a browser extension is if you actually want to record an application that you don't control. So say you want to record what your sales people do on Salesforce or what your services people do on a ServiceNow application. So if it's really a SaaS application that you want to monitor with Session Replay, we can do even that. In that case, though, you would need a browser extension because there's no way that you can actually get into the application as you don't control it yourself but in all other

cases you definitely don't need anything in the browser it all just happens magically that's cool and i think brian you also before we started you talked about uh that you are currently exploring uh this type of capability what we we call Dynatrace SaaS vendor RAM. Actually, mine's a little different. So we do, well, yeah, you can continue that thought, but my situation is a little bit different where it's the agentless RAM. So for anyone familiar with Dynatrace, there is the ability to basically inject the JavaScript tag and the file somewhere locally,

because the case in point is, let's say, Salesforce Commerce, which used to be demand where you don't have access to put agents somewhere, but you can still inject JavaScript and tags into your page. That's actually the case I'm looking into, Andy, but I believe the case you're talking about with the, what did you call it again? The browser extension? The SaaS vendor RAM. Right. That's more for like Salesforce proper where you can't even touch anything and you still have that browser extension that you can add in to collect the RAM data,

the real user monitoring data, which I guess, Simon, what you're saying is you'll be able to piggyback on top of that and add the replay tag to that as well? Yes, exactly. Yeah. So that's pretty cool. So that means to sum it up, we have the ability to enable visual replay for any app where you either install a Dynatrace 1 agent on the server side,

and that will automatically inject the RAM agent that we have, and then visual replay can be enabled. We can do it through, Brian, the the way you do it which is called agentless ram where you can inject a little javascript tag on let's say a page in case the vendor itself allows you to change these html templates and the third option is if you have no control at all about the rendering like salesforce office, whatever else you use, then you can use our SaaS vendor RAM browser plugin to inject the JavaScript agent and then monitor how your probably employees are using these services.

So that's pretty cool. Now, Simon, you started off with talking about the use cases. And I think you said, you know, kind of the user complaint resolution, figuring out what individual users are really doing. What else is out there? What else did you hear from people that have been exposed to visual replay? What are the other use cases that people like about it? Yeah, so as you mentioned, user complaint resolution is definitely one of the biggest ones where it's about single users. The other ones already have been mentioned by you, Andy, but also you, Brian.

It's really providing context because I maybe want to go back a little bit to this debug idea about JavaScript. Typically, yes, you have means on, for example, debugging in case of errors, but you typically can't do that on live systems. Because, I mean, you can do that in your browser while you're developing, but you're completely running blind. If something happens out there in the wild, some users are just getting into problems. And this is what we call the use case of providing context to anything that might happen. It could be a performance problem. It could be an error. But you can But typically, that's so hard to reproduce. So your developers just won't know what is going on. Why was this happening? How did it affect the user? What did he actually

perceive? Where can I fix it? What do I have to fix? And all these kind of questions you can simply then answer with a session replay. So this is the use case of providing context. And then there's one more, which is simply usability. So every time something pops up in your dashboard, so you see people are not converting, they're struggling, they're clicking like mad because this is this is stuff that you can easily let's say find out analytically you know you see these people you see these segments but you never know the why and the why is what we add the why is um that that's kind of the information that we can add to the picture to to explain why people were not able to fill a form. We've seen so many things like, you know, sometimes that you have an accessories list and it simply drops over the actual submit button in a checkout process.

So people were, well, given a lot of accessories to pick, but then finally could not conclude the actual transaction or buttons that look like buttons but are not. And people are just clicking there like mad. Nothing happens. And then they just clicking there like mad. Nothing happens. And then they're frustrated and drop off. All this information is super hard to get analytically, but it's so easy to just see. And so what we facilitate is just user experience improvement, which is another use case that we had very frequently and helping to even, let's say, on a processual level, which is then rather, let's say, if you want the use case for the organization itself,

to become more agile because with that immediate feedback, you're just so much faster in fixing issues. You're so much faster in improving your application. You're so much faster on, for example, the Navy test and getting feedback about which really work. And with that, it's way easier to get into iterative and agile processes and making your application much better in a much shorter cycle. Cool. Another topic that I remember from discussions at Perform was compliance.

And I obviously am not an expert in compliance. And I obviously, I'm not an expert in compliance, but I heard a lot of companies out there love a technology like visual replay for compliance reasons. So actually having the ability to kind of prove what individual users have done. Is this also, did I hear this correctly? Yes, certainly. So if we're also looking,

this is heavily industry dependent, if you want. If we're looking, for example, at financial industry or other heavily regulated industries, there's so much going on now. Also as a consequence, for example, of the financial crisis, that regulations have been tightening and you have to prove that you actually did give best advice. You have to prove that a customer, when he purchases something or he does a trade, that you have given the right conditions, that everything was visible, that you have shown the full price. And now we get into the situation that to prove that, well, you know, in the ages of

Internet 1.0, this was really easy because it was just page based and now we've single page applications getting data from very different systems putting it all together the only point where you actually see what has been going on truly and what the user has seen and what he was doing and whether he has confirmed the checkbox that he's supposed to check is on the client itself. And that's why it becomes more and more important to everything that's related to compliance to push it towards the actual end user experience and record this as ultimate proof what has been going on to show in case of litigation or towards the regulators.

So this is definitely a trend that we are also seeing that comes kind of in parallel to all these other use cases. In talking about compliance, that also brings up the, I was going to say 80-pound gorilla in the room, but it's 80-ton. I don't know. Whatever, the elephant in the room, right, which is privacy. So obviously on the one side you have compliance where you want to be able to prove the user did specific things that certain specific things were shown on the screen

but there's another big uh question that everyone has about these technologies which is the privacy am i capturing uh passwords are we seeing sensitive information about the users there was just recently an article in wired uh where they just this week I read it. It was about replay sessions, storing passwords. I think it was AutoTrack was the product and they were mistakenly capturing passwords and they weren't exposing them per se, but they were storing them within their data sets on their servers somewhere, right? So how does this tackle privacy and how do we stop the fear of people thinking, oh my gosh, this company is capturing and storing all this data about me and it's all private and anybody can see it? Well, we don't.

That's our hidden business case to actually sell this stuff to the NSA. We sell it to Facebook who sells it to the NSA, right? Exactly. Well, seriously, just let me answer this twofold. First thing is about privacy is, of course, a high concern. And there's no easy answer to that because you can, of course, record everything that is going on. But what we do in that case is that we, of course, also provide the possibilities to exclude stuff from being recorded to mask fields that should be there. Let's say personal identifying information,

passwords we don't record by default. You can exclude entire processes that should not be there. You can also decide on when to record. For example, if somebody actually does, let's assume he does an E-trade, then you have to record what he's doing. But if he's not doing such a trade, maybe you're not even allowed to do so. So we can very easily react on things that are happening within the session to decide on what to record and when to record. Our customers can configure on how this is supposed to work. So there are many things that you can do to actually protect privacy. So this is one part of the answer that in between not recording anything and recording

everything, there's, let's say, there's a big range in between. And depending on the use case and the regulations, we, of course, deal with that. And then there's also retention in that sense that depending on what data it is, you will not keep it for eternities. If it's for customer complaint resolution, you know, customers, if they have a problem, they typically don't call seven days later. They call tomorrow or today. So if it's just for that case, you'll just delete that data after two days.

But this is just one cluster. And there's another part to the answer where I always say, actually, we're the best thing that can happen for privacy. And that may sound a little bit strange, but you just have to be aware that what is going on today is that data is stored anyway in many, many different systems. And we've been talking about compliance. Now, think about all these backend systems that are recorded, all these logs that are recorded. If a user comes and asks you, show me what you have about me, how do you do that? You're not able to do so. If he's not your customer anymore and he asks you, can you please remove all the data that you have from myself? You won't be able to do so. If he's not your customer anymore and he asks you, can you please remove all the data that you have from myself? You won't be able to do so.

It's simply impossible because you just cannot tear that stuff apart. But if you switch and record what happens on the front end, we are user and session centric by nature. So it's a super transparent process. And transparency is one of the most important things for privacy, that you can actually, you know, we can show the user what we have about him, and we can delete it if needed. And we have a proper retention. And if it's gone, then the session data is gone. So this is kind of, you see, the entire cluster about privacy. And it's, as you say, it's probably not

the 80 kilo or the 80 ton, it's the 800 ton gorilla in the room. It's always one of the main questions, of course. But there is many things to the topics. And I think it's an illusion to believe that without session replay, the data is not retained anyway, but in a way that is way more complex to deal with. And I think just for anybody in the United States who's listening, you mentioned a lot about, I want you to remove the data that you have about me. This is all as a result of the GDPR rules, right? Which is a European rule about data storage, privacy, right? So Europe, everyone out there is so much more ahead of us in terms of privacy. And there's all these rules. So the nice thing to understand is this tool, this replay component was built in that environment where all this privacy and compliance has to exist.

So as opposed to, let's say, if it was built over here in the United States where we don't really necessarily think about those day to day, that's built into the tool from the ground up, I imagine, because you all knew this was coming. So there's no way you're going to be out of compliance with it. Cool. Hey, so I listened to this conversation and kept it a little quiet because I thought it was fascinating to learn more about privacy. Because as you said, Brian, it's nothing that is on our day-to-day radar. Now, one of the interesting things that you guys mentioned, it's important, especially for the compliance use case, to capture potentially every single user if we need to prove something. So what does this mean in terms of data volume? What does this mean in terms of scalability of this solution? Because obviously it's the thing that we've always claimed at Diamond Trace and we've always delivered on is the capability to monitor 100% of your end users and 100% of your transactions. Is this also possible with visual replay, assuming that there might be really a lot of data? Yeah, that's definitely what we provide is a 100% recording because, as you say, otherwise – also even for the user complaint resolution use case.

If then the user calls and you just do a sampling and you happen to not have the one that is actually calling in, then it's pretty hard to help them. And so we definitely thrive for a 100% recording and we're also able to do so. The good news about the approach that I just described with the DOM changes is that we work differentially. So we are just recording and capturing the changes that happen. And of course, also all the events like clicks and moves, but that's not expensive, let's say, expensive data or heavy data. And while we're sending that back, we also bulk it together such that we don't create an awful lot of requests on your network. And because it's text-based data, we can address it pretty well, which reduces, again, bandwidth,

which reduces, again, also the load and service, and of course, also the storage requirements. And let's say we've all these measures together. Yes, we're capable of recording 100%, and we will create a decent amount of storage, obviously, if you record millions and millions of sessions, but it's not that much that you would expect. Cool. Now, are there – I mean, you have a lot of data, and obviously there's this use case we talked about, but I'm sure with that amount of data and that granular data, there's a lot of cool maybe analytics use cases that you can additionally do. helping development teams to figure out why are people dropping out at certain points. And you mentioned the figuring out, hey, there might be, it looks like a button, but it's not a button and people clicking on it.

Is there something that can also be done, let's say, more proactively instead of doing the ad hoc analysis of a complaining user? Is this also possible with the data? Yes, it definitely is. And that's also what we want to do. We are not there right now, but that's the exact direction where we're heading. One paradigm that Dynatrace has always had is we do not just provide reports. We actually want to have recommendations. We want

to have actionable intelligence. So we won't tell people what they need to do to fix the problems they have. We don't just want to tell people what they need to do to fix the problems they have. We don't just want to tell them that they have one. And the exact same idea we also are going for when it comes to user experience analytics. So we have the data to not only tell that you have a conversion problem or actually it doesn't work or this form doesn't work, but we actually have the data to tell them what form field should they change, how to increase, let's say, conversion, to increase happiness of your user, to increase loyalty, to decrease churn, to decrease struggle. These are all the things that this data, it contains it all

because we literally have all the information about what users have been done and we also have it in structured form, but not just as a visual reproduction. Now, that's cool. I mean, this is, I mean, falls exactly into the line what we have been doing at Anitrace for a while, right? I mean, if you look at a RAM session right now, a user or a visit,

you can then see what are the top findings and how to optimize the page load. We also do the same thing now on the server side with top findings on the pure paths. So this falls perfect in the line because we cannot expect everyone out there to be an expert in analyzing all the data by hand. Nowhere can, not that we have the bandwidth, neither has the bandwidth. So let's use the machines to do the work for us and digging through the data, obviously optimized with

the analytics and the algorithms that you guys put in place. That's pretty cool. You know what I'm thinking, Andy? What are you thinking? Simon, I'm going to put you on the spot here. I hope you don't mind. It's probably, the answer is probably no, but this always comes back to going back to my old, you know old load testing days.

I'm wondering if there would be a way to somehow bulk export the sessions and turn those actions into some sort of playable script. Not necessarily for that user with that user data but you know one of the one of the pain points in modeling any kind of workload in a load test is putting together those scripts trying to figure out a realistic workload i'm just musing aloud whether or not any of that information in there would be something that could be manipulated and converted into some sort of a script i don't know i'll have to take a look at i guess once we start seeing what it outputs. But that's how we see it. Maybe to not put Simon on the spot, but to interject myself here in this discussion,

we actually have already load testing partners and testing partners of Dynatrace working on that. Really? Leveraging the RAM API, so working with the Lint's team, but I'm sure they will also soon reach out to you, Simon, to see what additional they can benefit from your data. But yeah, there's just been, you know, we have every single user and everything

click, yeah? They already have, so it's interesting that you mention it, because it's a use case that even in the old Qumran times, we already were, let's say, confronted with it, and of course, yes, we have so and it's interesting that you mention it because it's a use case that even in the old kumram times we already were let's say confronted with it and of course yes we have all the data that you could do selenium based or whatever tests um to then run it in a synthetic environment again record what is happening and yeah that's definitely something that we'll add some of the data that we have to to enable this functionality as well. Awesome. Cool.

All right. So Simon or Brian, any other thoughts? Anything else that we missed that we need to make sure that the people out there understand about visual replay? I've got nothing on my end. Simon, is there anything you have the mic now? Is there anything you would like to get out there, if it's just what you're gonna do this weekend or some boring stuff about barcelona weather which is actually pretty bad there's nothing

boring about barcelona are you kidding me i love love Barcelona. Yeah, it's a fantastic location. Well, not really. I think the only thing maybe as a last comment is that many times when I talk to people, they often try to solve problems by adding more and more logs and adding more and more information. And we often forget, as humans, how powerful analytical engines our eyes are. If we look at things, we immediately spot patterns, stuff that happens. It's so easy to use.

And so just if you're dealing with problems, if you're dealing with usability issues, if you're dealing with, well, whatever situation where you think, oh, it would be great to have a bit more information, just don't forget about session replay and add it to the stack and you'll be amazed how much you can do with it. Right. Cool.

Brian, is it time that I summarize? It's time for you to summon the summonerator. Let's do it. Perfect. All right. So Simon, this is what we do at the end of the show. I always try to sound smart by summarizing. So I think what I've learned, first of all, Simon, this is what we do at the end of the show. I always try to sound smart by summarizing the lesson learned. So I think what I've learned, first of all, Simon, not only are you very energetic on stage and also very energetic on the dance floor, but you also obviously love the technology that you have been helping to drive forward over the last couple of years.

Thanks for the insights on visual replay and session replay, as we call it. I learned about that it's actually not a video we record on the device. It's really technically the differences in the DOM as a user navigates and interacts with the site, which keeps obviously the volume down on data we need to collect, but still gives us all the context that we need. Now, there's a lot of great use cases, whether it's the classical user complaint resolution, helping our business people, our business analysts,

our developers to figure out where people are struggling with their websites. A big use case is obviously compliance. We should not be fearing any data compliance or privacy issues because the product has been built, manufactured, and optimized in Europe where we get these new regulations. So privacy concerns have been addressed right from the start. And there's a lot of cool things. Additionally, we will be able to do and we will see like automated recommendations. So not everybody has to be an expert in analyzing all the data, but Dynatrace will automatically provide recommendations on how to improve the user experience, how to improve conversion rates and your user experience overall. So thanks a lot, Simon.

I know that there is an early access program going on. I think by the time that this podcast airs, we may even get close to the beta phase. But in any case, people can go to the Dynatrix website, search for Visual Replay, and right now, but I'm sure it will be at the end of May when we are going to host our European Perform Conference. So for anyone who wants to see Simon in action, who wants to see visual replay and learn anything about Dynatrace, check out perform.dynatrace.com and then click on the European perform link and you can join us there for, I think it's two days or so of perform conference, including a training day. And yeah, that's all from my side. Pretty cool. Thank you so much. And thank you, Andy. Once again, you did an awesome job summarizing. I don't have any more from a technical point of view to add there, except that I'm just waiting to get my hands on it. And I want to say to Simon and anybody else who's heading over or in Barcelona, I would highly recommend going to, I'm going to mess up the name here, La Anxo Veta Restaurant.

It's a Catalonian, so I'm probably pronouncing it wrong it's a-n-x-o-v-e-t-a uh it's a small little restaurant on uh carrera de saint dominic and um i can't pronounce these things very well anyway it's awesome it's this guy who used to forget what he used to do uh and he we did one of those food tours of catalana it was just awesome because it was these really great places they got great bombas uh they have a great tomato bread uh the food is wonderful the wine is wonderful uh it's a small little place but get over there if you can i don't know if you've been there simon i think it's in the gracia neighborhood um it's just quite quite good that's what that's what my summarizing will be since we're talking

about barcelona um and replay it's awesome i can't wait to get my hands on it uh i know this isn't the first replay tool out there um but knowing what we've been seeing coming out of you guys and knowing how we do things here at dynatrace, I think it's going to be quite amazing. And the fact that it's going to be natively tied into everything else that we do is just going to make that replay experience so much better than just having a replay on its own. So I hope everyone's looking forward to it as much as I am. And we'll have some reports soon. Thank you, Simon.

Any last words from you? Well, if you're looking for a restaurant in Barcelona, you can also just call me. I'll be happy to help out. Yeah, thanks for having me. It was a pleasure talking to you, guys. Thank you.