Configuring Cookie Settings in the Launch Analytics Extension

Last update: 2023-06-05
  • Created for:
  • Beginner

If you are just getting started with Experience Platform Launch, and the Adobe Analytics extension, this video can help you understand if and how to set the cookie settings in the Analytics extension.


Hey everybody, this is Doug, in this video I wanna talk about the cookies section of the configuration of the Analytics extension in Launch. So when you are first setting up Launch and you’re setting up the Analytics extension you’re gonna want to go down through these configuration items and get them all set up correctly and I wanna talk about the cookies section now. So there are several fields in here that you can set and the first thing that I wanna say is that if you are migrating from DTM into Launch, or from a page base implementation into Launch the best thing you can do is to just set these the same as they were. So keep these settings the same. An example of that would be namespace, if you have a visitor namespace that you have from before and if you were to change it, then all of your visitors are gonna look like new visitors, it’s what we call visitor cliffing, and you don’t want that so, if you are migrating from another implementation again DTM or page based into Launch then go ahead and set these all the same. Okay, now if it’s a new implementation then mostly you won’t need to set any of these and you can just leave them all blank and default. I know that there are some people who want to set a custom visitor ID and I suppose you can do that but if you have any other solutions besides Analytics you are not gonna wanna do that because it will effectively kill any integration that you have between Analytics and the other solutions in the Experience Cloud. So you’re not gonna wanna set that and you don’t need to set it, what you should really do is just use the Experience Cloud ID service extension and you’ll be good to go. Now the exception to not setting anything here would be if you have a domain that has more than two periods in it when you have the www at the beginning. So for example, if your domain is just or in other words, let me go back here to the beginning and, this is what we would call two domain periods and this is the default and you would not need to put anything in here because the actual value that would automatically be placed in here is a two. And that’s what that means. However if your domain is something like for example, where when you put the www at the beginning you actually have three dots in here then you do need to put a three in here. So again if you just have a dot com or dot org or anything else, especially throughout the world if you have another suffix there then you are fine as long as it doesn’t have this double dot co dot jp, or dot co dot au or whatever right? So if you do have this kind of a set up then you’re gonna want to put a three in the domain periods and if you’re gonna do that then you should also put a three in the first party domain periods. Now if you wanna read a little bit more about then you can go up to the help and you can look for domain periods and it will bring you to this area in the documentation you can read about domain periods and first party domain periods and these will actually link out as well to some additional documentation which you can read about setting these cookie domain periods and first party cookie domain periods. So in any case if you wanna read a little bit more about it it is there available for you. But at the end of the day, if you do not have the dot co, dot something at the end then you can leave this blank, and if you do have that extra piece at the end like that then you’ll want to set this to three. And other than that, that’s all you really need, I hope that was helpful and good luck.

On this page