Configure library management for the Analytics extension

Learn about the library management configuration options for the Analytics extension in Experience Platform tags. This video also covers selecting report suites for data collection. For detailed documentation, see Adobe Analytics extension overview.

Hey everybody, this is Doug. In this video, I want to talk about the configuration of the Library Management section in the Adobe Analytics extension. So we are here in Adobe Experience Platform tags, and we are in our tag properties, and we’ve gone in, we’ve created this Luma App Measurement property. This is based on a Luma site you can see over here that we’re implementing through tags, and we’ve named it Luma App Measurement because what we’re talking about here is the AppMeasurement.js type implementation as opposed to the newer Web SDK implementation. We’re not talking about the Web SDK here, we’re talking about the App Measurement implementation where we’re using Adobe Analytics extension. So I’ve already added it, but I’m going to select it because you can configure it and reconfigure it anytime you want. I’m going to jump into Configure. This brings it up, and you can see here that it has this Library Management section even already opened for me, and you can collapse that and see that there are several sections. We’re just going to talk about this section for a minute. So I have talked about this a little bit already in another video, so hopefully this isn’t too much overlap for you if you saw the other video that I created about a basic overall configuration. In any case, in Library Management there’s really just two things to think about, and that is, number one, which of these radio buttons, this one that is selected here, or these other radio buttons should you select, and then we’ll talk about report suites for a minute. In most cases, you are going to want to let tags manage the library for you. So this selected one right there. You can see some of these other ones where you can use the library already installed on the page. That’s very rare that you would have a library already installed on the page, and this would be some kind of a secondary implementation. Very rare. Loading the library from a custom URL. So instead of actually using the embed code here in the environments tab over here, or this section, loading that library from a custom URL could be possible that you’re wanting to do this, but again, pretty rare. And then the last thing, let me provide custom library code, and if you select that, then it opens the editor, and then you paste the code in there, etc. Now you used to have to do this actually quite a while ago now. If you were going to forward the data from Adobe Analytics to Adobe Audience Manager, but you can see down here that’s all taken care of. Down here where you will have that data forwarded, again with this app measurement implementation. So once again, very rare that you would ever need to or want to have this custom code and put it in there. Really, really no need to do that anymore. So we will leave it on, manage the library for me, again in the vast majority of cases. Now, report suites here, you can see I’ve already put in a report suite here and I’ve put in the same one. This dev report suite that I’ve created, and you can see as you do this dropdown, you’ll have all of your report suites that have been created. I have a ton in here, it’s just a demo site. You probably won’t have that many. Maybe you do, but you might not. In any case, I’ve done this because I’m just starting development. So I’m putting this same development report suite ID in each of these, the development, the staging and the production fields here, because I do have to put something in there. You can create your staging report suite and your production report suite now and put them in here and that’s fine, that’s great. But the only downside of that is whenever you make a change to your development report suite, you say, maybe I need to add a variable or I want to change the name of this and the settings or a hundred other things like that that you’re going to do as you do the development and the implementation, you’re going to have to go ahead and do those in three different report suites if you’ve already created them. Instead, what I suggest is at least initially, you just have a dev report suite, you put it in all three sections here, and then when you’re done with your at least initial development, you’ve done the majority of your initial development, then create a new staging report suite copied from the developer report suite and the same for production. Create a new production report suite, which is a copy of the development report suite, and that way you do have different report suites. And then when you know, once you’ve done that, then of course you can go ahead and select it just by going in and changing it. And I’ve done that and here’s the production one. Oh, that’s mobile. That’s not what I mean right here. Retail. Web retail prod one. So that’s the production report suite that I want here. Once I’ve kind of done this development and for here, I want to do the staging one, you know, just put the stage one right there. So you want to end up with, you know, a dev report suite, a stage report suite and a production report suite so that you don’t, you know, muddy the data in production report suite with development data, you know, and vice versa. So anyway, that’s kind of the way that I suggest that you do this. I hope that makes sense and good luck.