Configuring General Settings in the Launch Analytics Extension

Hey everybody, this is Doug. In this video I wanna show you how to configure the general settings in the Adobe Analytics extension in Launch by Adobe. So, we’re here in the extension, I’m gonna go to the general settings, and there’s a few different things here that we wanna talk about. The first one is this check box to enable EU Compliance for Adobe Analytics. So, this allows you to enable or disable tracking, based on your EU Compliance cookie. And so, if we set that it has a tracking cookie name here, and if this is set, it’s going to look for the existence of this cookie. Now, if this cookie exists and is set to true, then it will allow Adobe Analytics to run normally. If this cookie does not exist or if it is set to anything other than true, for example, false then, it will not run. So Adobe Analytics will not track. And so it’s up to you to make sure that this cookie is set to true or false, based on, again, the user oping in or out. So, that is one thing that you can do in this general section. The next one is the character set. So, if you are going to send in any characters that are non-ASCII, then you’ll need to set this to the correct character set. Okay, so it’s gonna decide how the image request, or the hit, is encoded.

Next, we’ll look at the currency code here. So, you’re gonna wanna set this to the currency that you want to be stored in the data base. There will be options for reporting via different currencies but, what currency do you want stored on the back end, and so, you can set that here.

And last but not least, the tracking server, and the SSL tracking server. So the tracking server is basically the name of the end point, or the data collection server that you are going to send your analytics hit to. And so, if you have been already using Adobe Analytics and you are now moving to Launch, from DTM, or from Page Code, etc…, you are going to want to use the same tracking server and the same SSL tracking server that you have been using all along. That would be the first and most important thing. So, let me say that again, if this is not a new implementation, if this is a migration from DTM, or a migration form Page Code to using Launch, please make sure that you are using the same tracking server that you have been using before. If you don’t, then you’re gonna have a potential cliff of visitors, in other words, everybody will look like a new visitor, and so your numbers, your analytics will look goofy and everybody will wonder what’s going on. So, that’s the number one thing. So, if this is a new implementation of Adobe Analytics, then, it’s not quite so important that I have to be all, you know, crazy about it like that with you.

So, if you are using a CNAME, or if you’re used to using a CNAME, in order to use a first party domain, then that would probably be the best. Now, your tracking is still gonna be loaded into a first party cookie with Adobe Analytics. But, if you’re using a CNAME, then that’s gonna go into Adobe Analytics in the request header, which potentially is a better idea moving forward, as the internet has different tracking restrictions, and different browsers have tracking restriction, etc… Then, You’re probably safest with using a CNAME, being sent in, in order to make sure that everybody gets tracked correctly. But, even if you’re not using a CNAME, then you can you either do one of two things, you can leave this blank, and it will use a 207.net domain, or you can do, what I like to do, which is another one, that we use, I’ll use TMD for our Tech Marking Demo site, and then it is .sc.omtrdc.net, and this is the other domain that you can use so that data will come into Adobe Analytics, and go into your reports suites. So, in any case, you can also look up tracking server in our documentation and get more information there. Then, you can copy and paste things from there as well. And, if you’re using SSL, then, it would be basically the same as this, but tmd.ssl.sc.omtrdc.net for example. Or again, if you’re using a CNAME, then you can use that SSLC name that should be mapped to yourname.ssl.sc.omtrdc.net. In any case, I hope this helps, and good luck.