Skill Exchange Event Sept 2022 Analytics Grow Making Adobe Analytics Your Own

Transcript

Thank you for that introduction.

My name is Jason Egan. I’m a senior analytics engineer at Search Discovery and I’m happy to present to you today how to make Adobe Analytics your own. Let’s start off by telling you a little bit about myself first. I’ve been in the consulting and analytics industry now on both the practitioner and consulting side for about 20 years. The last 10 of that have been with Search Discovery, where I’m at now, which is an Adobe Analytics partner. During that time, I have performed hundreds of analytics implementations for many different verticals. A little bit more about myself personally, I am from Knoxville, Tennessee, where I’ve lived for the last 15 years or so.

Go Vols. I, on a personal note, am into weightlifting, D&D, and Warhammer. So on the topic of making Adobe Analytics your own, we’re gonna be looking at the features and strategies that you can use to create a great experience for your users. Typically, you have an Adobe Analytics implementation. It’s very complex, but you have it. Now what? We’re gonna work on making it your own by taking advantage of the features and strategies unique to your business users. This is gonna include several things, including curated workspaces, so that you can create a curated experience for your users, notes and annotations, which will provide some context and date-sensitive information that will be useful to your users. We’re gonna talk about reporting governance, and there we’re going to cover the sharing and creation of reporting values, classifications, and some other best practices. And finally, we’ll wrap up by talking about virtual report suites, which can be used to provide only the data that your customers or users need. So let’s look at this in terms of analytics challenges that may be present for your users. First off, there’s implementation complexity. You may have many builds as a part of your implementation, daily or monthly, that can change things. You may have dozens or even a thousand events, variables, props, and the different confusing attribution methodologies and expiration points for these different variables and values. One of my favorites is also the concept of one question, many answers. Here we see someone looking for information on marketing channel reporting. There are seven or eight different possible values here of different nature that could result in your users trying to understand marketing. Everyone tries to create the same analysis, but comes up with a different answer. Next, there are different and confusing reporting values. Sometimes they may mean something, sometimes they may not to your users directly and immediately. So we’re gonna talk about governance and better management of these reporting values. Next, there are dips and spikes in traffic. This happens all the time. How can you better inform and proactively inform your visitors as to the nature of these spikes and dips in the data? And then lastly, all users are not created the same, nor do they all have the same reporting needs. Here we see an example where there are 500 different users for Adobe Analytics. You’re going to need to tailor and want to tailor the experience for these different users so that they can all get to the analysis that they need as quickly as possible. Next, let’s look at a little bit about phrasing these challenges in terms of how users might state their questions. Number one, there’s tons of data, where do I start? Well, the solution there that we’re gonna cover here is that you’re going to create a curated experience for these users so that you kind of eliminate all of that potential confusion that exists out there. Another question that a user may pose is how do they properly report on marketing channels or other items, which there are just so many options. Again, we’re gonna eliminate that noise by generating ways that they can answer the question that they may have in the agreed upon or best practice method. Next, you’re gonna have, I see shared segments and metrics. Which one do I use? We’re gonna talk about governance and how you can best manage that for your users. Next, as I showed on the previous slide, the changes, the spikes, the dips around traffic, we’re gonna provide date sensitive context around those things so that people don’t have to come and ask every single time, what happened on this date? Why was there a spike? Why was there a decline in this information? Lastly, there are many report suites possibly. Nowadays, we see report suites for geo-specific content. There are a lot of issues around that for privacy issues. There could be different components of the business that may have different report suites. So we wanna tailor that experience for users so that they see only the data that they need to see and eliminate that additional confusion. We’re gonna first address these issues and challenges by looking at curated workspaces and creating a tailored experience for your users. So let’s look at this first in terms of the challenge that can be encountered by your users. You have a robust implementation and it can be daunting for your users to analyze. As I mentioned earlier, there are potentially hundreds of events, props, EVARs, segments, date ranges, many different components that can confuse your users. As you can see here, this is the standard interface for workspace. What we’re going to want to do here is to create a tailored experience. We’ll do that by limiting the number of metrics and dimensions, segments, and these other components that are immediately presented to your users. This way we’re reducing the possibility of confusion, we’re shortening the time that it takes your users to create valuable insight because they’re not going to be confused or go down a rabbit hole of other pieces of this analysis possibly. And we’re just gonna reduce this complexity. And like I said, not everyone is familiar with the full details of your analytics implementation. As I mentioned at the beginning, you now have Adobe Analytics, what do you do? There are most situations where your users are not familiar with the data collection deployment of your implementation, and they may not know exactly everywhere and every place that every event or dimension is set on your site. So in terms of reducing complexity, we don’t want users to suffer from analysis paralysis. You can see here kind of an expanded or blown out view of what we saw on the previous slide, where we see all of the dimensions, the metrics and the segments presented to someone as possible in analysis. And I like to call this a fire hose of all of these different things. Another kind of bonus example here that I love and it’s something I frequently see is the situation where people are creating calculated metrics. You can see here there are five or six different bounce rates, which one’s the right one to use in this situation. This comes up quite frequently where every single user is creating their own bounce rate or conversion rate or average order value, they may all be the same, they may be different.

So we’re gonna eliminate this by turning this more into a garden hose as opposed to fire hose. So that you can still see everything that you need, but not everything that you may not need. So what we’re looking at here is an example of the dimensions portion of a workspace analysis. And this has been curated to users so that they can perform an analysis on products, page content and marketing channel detail. Maybe they don’t need to see user agent reports or other technical components of your implementation. And the great thing about this is that this still enables users to use all of the components. It just tailors the experience so that they’re immediately presented with the components that they are most likely to use or they’re most frequently used. Not everyone is a power user, so it doesn’t make sense to necessarily have every single component in the hundreds of variables and events and dimensions and segments that are available for every single user. It’s a little bit of an overkill possibly.

So how do you create these create analyses? Most of the time, as someone that has been in analytics and consulting for so long, I’ve seen many, many examples of times where implementations are done and someone has a workspace, they create this workspace, but they don’t do anything with it other than here’s the numbers. What we’re looking at here is if you go into workspace and choose curate project data, you create your workspace, you add the dimensions, metrics and segments that may be used in that analysis. Once you hit this, the available components within workspace are immediately limited to the components that are actively a part of that analysis. Again, those can still be used and you can still drill down and get everything you really need if you’re a power user, for example. Additionally, users or the creators of these workspaces can come back into workspace and add additional components that you think may be of interest to the particular users. Here, you see that you can drag from the bottom left over in the segments, dimensions and events up into the additional curated data. So while the user is presented with a workspace that is very specifically designed to meet some need, they still will have the option to drill down for additional detail into the areas of the workspace that you anticipate being of additional interest to these users. Next, let’s talk about notes and annotations. Again, back to what I said a minute ago, I think that a lot of users see dashboards or reports and they often have no context. They’re simply charts, line graphs, other visualizations, ranked reports and don’t really have any kind of context around them. The challenge there is that as an analyst preparing this, you’re going to be encountering frequent issues where the recipients or users of these workspaces can gloss over these things, not really understand all of the issues that they see.

And we’re gonna start providing that context and giving that detail with annotations. And if the annotations provide this date sensitive context around your reporting, what happened on this date? Why was there a spike? Why was there a decline in this data? When we create an annotation in a trended report, you will see an example like we see here where there is a small icon with a little bar underneath to indicate the time period in which some event occurred. And this could explain this drop that we see here in this example. When that is clicked on, it provides additional context so that not only do they know that some of that happened, which they may be able to identify themselves on the user side, but now they understand exactly why that data had that decline on that particular date.

Additionally, in your rank reports that aren’t really necessarily graphs or charted over time, the same annotations will be presented by an icon in those ranked reports as well, as long as the time range of your report includes that particular event and its occurrence. So this can provide a lot of date sensitive context around events for your users and eliminate a lot of the time that analysts and the creators of these workspaces have and take to answer questions about these spikes. The great thing about this is that it can actually spur additional questions and maybe more thoughtful questions by the consumers of this data. So in other words, in terms of why, the question will be more than what happened here, it will be why did this happen here? Let’s talk about what we can do to make sure that this decline doesn’t happen again, or how do we recreate this great spike that result in additional orders or traffic to the site.

Next, let’s talk about workspace notes. Workspace notes are also one of the most frequently underutilized aspects of Adobe Analytics workspace. Notes provide information about the analysis, the purpose of the analysis, how to use these components such as dimensions, metrics, and events that are a part of the analysis. Most frequently, you’re gonna have users that log into workspace, look at these things, and not really understand exactly where to drill down for further things, which segments can be changed. You can use this to provide direction to the users of this data. Here we see kind of an example where you’ve also included rich content and images in these screenshots that you see. This can also provide additional direction for your users. Again, so workspace notes and annotations used together can provide a significant amount of additional context for your users. Next, let’s talk about some governance of metrics, dimensions, and segments. And we’re gonna put this into the context of naming conventions, sharing, and the usage of classifications. The challenge here is how do you ensure that users are not confused and are using the right data points? And how are they able to understand these data points? So the solution is to create naming conventions and thoughtfully consider your sharing and governance of these dimensions.

If you do not consider how things are shared within your implementation and the values that are passed as a part of your reporting in EVARS and PROPS, then you’re going to encounter, your implementation is gonna become the Wild West of analytics. There’s just gonna be, as we saw a moment ago, five different bounce rates, same number of questions for 15 different segments that you’re gonna see. Here we see an example where there are 10 or 12 different segments here. I don’t know, looking at this as a user, which one of these are agreed upon? They’re created by different people within the company. Who is the subject matter expert or the person that I should trust to have created these segments and had to have created them correctly? Should I go and create my own? This can be very challenging and present another situation, like I mentioned in the very first challenge slide in that there are many, one question, many answers. If you don’t know which segment or event or calculated metric or different component to use, then you could have many different users asking the same question and coming up with different answers. You’re gonna encounter this a lot with marketing channel attribution, as an example, which could be satisfied by the curated workspaces component that we mentioned earlier, but you could have someone saying, natural search performed this way because the refer type of natural search is credited with this many orders or the marketing channel had this many orders associated with the natural search channel or maybe not natural search, but the tracking code report for paid search. If you rolled up all of your paid search tracking codes into a paid search channel, you’re gonna have three different answers for paid search, for paid search marketing channel, paid search tracking codes and paid search as a refer type. All three providing the same, answering the same question with different results. The best way to combat this is to create the idea or a concept of an approved creator for these different calculated metrics, segments, virtual report suites, which we’ll talk about in a few minutes and have that person be the known subject matter expert and owner of these items. That way you can create a governance approach within your organization so that all users understand that they should be using this particular set of segments, calculated metrics, virtual report suites, or any other analysis or project component that should be shared or could be shared with them. This creates a state of consistency for your business stakeholders, analysts and other users. And they’re gonna understand when I go to look for a segment, if it’s not there, I need to reach out to that person, have them create that segment so they have an agreed upon solution or agreed upon point of data for that particular item that others can use reliably so that I know that they’re going to arrive at the same results. Naming conventions we see here as another great example of something that requires governance.

We’re gonna talk about this a little bit more in the next slide as well, but here is just a kind of an example of a page name where you’re just gonna have something or segments where it just makes sense to have things in a readable format that are concatenated in a manner that is concise and clear. We’ll talk about that a little more on the next slide as well.

Again, the multiple bounce rates are just such a great example that I see every day for many metrics.

This is the naming conventions component that I mentioned. This, if you’ve been with Adobe as long as I have, you may very well have seen this particular screenshot that here that I have about content naming best practices. I think it’s been around, I mentioned I’ve been in analytics for 20 years. Of that 20 years, I have focused on Adobe technology and this might predate me. I remember this on one of my first interactions with Adobe, this particular best practice recommendation, and it still applies to this day. This is the five Cs concept for governance around page naming. And while this is around page naming, this can apply to any dimension, value, props, EVARS, campaign tracking codes. Here we see that this five C concept says, is it clear, is it clean, is it contextual, is it concise, and is it consistent? And all of these different components result in you having a dimensional reporting value that is consistent, like I said, is that last piece, but also reliable for your users. They can understand what this is when they see it and it’s not entirely confusing. So around content identification and that governance, as I mentioned, you’re often gonna have reporting values that can be complex or confusing. Tracking codes are a great example of this. Here we see an example where there are some tracking codes specific to different campaigns, engage, services, partners, and other campaigns. And in this case, they are clear, they are concise, and we can kind of understand what they mean. They’re also delimited with a pipe character, so that provides additional value. Where we can take this to the next level though, is that some of your users will want to understand your reporting and dimensions. And again, we’re keeping this into the entire, looking at this through the lens of making Adobe Analytics your own, kind of just bringing it back to that. How do you roll this up into something that’s a little more usable for your users and the questions that may frequently have? So how are our services campaigns doing? So yes, you can do a search in the report and see all of the different values that start with services pipe, as we see here.

But the best recommendation that you can do is to leverage something called classification rules. And what we’re seeing here looks a little complex, but basically it’s a regular expression that someone has created in Adobe Analytics that says let’s take that marketing channel detail value that we have there, let’s break it apart at that pipe character.

And then we’re going to place that first component of that concatenated string into a classification called channel detail level one.

And here you can see the result of this when it does show up in reporting would be that you would have a new report called channel detail level one. In that channel detail level one report, you’re only going to see those rolled up higher values such as services, engage, partners, stay current, et cetera as you see in that first screenshot.

The other thing to keep in mind too is that classifications are also great for creating this hierarchy or view of your data, but sometimes you may not be able to create conveniently concatenated strings. This is most frequent with products.

Products don’t usually have a well concatenated string. You may not have something that’s women, purses, leather.

May not be that convenient and typically it’s not. It’s usually something like CBA 1274, which doesn’t mean anything to anyone viewing a report. And in this situation, again, you do want classifications. However, to keep things and make this implementation of your own, you need to work with developers and IT to automate the upload of that product or catalog feed into Adobe analytics so that you can create different roll-ups for product category, product color, product size, et cetera. That will be another way that you can make Adobe analytics your own by taking care of all of the different content naming and rolling that up into the different aggregate reporting values that would be of use to your users. Next, let’s talk about virtual report suites and how we can use them to deliver only the data that is needed by your users. We’ve already talked about restricting the values and dimensions to make things more clear and concise for your users. Let’s now move that to the next step. Users can often be overwhelmed with a number of options to presented to them. And this is very frequently seen in report suites. As I mentioned early on, you could have report suites for different geographic regions. If you have a furniture sales site, you could have a commercial business and a direct to consumer component of the site. Those things may be very distinct in their business goals. And the individuals at your corporation that manage the direct to corporation sales versus business to consumer may not need to see each other’s data, just from a, not even necessarily from a security standpoint of your data, but also just to reduce complexity. So the solution there are what are called virtual report suites.

Here we’re gonna see an example of the different report suites that may be presented when someone creates an Adobe analytics workspace. You’ll notice here that there are a few with a, what looks like a little teal dot. Those teal dots represent what are referred to as virtual report suites.

In this case, a virtual report suite, think of it as a permanently locked segment. Here you can see kind of in this bottom example that this is locked to visits natural search. Maybe a little difficult to read that, but we’re talking about creating a report suite that is focused on natural search. This may be of usage to an SEO team within your company so that they are not confused by additional data points around other marketing channels, for example. This can greatly simplify the usage of Adobe analytics for your users. Additionally, it can ensure that you are using a single report suite as opposed to having to maintain a dozen report suites potentially. You can send all of your data to a single report suite and then create virtual report suites off of that global report suite as a way to further simplify things even on the implementation side and the analysis side. The other great thing about virtual report suites is that since they’re essentially locked segments for a report suite that has existed already for some period of time, any change you do here when you create this virtual report suite, it’s retroactive. There are a couple of other really cool things you can do in here that are really in the weeds like changing how long a session length is or changing the time zone. Maybe you have some users that are in Europe and you’re in the United States and they wanna see things in BST in England, for example. You could create a different view of a component section of virtual report suite so that they see that data in BST as opposed to EST, CST, et cetera here in the United States.

Again, this is just another great way to reduce the time that it takes for users to arrive at valuable insights. So in closing, what we’ve looked at here today is a way to make Adobe Analytics your own through these various features and best practices. I look forward to answering your questions coming up soon. Hello, Jason, what a great range of features from the five Cs to virtual report suites you’ve shared with us. Thanks, Sarah, I appreciate it. It’s been a great opportunity to speak and I look forward to answering any questions that might have come in. Excellent, because we have some really good ones here for you. All right, the first one up is, if I created workspaces for my users, is it possible to make it so users cannot alter the workspace for anyone else? That’s a great question, it is. And when workspace was first created, this wasn’t a feature and I think this came around a couple of years ago and I think it’s even evolved a little since then, but when you create a workspace, you can share it. And I’ll say that you can only share it with people that actually have Adobe accounts as well that are users, but you can give them permissions to either copy, view or edit the workspace. So you have a lot of options available. So most likely you don’t want people in there changing things, changing line charts, changing dates, changing the content, which immediately alters it for everyone, but you can most likely, I frequently see the ability to copy or someone can essentially do a save as, create their own version and create their own customizations within it while maintaining the fidelity of the existing or original workspace. Oh yeah, I love that. I make a copy, tweak it yourself, play around with it, that way you have the original. That’s a great one. Oh, too fun.

Well, talking about curating workspaces, another question that came in talks about asking, it’s asking about other ways other than curating workspaces that you could limit what people see in Adobe Analytics. So there’s a couple of different answers for that. That’s a good question.

First, I mentioned virtual report suites during the presentation just a few moments ago. So that is one way that you can limit that access to what people see, but even beyond that, and it’s a little outside of the concept of workspaces and reports is the admin console. You can create different user groups. For example, if you have a presence in EMEA and in the United States or North America, you can create a user group that has access to the report suites in EMEA or those only in the United States and kind of restrict access that way and limit their viewing or what they may potentially have access to. That’s actually one of the reasons you might also even consider creating virtual report suites in the first place. You might have a global report suite for which you create virtual report suites based on segments for EMEA versus the United States and virtual report suites themselves can be a part of that admin console group so that people see only the EMEA virtual report suite or the US virtual report suite as opposed to both or the entire global set of reporting.

You’ve given us a lot of good virtual report suites examples. I think you talked about like natural and paid search in your presentation and now having some geo. It sounds like you’ve done a lot with virtual report suites. Is there anything else that you might wanna tell us about virtual reports suites? I think the most common use is typically when someone has that global data repository that I mentioned. So a single global report suite primarily and then they’re going to break it out from that. Most of the time, most business users will wanna see the entire, let’s say retail reporting at a given time global level but then also be able to break it out easily at the different regional levels or maybe even different business components. And that’s probably one of the most typical uses of virtual report suites. I like that.

All right, I feel like I’ve set you some hard ones. So hopefully this one’s a little bit on the, not so intense side. They wanna know how did you turn on your dark mode? Because we saw Christos earlier did not have it on. So it’s interesting that you had yours on. Yeah, that’s an easy one. In the top right corner, there’s a little symbol. I think it looks like a little circle or a little pie chart that’s kind of gives you access to your account preferences within analytics. And if you click that, there’s a little toggle back up there for dark mode.

I think it’s just a more popular thing. It’s become popular recently for a lot of different sites and just how I choose to do it.

I know, I remember back in the day with ad hoc when it was, that was like the only thing that was dark and kind of looked like you had mission control when you’re at your desk. So it’s kind of fun to have it back again.

Now that you mentioned it, it’s also sort of worth keeping in mind too. And it hadn’t really occurred to me right now. And we may have a question about annotations and things like that later too. But when you think about how people might have dark mode or light mode, when you create annotations and add other contents into those workspaces, and consider the fact that you might need to think about people having light or dark mode gray and back and forth, things might look different. So it’s something to consider for sure. Oh, that’s not only is it good to remember, but it’s a great segue because we do have a question about annotations and asking like, how can you customize them? Like what are some examples of customizations to annotations that you’ve done? So it’s a very rich system, the annotations. You can create bullet point lists, change anything. It’s very much like a word processor like Microsoft Word or Google documents, for example, where you can just simply add bullet points, change font, italicize, bold, add images in there.

The most use that I see and the best use out of annotations is really providing context. Kind of like I said in the presentation, providing context around your workspace. More often than not, I’ve seen a lot of workspaces where it’s just some of throwing up just tons of ranked reports or charts. And without any kind of context as to what’s going on there, what you might be able to derive or learn about those things providing that context and some direction for the users is the best use of annotations. No, that’s awesome.

Well, kind of along the same lines as annotations, this question’s about like trying to help explain stuff in your workspace. It says, is there a way to insert a screenshot of the website or a visual of a webpage into workspace? There is. And I think I had one kind of blurred out a little bit to protect the innocent there in my presentation. So yes, you can throw images in there, but my only comment would be that it needs to be hosted somewhere, be that on your own CDN or within AEM assets, it needs to be hosted somewhere that you can access essentially by pasting in a URL basically. So workspace itself is not a repository or a database where you can just upload unlimited images. Nope, nope, yep. It is nice to add those images. So, oh, that’s cool. All right, so I’m looking through, we’ve got quite a few. Your presentation has spurred the questions. Oh, here’s a fun one. The kind of similar to one that we asked Christos too about his favorite. So what’s your favorite calculated metric to use? So my favorite metric, it’s one for which a calculated metric already exists actually, that’s bounce rate. There is already a calculated metric for bounce rate, but it’s worth explaining. There’s documentation that can be looked up about this, about what constitutes a bounce essentially. A bounce is a server call. It’s not just a page view technically. So if you have a page that loads and has a video that plays and you track that video in a server call, that’s one page view. And then immediately another server call happens for someone viewing that video on that single page. That’s not a bounce because there are two server calls that went out right then. But a lot of users may not really interpret a bounce that way. They want to know that someone saw a single page and then left. So you can create a calculated metric that’s, I just call it calculated bounce rate for lack of a better thing to name it, but which is just single access visits divided by total visits. So that’ll give you that kind of page level bounce rate that I think people probably would just intuitively understand a little more so than having to constantly explain server calls and other things that might impact that bounce rate. I don’t know, you could use your annotations and maybe an image and you could explain it every time. I do. It’s worth noting too. And I don’t think I mentioned this that in the calculated metrics, you can provide a description about those things so that when someone clicks the little eye icon next to it, they can see a comment or description of that too. So it’s worth adding that description as to say why you use this one. Sweet. And as long as there’s not five of the same calculated metric, right? Like you just want the one. Yeah, exactly.

Oh, too funny. Well, I was kind of joking around saying five, but I think this question lends itself to saying, how do you stop having so many? So with hundreds of analytics users, how do you recommend we get a handle on creating a single source of truth for shared segments and our favorite calculated metrics? So this is how do you know which of the five bounce rates that I’ve created it, you created it, and they can all even be the same, right? So there’s a couple of options. There’s a few that I can think of. So number one, there’s probably the most clear and obvious, which is the checkbox that says approved. So you can mark a metric as approved and view approved metrics and segments, et cetera. However, you may have a lot of admin users and there may be two or more people approving things that again, cause issues with multiple instances arriving of metrics and segments. Another option are tags. You can tag and provide kind of tags to just word tags. You might see in a blog, for example, for different metrics and segments and visitors can choose to peruse those different calculated metrics and segments by tags. And maybe your company can have an approved tag that has some kind of specific wording that they know to expect or look for. And lastly, you could also have a single primary, I guess you could call it maybe a super admin or an account in Adobe Analytics where this one person, or it can even be a single account shared across several people for the purpose of sharing this content. And there, everyone knows that this account, this calculated metric or segment was created by person X or account X. And those are the ones that are approved. And those are the ones that I should use and I should stay away from other ones just created by people as they choose. Awesome, so use the ones created by Jason, you’re good to go.

Oh, that raises a good point. If you do choose that method, don’t tie it to an individual actual person, I would say create an account because people leave and move on and change job roles. You can transfer calculated metrics and ownership of those things to another account. But if you kind of keep it in a sort of user agnostic account for the purpose of that, then you don’t have to worry about that transfer and back and forth and ownership of things too potentially. Oh, I like that. That’s a really good one, thanks.

Talking about sharing here, and we have a question that says, oftentimes I need to share out my reports with colleagues who don’t have access to Adobe Analytics. Well, that right there is kind of a sad statement. But the question goes on to say, can I share a working link to my dashboard or my report with them? PDFs maybe aren’t most ideal. So I sort of briefly touched on that early on when I was caught talking about the ability to view, the permissions associated with workspaces where you can either mark them as view, copy, edit. And I said you had to have an account to do those things. And that really applies here as well. So to share out that link, you do have to have an Adobe account. Someone would have to create one.

So no, you can’t share out just access to Adobe Analytics without having to someone that does not have account. However, there are PDF options with that, which I know may not necessarily be ideal. They can also be delivered through HTML and not necessarily workspace, but one other thing to consider is Report Builder. And this is just a tool that places all of this reporting in Microsoft Excel that can be updated and delivered to people through email. And most people are gonna have Microsoft Excel. That’s another option or consideration to deliver that reporting out to people that is maybe even in a way that they can manipulate themselves in Excel and see if they potentially update themselves too. Yeah, I love that Report Builder. Yeah, cause those can be scheduled. You can set them up, get them scheduled. They still have the good visuals. I mean, they’re not the Workspace visuals, but you can still do some nice visuals within Excel. And I’ll add, I think the Mac version of Report Builder is now to create and edit them anyway. I think it’s something that’s available now, I believe too. Yeah, yeah. I think like CJA maybe, I can’t remember. It might be one of those like nuggets for CJA, but, oh, that’s awesome. No, that’s great answer. Yay, thanks for thinking of something other than PDF. Let’s see. Oh, we’re getting down kind of here to the last minute. So let’s see, what’s our last one out. This is a good one. Someone was listening to your intro because they would love to hear any tips for the certification test.

So I did, I have worked with Adobe in the past to write Adobe Analytics exams. I will say that there are, that I’m aware of right now, an architect, a developer, and a business practitioner exam. And the way that they’re structured is I would recommend that people consider the use cases and business cases around why you might be doing things in analytics because the tests are written in a manner where you can’t necessarily or shouldn’t necessarily simply be able to just look everything up in documentation. You know, they’re not written for the point of just rote memorization. They’re been written for use cases and proving that you understand situations. Oh man, Jason, this has been so great. Thanks so much. I appreciate it, thank you. It was a great opportunity. Look forward to doing it again in the future.