Before you implement Analytics in tags, you need some supporting documents, and you need to set up a few things in both Analytics and tags. This video covers these things.
Launch is now tags
Hey everybody, this is Doug. In this video I want to talk to you about some of the things you’ll need to do to prepare to use Launch, and then some of things you’ll need to do in Launch to prepare to implement analytics. So lets start with before we get into Launch. Now first of all, I’m hoping that you have access to Launch. When you log in to the experience cloud, you can go over to the solution switcher and click on that, and then go to activation, and inside activation there’ll be a link to Launch. So if you have access to Launch, you’ll be able to click it there. If you don’t, then you’ll need to talk to your Admin and make sure they grant you access to Launch. Let me also say that, at this point I’m hoping that you have watched the videos or done some other research to get to know Launch. I’m not going to go over all of the different aspects of Launch. I’m not going to go over all the features of Launch. But I am going to show you how you can quickly get up and running with analytics on a basic analytics implementation through Launch. Okay. Now a couple other things you’ll want to gather. If I jump over here to Accel, and I have my BRD and SDR and so. If you have your Business Requirements Document and you have your Solution Design here, then hopefully you will have a good idea of some of the things that you’ll need to do once you get into Launch. Right? You’ll need some kind of a check-list. Some kind of a what do I do first, or second, or third. And the SDR can act as that kind of a check-list for you. I have only a few things that I have to setup in Launch in this basic example. Yours might be a lot more extensive, but you can see over here in column G that I have written down some the things I’m going to need to do. I’m going to need to setup a default page load rule, and set these variables up in there. I have a couple other rules I’m going to need to do, and I’m going to need to configure analytics. So this will act as good check-list to make sure that I have everything implemented. Okay, so have that handy. If I go back, then another thing you’ll want to know of course is your reports we’d ID. So here in analytics, again if you go to Admin and Report Suites you’ll be able to see the Report Suites that you have created, and I hope by this time you’ve also created at least a Dev Report Suite for your site. So you’re going to need to know this Report Suite ID. Now the good thing is, we won’t have to actually type it. We’ll be able to use a drop down, and it’ll be there, and we’ll be able to select it. But we do still need to know which one it is. Okay, lets dive back into Launch, and we’re going to get started. We’re going to create a new property, if you haven’t already done this for you site. Maybe you already did when you were learning about Launch, and that’s great, but I haven’t yet for this one. So I’m going to put in Geometrixx Clothiers.
And this is my property. It is a web property, and you can see I have it over here, and I’m going to grab this domain that I have it on, and put it right into here. Okay. And that really only matters if you have multiple domains. It’ll fill some check boxes in Launch. So if you only have one domain, I mean don’t worry about this too much. Just put it in like that, and you need to worry about it. So going to hit save.
Okay, and here we are. So I’ll click into that. Okay, a couple things we’re goin to do to get this all setup and ready to go, and that is. First, I just want to show you the Hosts. We’re not going to have to do anything here. If I click on that it shows us that we have managed by Adobe, and that’s through occumy, and we’re going to leave it like that. There is an opportunity for you to host that yourself. Meaning, and when I say that, I mean the library files and the Launch files, but we’re going to leave it hosted on occumy.
Now if you go to environments. You’ll see that there has automatically been setup for you. These environments Production, Staging, and Development. So what we need to do, is we need to embed the development embed code on our site. So, we are going to go over to this install button here. Open that up. We’re going to click on this icon over here to copy the embed code. And as you can see this just needs to be pasted inside the Head Tag of your document. So I’m going to jump over to a text editor here where I have one of my files open. So this is just the Index page of that Demo Site, and I am here at the end of my Head Section. Now I’m going to put this at the bottom of my Head Section. And the reason why I’m goin to do that, is because above here I have a data Layer. And we’ll talk about a Data Layer in another video. But I definitely want to have my embed code after that, so that this code, the things in my Data Layer can be used and will be ready for me in Launch. So I will paste it in there, and there’s my Launch code. Now again, this is the Development code, and so once we are done Developing, then we will want to change this code to Staging, and change it to Production as we get going. So even though I’m hard coding this in here, I’m sure you’ll have a better way to make sure that is included on all of your pages. So I’m going to save that, and I’m not going to make you watch me upload it to my server, but just know that I will be making sure that is on all the pages of my site. So lets go back to Launch.
Okay, and I’ve done that step. So I’ve done Hosts. We’ve done the Environments. We’ve put the embed code on the page, and I want to jump in to Extensions for just a minute here. And you’ll see they core extension is already there. You don’t need to configure anything there, it’s already done. We’ll go to the catalog, and I want the Experience Cloud ID Service. There it is. So I click install. So you absolutely want to install the Experience Cloud ID Services Extension for all of your sites that you’re ever doing through Launch. And so, you should just have to do that much. I mean it should have your org ID here for you. You don’t really have to do anything else. Especially in this basic implementation. So I’m going to go ahead and just save that, and we can move on. Now one more thing we want to do before we install the Analytics Extension and get going on all those things. And that is, we need to setup a library that we can publish. Okay, and you’ll see up here we have Working Library. And if I say “select an option”. I can say New Library, so I can click there. Or I can go into this Publishing Tab, and add a new Library. It’s all the same. Its taken me into the Create New Library, and I will call it “Initial Setup”. You can see I’ve done this before. And we have to mount that to our environment, which is a Development Environment. Now we’re going to go down here, and we’re going to say Add All Changed Resources.
And that will add just that extension that I just added, the Experience Cloud ID Service, of course the Core Extension as well. And that’s really it. And now I’m going to go up here and say Save, and Build for Development. And that will bring me back here, and you’ll see that it’s spinning until it’s done. Okay good, that should be relatively quick. And now I can also select, as a working Library, that Initial Setup. And so now I won’t have to come back into the Publishing Area every time I make a change on this property. I’ll be able to save it, and build it to my Working Library. So those are the main things that we have to do to get setup and ready to go. I hope that was helpful, and they followed along. And after this we’ll go ahead and get going the Analytics Extension, and good luck.