Bringing your Adobe Analytics data and analyses into Customer Journey Analytics

Everybody. Welcome to the show this morning. This afternoon. Tonight, wherever you are dialing in from. Glad to have you with us today on this experience league live show. And we’ve got a great show for you today. We’ve got great guests to talk about. Some really cool stuff, bringing your data and your analysis into Customer Journey Analytics from Adobe Analytics. So we’ve got some awesome guests. Before that, I will just say be sure to go to experience league dot Adobe dot com. Your one stop shop for everything self-help. So you’ve got free courses and we’ve got tutorials. Of course that’s where you find the documentation. We got the communities there. Lots of great stuff. And so definitely go to experience link dot, adobe dot com to get help for any of those things. So let’s do it. We’ve got a couple of great guests today. First, we’re going to bring in Eric Matisse. Yo. There we go. And and we also have today Brian Skelton. Oh, Oh, you got actually a big crowd there going for him that had sort of had one of these maybe. And then. Like, my kids will appreciate that. Thank you. Yeah. Yeah. Great. So glad to have you guys with us today. It looks like we’ve got people dialing in from all over the place. It is awesome. Welcome, everybody. Founder and CEO, man, prog and Ohio. Love, Brad. Germany the gates. Good Martin and everywhere else. So let’s see the next one in Prague. Okay, Doug. What’s that? We’re going to do the next one in Prague. Okay. That’s a good. Idea. Okay. Yeah. Cool site. Yeah. Yes. It’s like live on site. Okay, we’ll do it. All right. So, yeah, before we jump into the topics, like, let’s introduce you guys. Eric, why don’t you start and tell us your job title and what you do all day? Sure. Yeah. My pleasure. Great to be here. Thanks, Doug. Thanks, Brian. My name is Eric Madsen. My role at Adobe is as the global evangelist for analytics and data science. I want to go to Costa Rica to Oh, man. And my role is actually I’m not on the sales team or consulting or anything along those lines. I sit as a part of our product marketing team and my focus is just helping to make sure that our customers are getting as much possible value out of our products as possible. So that means whether it’s sharing tips and tricks or sharing roadmap items or talking about what is possible, what isn’t possible, what’s coming soon, what we would never consider doing, all of those kind of fun things. And one of them is getting to work with my buddies, Doug and Brian, here to walk you through some of the latest and greatest when it comes to Adobe Analytics and Customer Journey Analytics. All right there. How’s that? Okay. Nice party. Well, great. Thank you, Eric. That’s great. And I’m going to be on Sneaks again this year at Fingers Crossed. I’m hoping so. You know, to TBD from what I hear. Okay. Well, great. I’m sure you’ll do great things at Summit this year. Okay. And, Brian, tell us tell us your role and and what you are doing there. Thanks, Doug. Really excited to be here with you and Eric. Brian Skelton. I am a member of a CSA Adobe’s consulting arm, been with Adobe for a little over eight years now and have focused exclusively on Customer Journey Analytics customers for the last three or four years. So really Lucky done a couple dozen implementations or been involved with most of the US based implementations of customer Journey Analytics. I’m remotely based in Charlotte, North Carolina, and it’s chilly here today, so I too would like to be in Costa Rica right now. What’s what’s your definition of chilly, Brian? Yeah. Well, it was it was 19 this morning when we woke. Okay. All right. That’s chilly. It was 16 here. But, you know, we’re not no one’s keeping score. But really sure somebody could beat that. Yeah, yeah, yeah. So. Yeah. Okay. All right. So cool. Thanks, guys. Just real quick, we saw on the what we call the lobby as that was. We’re getting ready to go then. Eric, I just couldn’t, you know, I had to first ask you about your minivan and. Yes, you. It sounds like you’ve embraced the minivan. Is that right? Oh, yeah. All the. Way. Why? You like the caravan so much? So I’ve got three kids and their ages six, four and ten months. And so we needed three rows. And we’re looking at the the like, midsize SUVs that have three rows and it’s got no trunk space. So then it was like, all right, are we going to look at a Suburban, a Tahoe or something like that? And that just seemed insane, especially in Little town America where I live, where, you know, my house was built in 1930. So they do not have room for a suburban anywhere. And I love it because I press a button and open the door. I press another button and the kids have a have the heat on. I’ve got the air conditioning on. Yeah, yeah. It’s fully functional and it’s a hybrid. So I get like 38, 39 miles per gallon. Nice. And try doing that in the Tahoe. Yeah. Well that is, that’s great. And not to mention, you know, room for musical gear. So when you are going to the gig you have all your gear right. Yeah that’s the thing is tons of. TrunkSpace I don’t have to bring my drums with me anywhere lately, but I do have to bring kids bikes and scooters and, and soccer balls and things like that. So yeah. That’s it’s. All right. It’s nice to have that. TrunkSpace Space Yeah. Cool. Okay, awesome. Brian We saw on there that you are a too freakazoid. Wouldn’t be the term I use, but yes, quite the fan. I just I want to know and you’ve been to many concerts. I saw that you got one coming up. Right? And, and do you go backstage and hang out with the guys? Unfortunately, no funny story. I told my wife when we were dating. I said, if you could somehow get me to be able to meet Bono, I will marry you. And she she looked into it didn’t happen, but we got married anyway. Yeah. Yeah. So a bunch of different shows, a couple different countries actually took my kids to their first U2 show over in London. And then looking forward to being in Vegas a little before the summit to see them at the Sphere in Vegas. So well forward of that show. And then yeah, so hopefully I’ll see some of you in Vegas as well at Summit. Got a got a DJ lab on tap and I look forward to share for that cigar. Goodness. Nice. Amazing. Well, that’s fun. Let’s dive in, guys. I think we’ve got a lot of people here very excited about the topic today that people reach out to me and tell tell me that. So that’s great. So, Eric, why don’t you kind of frame some of the stuff we’re going to talk about today? Yeah, for sure. My pleasure. We have a lot of topics to cover, so I’m glad we’re not wasting any time talking about minivans and and our favorite bands. So many bands and bands. That’s the name of our podcast, guys. Yeah. And so we want to talk about, first of all, data. How do we get data into C.J. that was generated in Adobe Analytics? So this is your web data, your mobile app data, your digital data. How do we do it in a way that is convenient, that is accurate, that is reliable, and what are the gives and takes? What are the pros and cons with everything? Adobe you know, since the, um, the days and before there’s we’ve had a focus on Customizability and I personally find Customizability to be like a double edged sword. It’s like, great, because you can be super flexible, but it also is a little challenging because it means you’ve got all these decisions to make along the way. And so data is our first topic. Our next topic is going to be around analysis. Everyone in here has probably spent months, years, decades analyzing data within Adobe Analytics. How do we take those analyzes and bring them to the world of Customer Journey Analytics? So we’re going to talk a little bit with you there as well. And then the last thing is around our especially for our administrators, how do we plan for bringing users along for the ride of, you know, going to the tool that they’ve been using for, again, years, decades, maybe more centuries and, you know, for for some of our oldest customers, how do we make sure that they are migrated properly and have the right access and the right ability to succeed? So those are a three topics data analysis users. Nice, Nice. Okay, so data, let’s do it. Let’s talk data. I love talking data. This is this is why it is why I work here. So so there’s a number of different things that we can that we can do when it comes to data. There’s options, as I was mentioning, there’s all sorts of options that you have as an Adobe Analytics customer for how do I get my data into Customer Journey Analytics to take advantage of all the amazing things that Suja brings our customers. That is usually one of the topics that we cover within our webinars. Usually we’re asked, we’re talking about different fields and data views and all these amazing and omnichannel and visit stitching and all these super cool things. But we thought, why don’t we take a step back a little bit and think about how can we what are the options for getting data from Adobe Analytics into Customer Journey Analytics? And so the there are two ways that your web data, your digital data, your mobile app data can come from Adobe Analytics if it’s living in a report suite or coming from your digital experiences into Customer Journey Analytics. And those two ways are, number one, the analytics data connector, we internally, we’ll call it ADC Analytics Data Connector. How can data from a report suite get pulled out of Adobe Analyze that pulled out but pushed into Adobe Experience platform so that you can then analyze it? And the reason I actually corrected myself there is we’re not we’re not actually removing it from Adobe Analytics. We’re, we’re copying it into so that way you can, you know, we’re talking about what the process is. You can continue to utilize Adobe Analytics for months, years, however long you need to and what’s great is for those that are ready to also analyze that data and it’ll be there as well so that you can just simply prefer in that copy. Actually, you know what I’m realizing, Doug, is it may actually be a good time for me to share my screen, which which I didn’t think I was going to do until this very moment. So how about I. But I do that and you let me know when it’s when it’s ready for me. Okay. Give me a second here. And we are we’re on. We’re seeing your screen. Awesome. So there’s this one really nice diagram that we’ve been trying to keep up to date over the years called the Adobe Analytics Processing Order of Operations. Something along those lines. You can get to it really quickly by going to a lower case Adobe Y slash a processing. And I think Doug can take that URL and and share it to y’all shortly as well. But when you get there, it’ll bring you to this page which has this pretty hefty diagram for you. And I like to just open it in a new tab and zoom and this gives you a feel and remember, this is this is actually getting data into Adobe Analytics. But what’s really nice is understanding how that data also where your options are forgetting that data into Adobe Experience platform. So we start all the way on the left here you’ve got the Web SDK, the Mobile SDK, the Edge Network Server API. You can send that data to a data stream, you can prep it a little bit. You can also push it off to event forwarding for sending conversion APIs and all those things. Or if you have the legacy tag library, we’ve got that and that goes through some preprocessing. So IP obfuscation, obfuscation, they’re is passing rolls. This are rules and marketing channel rules. And then this right here, this blue pipe that gets you into the analytics data connector. ADC So we’re sort of pull it, we’re copying that data out of the middle of the pipeline here in order to send it into Adobe Experience platform so you can analyze it and it. And the reason I wanted to call that out here is there are some things in our processing pipeline within Adobe Analytics that we aren’t necessarily doing, but that a lot of those things are because they’re really not necessary and because of the flexibility of what comes with data views and and your your, your, your best practices when it comes to setting those up in that that Brian can also talk about as well. So I wanted to point out I just wanted to pull up this this order of operations for you. I thought it could be helpful in that we’ve got your two options listed right here. You can have Web SDK, go to a data stream or a mobile SDK or Sun to enter an API or go to a data stream and it’ll get sent. We can even manage that data a little bit. You can finagle it using using data. You can just have that follow these purple or pink lines straight into Adobe Experience platform and you can skip everything that there is within Adobe Analytics. So that’s option two. That’s using the Web SDK to send data directly into Adobe Experience platform, then analyze it within. Yeah. The other is going through this pipeline where we can say, you know what, You can even continue to use that measurement. You can continue to use G code. If you’re crazy and send that data into the Adobe Analytics processing pipes. And that will also mid-way through get copied into a data set with an Experience Platform and it will continue to go through all the way through to data feeds, classifications, real time reports, cross-device analytics, stitching, all that good stuff. And so that’s everything I wanted to share here. Doug So you can, you can kind of take us back if you’d like to, but there are a few items that I thought maybe the three of us could kind of wrap on. Yeah, yeah, that’s good. Just to make sure that I got this right. Right. It was Adobe Dot l y a processing. Yes. Yes. This is something. I go through all over again. Another Rudy tried to post up and maybe it didn’t come through. Let’s just see up there it is. Hopefully that. Will. Oh, that’s, that’s you know. I don’t quite know by How about that. Oops. Let’s try it out again. Yeah. Adobe Adobe dot l y a processing. Yeah. No extra charge there. We don’t have Adobe right away. Processing. Look. There you go. Okay. Yes. The thing I wanted to amplify what Eric said, it’s, it’s a really important point. It’s great. The analytics source connector is awesome for bringing in all that data are used to seeing a traditional analytics, which by the way, you can continue seeing in Adobe Analytics. Right? This is not an either or. You can continue to send your data to Adobe’s data collection servers or report on it in traditional Adobe Analytics, but also send it to APP for transition time. The key difference there that mid values data has no persistence applied and we’ll cover that a little bit more when we talk about data views in detail. But it’s extremely important to understand that everything in that Adobe data Connector data, everything is like a prop. Everything in, in that source data set is same hit persistence, right? It does not. There is no persistence. So it’s a really important concept. But we have so much power for what I call the magic of CG and data views where you can customize persistence. So you may have your own settings in traditional analytics, but we have just an unbelievable amount of customization that’s available in CG at the data view level. So we’ll look at that in a little bit. Okay, cool. Yeah. Yeah, that’s a great point, Brian, is is that data coming out of that analytics data connector, that blue pipe we’re talking about, everything is is expiring on that hit by default. And then the really fun part is what you can do with it later to say, you know what, let me customize this. Let me change how it said, let me duplicate it and have a few different changes, all sorts of really cool options. Brian, what are what do you see in your customers and your clients do with classifications as their considering, you know, analytics, data, connector, web SDK and beyond? Yeah. So you alluded to this, Eric. You know, you have some customers have been using traditional Adobe Analytics for a decade or more, right? So they’ve got really robust, highly customized implementations, including things like classifications. So our product and engineering teams have tried to make it easy to actually bring over those same classifications that you’ve worked in for years and fine tuning, right? We do have the ability at the source connector level to bring over those classification files. We call them look up datasets in AP and CG land, but you can seamlessly bring those over a little bit of, you know, Eric mentioned there’s always tradeoffs or a little bit of tradeoff is there is update once a week. So if you have something that’s more important or refreshes more often than that, we actually have another path, right? You can create a custom data set within API, bring that into CGA and update that at your own cadence so we try and make it easy. There is a push button option if you have more advanced needs, we have more advanced options. Nice. Kind of a easy, more simple route that gives you some of what might, might work for most people. But then yeah, you can, you can always get a little bit more. Yeah more often that great. Before I let this pass by I will also say that Bill asked for an example. Let me see. Maybe we can put this up here. It’ll work. So the better. An example SDR provided by Adobe for saw that bill we are creating and I think I’m trying to remember if we already updated the one that’s inexperience league if your search experience league for, you know like SDR and and VRD we have some tutorials on just kind of how what kind of things to think about when you’re creating those and we have updated those somewhat for moving through to to Customer Journey Analytics I believe. So I’ll also take a look at that and make sure that that’s that’s been updated and hopefully that will be really helpful to you when, when you can download that. Otherwise I’ll get up there. Okay, cool. We have another question here from Victor. Victor says the CGA allowed users to reproduce post processing rules like Vista once. So the short answer is yes. And what’s impressive and powerful and maybe share a link if we can find one on experience quickly about dry fields, what’s especially powerful about them in the way that we’ve implemented them in Customer Journey Analytics is that they’re fully retroactive. So what that means is if today, if you’ve been collecting data for six months and today you decide, Oh no, you know what? I want to every time I’m collecting the word Brian, I’m spelling it with an eye. But I meant to collect it with a Y, which is the way the brain spells it. You can use a derived field to retroactively make that adjustment so that not only from today going forward, well, Brian bestowed correctly, but also the last six months worth of data or or two years or ten years worth of data is fully updated as well. That’s made possible because so much of how Customer Journey Analytics works is through is done by report time processing. So as soon as you make the request, we’re saying, okay, run that through these rules. Those rules can include attribution settings and persistence settings similar to those that you’re used to within Attribution IQ, within Adobe Analytics, but they can also include you just set this, set this dimension to always be lowercase, which is a big one, you know, especially for global organizations. Think about like marketing teams that have campaigns that sometimes will have the camel case, their campaign names or sometimes they want, well, you can consolidate them together and it’s duplicated. It’s all lowercase little things like that. They can go a really, really long way. Yeah. Yeah. And the big thing to emphasize what Eric just said, CGA is entirely a report time processing engine. So everything that we’re going to show you in data, views and derived fields, you literally make a change, hit, save. You can go refresh in your report and all of your data retroactively and going forward reflects that change. Super powerful. Yeah. Yeah. Right cool. And and that actually kind of aligns with one of the topics I wanted to discuss around data, which is marketing channels. And for you go, Brian, I’m like this also, let me just also tell Victor that you’re right, I don’t have the URL on hand, but if you go to experience like the dot com and you go to the tutorials and then and go to the tutorials and then you can find we do have some, some, some tutorials there on, on the derived fields. So you can take a look at those there as well. Fantastic. Sorry Eric, keep going. Know perfectly fine. So within 2 to 3 to do within those same report time capabilities are considerations around marketing channels. We’ve got marketing channel set up in Adobe Analytics that have been set up and reasonably reliable for how many years. And you need to think about like, okay, well I’ve got a new place that I’m going to be analyzing these. We’re just looking at that analytics processing order of operations that the pipeline there and we are applying marketing channel rules to the data that comes in and the question is, do you want to continue to use those marketing channel rules or do you want to expand on them or start from scratch? Brian I’m actually curious. You know, you’ve worked on just as many AA implementations as probably anybody. Yeah. So when I started working with customers on marketing channels, I had hair and. Now. That’s changed a little bit. So as Eric alluded to. Young, our our analytics customers have been using marketing channels for a long time, and some of them are very, very, very, I don’t know, very jealously guarding their marketing channel and reporting. Some people actually have like business incentives tied to their Adobe Analytics marketing channel reporting. So change is hard, right? So CGA is an entirely new reporting engine. As Eric mentioned, we do have marketing channel information in the analytics source connector, so seamlessly push a button, bring in your analytics data into CGA, and it’ll also include some marketing channel information with some minor caveats and those minor caveats cause some customers heartburn. The good thing is Eric’s already talked about it, right? So, you know, our product team over the last years as we’ve been developing CGA, they realize there’s some gaps here and there, so they made this thing called Drive Fields, and that is like the super glue of CGA, right? If you need to fix something typically derived fields is your answer. And so Web SDK data collection, right, bypasses that whole analytics processing engine goes right into API. What happens with marketing channels, right? Because marketing channels was Adobe Analytics only construct We’re go web SDK, right to AP. What what about my marketing channels? You know somebody could get killed if I don’t have my marketing channel data. So we’ve created a that capability within drive fields. We actually provide a template within the derived field library to help you recreate that marketing channel reporting. Again, some caveats because there are different processing engines. We don’t have some of that post-processing that you typically get in traditional analytics reporting, but again, much more powerful because it’s on the fly and totally customizable. So yeah, there’s been some bruises, Eric, in dealing with marketing channels with different customers, but again, super excited about dry fields in the possibilities that offers because no longer you limited to the way that Adobe Out of Thin Air came up with marketing channels I don’t know, ten years ago and that’s the way marketing channels have always worked and will always work. Now you have some more flexibility within CGA and dry fields here. Like my favorite part about it is the amount of time I used to spend debugging marketing channels in Adobe Analytics was it like it feels infinite? You know, you would start by saying like, Oh, you know what, this one thing seems off and then you would break it down, you would correlate, you’d separate a segment, you’d kind of figure, Hey, you know what? Okay, we’ve got a problem. And then you dig into the rules and you say, okay, well, the rules look right. What’s going on here? And then you export a data feed from a day and like, then, yeah, that’s the reason Doug has the most hair out of us. I’m like, in the middle with still some remaining. And Brian has spent the most time consulting, which is why he’s got the least a year an we’re in order here and but the whole point is, you know it’s so much easier to do that debugging within CGA because you can just make the switch and see and see instantly what the changes were. You can instantly say, okay, did that fix the problem or did that cause a new problem? And you know, there’s there’s a question around when you make these retroactive changes from first year. Doug, I don’t know if you want to throw that up on the screen. Will that change any reporting that included previous input? And the answer is yes when you know it like not to be Uncle Ben, but you know, with great power comes great responsibility and I’ll go back, right? Yeah. I’m like, okay, I’ll go back. And so so that’s really key when it comes to making these tweaks, when when it comes to marketing channels and the rules that define them is what I like to do. And Brian, I would, I would bet you have bunch done a bunch too is actually duplicate it first test out my changes so I can know. Okay did it pass my Q A It’s just like saying of tags. But the advantage is if you break something you just delete it. It’s got right so you can really so I really like to duplicate and then edit find my solution and then bring that back to the original value. Yeah, yeah. Great power. Like you said in CGA, the ability to change that and date of you, which is a virtual thing, hit refresh, see if it fixed it. Now, in traditional analytics, you know, your option is like to reset all those channels and then you’re starting basically from scratch, right? So then you know, you got marketing channel data from forward from that change, right? This applies totally retroactively. So it is really powerful. Cool. So let’s see, I don’t know if we want to dig any deeper on maybe our last topic with data or kind of move on. What do you guys think? Yeah, Brian, did you want to do something with connections at all? Yeah, we can. We can talk about connections. Next, I’ll go ahead and share my screen and take. A couple of minutes. I think we have time for a couple of minutes there. All right. So I’m there is a question. I don’t know if you guys want to talk about that while I’m starting to share my screen. I just mean it might be above my head. Let me see. We got there. So any timeline to have something like advertising analytics and see J or can you bring your G 360 advertising data in as a data stream. That we are looking at all different ways of connecting data from non Adobe systems and non first party systems into Adobe Experience platform for analysis and, and that includes data like advertising data. The fun challenge of course is that big old thing called cookies and identities and stuff like that. We want to make sure that as you’re pulling data out of paid search publishers or social media publishers or display media publishers, etc., that you’re able to link it properly. And if you’re not able to link it properly, at least similar to how we do advertising analytics in Adobe Analytics, we can align it as best we can. And so we’re toying around with a number of different ways of, number one, getting that data out of those systems. The really fun thing about Adobe Experience platform is we’re no longer thinking about just analytics. We’re also thinking about activation through Real-Time CDP. We’re also thinking about delivering personalized messaging through Adobe Journey Optimizer. We’re also thinking about mix modeling, so how we can send their plan a scenario and for our costs. And that last one is the one that really gets me excited for this topic because you can’t do mixed modeling if you’re only limiting your data sources to those data sources that have an identity. And so I’m not giving you a full answer there, Leonor, but I think you can kind of like read between the lines a little bit around how we’re thinking and how we want to make sure that you feel confident with the data you’re pulling in and that it’s integrated to the best of your and our abilities. Thanks, Eric. Okay, let’s jump over to Brian’s screen. All great. Thanks, Doug. What do you want to show there, Brian. Yeah, so Customer Journey Analytics friendly we’re. Seeing on your screen. Let me see there. Yeah, sorry. Okay. Now within, you know, internally we often refer to CGA customer Journey analytics as works based on platform, right? Because if those of you who have seen CGA or had access to it or had a demo, the interface looks exactly like traditional analytics, right? That workspace interface goes across both tools. The difference is with CGA, you know, the analytics data, right, went off into those Adobe servers and you never saw it right within customer Journey Analytics workspace on platform all the data exists in platform first, right? So we make it super easy, whole bunch of different connectors, easy ways to get data into app, right? You could click a push button, get access to your report suite data and have that start flowing into Adobe Experience platform. Right? These data sets, your analysts aren’t ever going to need this or use this or even access this, but it’s really important for you as the expert in your organization, to understand where this data comes from. So, you know, CGA doesn’t you know, I often get questions from customers, Hey, how, how come, you know, how did CGA change this data or what they do? How come this data did You didn’t do anything right? It reads what comes into platform and reports on that. And to tie in to the last question that came in, you can certainly bring in A360 data or any data, right? You can bring in your, you know, your health data off your watch. Eric has, you know, tracked his what was it, your soccer league. You knows all different things. CGA is very agnostic, right? So yes, it’s optimized obviously for for for digital data. But you can bring in anything as long as it has a person ID and at times it works better when it correlates to other sources with the same identifiers. But anyway, we can bring in this data into into app. I often like to go ahead and take a look at the data. Right. So again, this is more an administrator view where you’re actually looking at the underlying data. This is something you couldn’t do in traditional analytics. What you’re about to see here. We’re going to preview the last batch of data that came into ADP from an Adobe Analytics report suite. This is actually for our Adobe Store swag if you ever want to get some extra stuff. But we can go ahead and see actually again, we’re previewing the last 99 rows of the most recent batch, but you can actually see the values in here. You can preview the schema and see what type of you know, what type of scheme of value this is, whether or not it’s a string or a number that determines whether or not it’s a dimension or a metric. And all that just makes it really easy to preview what data you’re going to see in CGI. And actually you can actually edit this information, right? So yep, you have access to this, you can run data distiller on this, you can edit it on the way into ADP with our data prep functionality, not having to use Vista rules or engage the Adobe engineering teams and pay all that extra money to to edit your analytics data. Much easier to do that now in Customer Journey Analytics. This all comes together. I’m now looking at the CGA interface right now. This is again an administrator view. I can see this connection tab in the state of you tab. Your normal analysts will only see the workspace and components menus. They won’t see this, but it’s important again to understand how all this data comes together. So if I’m making a connection, right, I can see that this connection here is actually made up of two different data sets, right? So no longer are we looking at single channel data like in traditional analytics where maybe you combined your your web and app data, right? We can bring in all sorts of data, including other Adobe app services like Adobe Journey Optimizer. We can bring in call center data, we can bring in point of sale, right? All that offline data, all that information can be union together in a CGA connection and that concept is super important union, right? So all the data sets that are in a connection make up one new big super wide table. So every column in all those data sets gets added to every possible row. And that’s where then persistence comes into play, right? You could have an action or an activity in your call center that actually applies or gets attributed to something that happens later on in your web data. If those IDs match, right, that person ID matches. So data comes from AP gets union together in a CGA connection. And then we’ll talk a little bit more about data views in a while. But data views are the virtual settings on top of connections. Quick reminder here I like to be conservative with connections. Liberal data views. Connections are hard copies of data. That’s what we actually believe against all the data that’s in your connections. SO even though it’s very much a push button interface, I do wish there was a little bit more of a I don’t know how to say this an idiot filter on this because you can actually do some things in here that you know have import in terms of how long data takes to re backfill or things like that. So be careful with your connections make as many changes as you can in your data views. It’s again it’s a good tip conservative with with connections and liberal with your data views. Yep yep. Cool. Before we move on, maybe last thing and then we need to move on to data views. I just wanted to know there’s a lot more we could talk about for every for each of these sections, but I just wanted to chat with you guys for one second about Aaron’s questions about validation. Right. It being it’s a little harder, right, with C.J. and we think we need to you know, it was it was so easy to just like use a, you know, the debugger or whatever for stuff coming out come coming through to Adobe Analytics. Well what are your what do you have for tips or something regarding validation debugging. I’ll go first Eric and then you can then you can add on. So tend say, don’t worry, right? So CGA the data doesn’t come directly to see the data goes to. AP Right? So you do a lot of your validation within AP. So here’s here I’m doing some validation. I’m seeing what types of values are coming into each of these fields. Not only that, there is the ability within AP to run a query on that underlying data set, right? That’s something you could never do in traditional analytics. Once that data was in there, the only way you could see it is in the workspace interface. Now we actually allow you to run SQL to again validate your data. So even once you get some basic abilities to validate data using query service, some more advanced capabilities with the data is still our product. And then, Eric, I don’t know if you want to maybe talk about what folks do with Web SDK. Yeah, absolutely. So there’s a number of things to discuss. Yeah, please. Okay, let me know on some sharing here. So I just pulled up. Okay. Adobe store become awesome. So Adobe store dot com is that is feeding data from the web SDK into that dataset that Brian was just sharing and here’s like my number one tip for using the network tab within your browser. I use Microsoft Edge, but it’s chromium, so it’ll work the same within Chrome as well. When you select your door, your request here and go into payload, a lot of people just kind of click, click, click, click, click, and it takes forever. I’m a really big fan. I’ve been talking about right clicking, it seems like my entire career at Adobe, but this is another chance to talk about right clicking. So if you right click here and just hit expand recursively. But a big bar, boom, you got everything you need. Every single object in array is opened here right for you within the event that you’re trying to analyze and trying to debug. I’m also a really big fan of the Adobe Experience Platform Debugger, and there’s some really nice things you can do around the Edge logs feature. I think I’m probably not logged in here would be my guess. Just knowing myself. So I don’t. Yeah, but there’s a, there’s some really nice capabilities around not only seeing the data that is being sent from the client, which is what we’re seeing here in network. But if you log in and connect with the edge logs, you can also see how data prep is affecting your data collection as well. So the very last thing I’ll mention around this topic around debugging is the really nice thing about Customer Journey Analytics as well is we are you have access to identities. So if I were to pull in a blank panel here and just say, you know what page are row and look at identity, I can actually see every little ECI ID identifier that is being used. And imagine if I obviously I have my XD memorized. What I could do from a debugging standpoint is you know, I could actually see exactly how just for me, all of my events are being captured in Customer Journey Analytics. I can do that with any type of visualization, of course, because that filter is applied to the whole panel. So I could look at flow or fallout or beyond. And so I think that’s a really nice way to have like multiple levels of debugging, which I’m a big fan of. So you’ve got debugging from the client within the network tab over yonder. And again, right click expand recursively and you’re going to be saving some some time there. You’ve also got, if you’re using data prep to manage that data a little bit before it gets fully ingested, then you’ve got those edge logs and then you can also, once that data gets into, you can also filter based on just your own said you can even create your own data view, which is a perfect segue way into our next topic that is aligned with your XD or your staging environment or something along those lines. Nice. So one thing as Eric transitions in the state of use that he kind of glossed over, CGI gives you row level access to every hit or event in all your event data sets. No unique succeeded you could filter down as Eric just showed you to any dimension value, any high cardinality dimension. You actually have row level detail to every single dimension value both for filtering what we call segmentation in CGA and reporting. Right? So you can drill down as so as narrow as you want. That’s a huge and I came from the client side and that was, you know that was always such a pain. Right after the third or fourth day of the month, we had unique succeeded in our in our reports right now you no longer have to worry about. That. That is awesome. That’s awesome, guys. Yeah, we definitely have to make. A pass against that. Yeah. Let’s move on to, to talking about some data views tips. Yeah. Great. Yeah. Thanks, Doug. Am I sort of sharing my screen bar? I don’t need to be. Okay, cool. We can. I can stop sharing. We can. We can have a little fun little conversation there. Okay. We’ll go back to conversation mode. There we are. Conversation mode. How’s it going? So so one of the really interesting things around data view. So data views I like, I like to think of them as connections is how data gets into a similar to like your report suites, data comes into report suites in Adobe Analytics, but then you have this additional filter and and level of customizability that you can apply to that data after the fact. And that’s where all that rich port time processing that we’re talking about comes into play. And that’s within data views. It’s kind of akin to a virtual report suite in Adobe Analytics. But you know, as the entire tech world likes to say, it’s like virtual report suites on steroids. You’ve got all these way more powerful things that you can do within Customer Journey Analytics, within a data view that you can do within a virtual report suite. And one of the things I’ve become a really big fan of Brian and I were talking about earlier is around using virtual report suites as a means for governance, not virtual reports. It’s using data views as a means for governance, and it’s actually something that we recommended within virtual report Suites and Adobe Analytics as well. It was, you know what, if you want to give access to your paid search agency or your digital agency access to a slice of data, you apply a segment and then give them access to just that virtual report suite. Then they can go to town and they won’t have access to your full set of data. You can do the same thing in data views, but you’ve got way more power, way more flexibility and more control over what they can see. You can you can limit the components they have access to. You can set unique attribution and persistence settings and more. Brian I don’t know if there’s anything else on top of that around governance that you wanted to add in as users are kind of mixed up migration. Yeah. So Doug, if you want to let me share again, you know, we’re the key thing. So you have the component level governance of a data view. You can remove as many components as you want, you can make customized settings however you want, but then once you’re in, in the admin console here, right, I’m showing some product profiles for Customer Journey Analytics CJS managed in the Adobe Admin console. Fortunately, unfortunately, depending on your opinion and we have the ability within each of these product profiles in permissions. Right? The data views is an area that you can choose to give access to for that product profile. So product profiles can include people and or user groups, right? So if concerned conservative, your connection put all the data in it. You make a data view that limits it down to certain components or types of data via filters. And then on top of that, right, you can choose to actually add all auto include, you know, for your power users, every data of you or specifically include only a particular date of you. Then it doesn’t matter what data is in your connection. Call center data could be in there, but if that data of you that this person is enabled to see or this user group is enabled to see, if that doesn’t give you permission in the data for you to see what’s in the connection, it doesn’t exist for them. All they can see is what’s enabled at the data view level and then this additional level of governance at the product profile level gives you that more fine grained control over who sees what. Yeah, big time. I don’t I don’t want to spend our entire time talking about why data views are great. That’s for that’s for another conversation. Time a little bit but keep going. And and so I wanted to just kind of quickly review just a few best practices or ideas that we’ve seen customers utilize data, view customizations and derived fields for. And they are marketing channels which we’ve already discussed Dimension cleanup, which we’ve kind of touched upon. But if you’ve got page names that are messy and need to be cleaned up, that’s a great way to clean them up. Bucketing regions, link types, page types, all of that good stuff. Brian had this great one around data set friendly names. It’s like very simple dataset IDs come in, which is this crazy long alphanumeric code that Brian memorizes but no one else does. And so you can basically apply a classification to those data set IDs. And then the last one, Brian, I don’t know if you had any like best practices around attribution settings or persistent settings for refers and marketing channels and like how you’re seeing customers consider those. Yeah. So I think the product managers made a opinionated effort on this, right? So we don’t automatically bring over all of your analytics settings, right? Because we realize this is a new world within Customer Journey Analytics. Now you have the ability for each of these dimensions to go in and set customer persistence right again at a at a default. It’s all same hit. There is no persistence, but you could easily change that to all of the, you know, allocation and expiration options that we have, including some more advanced look back windows within CGA. So we don’t automatically copy things over because it may not make as much sense in a new world where you have multiple channels, right? You may want to customize how much you persist a marketing channel or whether or not a referrer should impact attribution for a call center or point of sale transaction. So all of these are able to be set to the same level that you had in traditional analytics, but by default they are, as we mentioned, same hit persistence. So you have to customize them if you want them to act exactly like Adobe Analytics or you may want to take this option, particularly as we talk about other migration efforts to make more informed decisions about how you do that. I know, Eric, you had that one example around referrer that you wanted to share. I forgot. That. That’s okay. The since referrer comes in also hit based you want to set it to be. We’ve got some options around first known and last known that are specifically referring to refer. So keep an eye out there because the way the web SDK works is every single hit has the referring your role in it. So you’re not going to want to know that for you’re not going to want to set that and think like, Oh, there’s all these internal refers. No, in in reality, it’s just we’re sending it on every hit. So you want to set the date view to have the persistence of first known for example within that session. So some kind of key things to keep an eye on. That’s a good tip on that one. We’ve talked about data. We’ve talked about users as well around some of that governance that Brian was sharing, like the very last one and maybe like we take two or 3 minutes, Brian, to kind of walk through how you’re seeing customers and what you’re doing with migrating projects from core Adobe Analytics within WORKSPACE over to CGA and what some of the some of the kind of cool things you’ve seen folks do on the web. Yeah. So, you know, really excited about this product feature that only became available second half of the year, right? So, you know, we have a lot of analytics customers and we hope that they eventually are going to enjoy Customer Journey Analytics. We’re trying to move some, remove some of the friction because again, you may have ten worth of workspaces and, and calculated metrics and segments, right? And there’s an app which say a dairy does. Yes. Centuries of data. Yeah. So we have a new tool. If you’re a Adobe Analytics admin, you can go to component migration and have access to your projects and choose to migrate them when you enable this flow and go through this. Right? So I’m going to set myself as the owner. You can set somebody else is owner and then I want to choose my destination date of you, right? So there’s all the different ones that are available. And then you have this map schema and this actually gets remembered. So it makes it easier to move over multiple reports later. If there is a segment or calculate a metric within your project, it actually goes ahead and includes that information as part of the what you’re migrating. So, you know, even let me see if I can find that project real fast as well. Any anyone that you’re moving to, if I’ve got migrate, I don’t know where I put it, but if there is a again segment or how can a metric included in that project, this is part of what gets it moved over. So every component in the tables as well as any segments or know metrics that are applied get moved over so that in CGA you will then have a exact duplicate of that project available with these segments and calculate a metric supplied. Now there is a process where you have to map things and sometimes there are some components that don’t exist, right? So CGA doesn’t have an equivalent of, you know, page hit depth, for example, but you could apply a catch all or any sort of derived field, right, to use as the, the way you want to map that so that then this mapping process will complete and the project to migrate and it takes again, just a couple of seconds. So for elements that don’t exist in CGA, recommend going ahead and creating a catch all that you can then go to the destination project in CGA and edit it there. You can remove it out or replace it with something else. Yeah, and just some of it. I’ll just kind of add. Yeah, I have a couple of, of tutorials of videos on experience like that that I’m updating right now because they say actually if you’re moving your calculated metrics and your segments over to CGA that you basically have to recreate them. And that is no longer true because of this, right? So I’m actually updating that. So if you watch my video in the next week, then then don’t be alarmed that you’d have to recreate everything still, but rather that we now have this option. And just to be clear, like because Brian was talking about that your segments and your calculate metrics have to be included in the project, like on the screen, in a table, in a visualization, or they won’t come over. If you have a bunch of calculated metrics or, or segments that you want to bring over and they’re not applied to a you know, to a table or whatever, just make a table in analytics and nobody analytics put them in there, just pop them in before you actually migrate. And then they’ll come over and you’ll have them. Because if you don’t add them, if they’re just sitting in the last rail still, they won’t come over as you migrate the project. I know we’ve got some, I know we’ve got a bunch of questions that have come through. I will say that, you know, since we didn’t get to all the questions, you guys, I will put am, I’m going to put a community discussion up. Yeah. You know, in the analytics community. So give me a day or two and we will answer all of your questions there. I will put a link to that since I crazy and I’ll put a link to that back here on this same page. So if you come back to this YouTube page, I’ll put a link to the to the community discussion and we’ll answer all of your questions there so that you don’t, you know, get left behind on those. And if you have more questions about that, you can put them in there as well. And we’ll answer those even if you have questions after this. So I’m sorry, again, that we didn’t get to all of the questions, but we will. So thank you so much for joining. Before we leave, we got one quick minute, Brian, for our last segment. We have to do it. Here it is for real. I’m sorry. No. Real quick and time traveling. You know, we’re. Starting to start over, Brian. Here we go. Go ahead. So those of you that spend some time traveling, whether it’s for work or pleasure, you know, my my initial tip was going to be, hey, you know, bring a binder clip or use your your hanger in the hotel closet to make sure your blinds are closed. But somebody really give that tip. I can’t believe it. So my second step is have a little bit of black tape or some little black stickies to cover up all those various doodad lights. Right. The coffeemaker, the the thermostat, the TV, remote, the TV all have these little bright buttons and your room is as bright as the moon sometimes when you’re trying to go to sleep in a hotel. But bring that tape, cover those up and you’ll get a better night’s sleep. And you could do all the special things you’re supposed to do on your trip. That’s a great idea. And hopefully in Vegas. I love it. I love it. Okay, awesome. Good. Unrelated. Cool to appreciate that. Brian. Well, Eric, Brian thank you guys so much for being here today, going through these things. I know that this will be really helpful to our customers as they, you know, move their data analysis over to C.J. And again, everybody, thanks to everybody that came and for everybody that’s watching this afterwards as well, we’ll be putting this up on experience as well. So thanks for joining us. And until next time, we will see you later. Thanks, everyone. Doug. Thanks, man. Thanks so.