Highlighted

Cookie and profiles

Rookie Contributor
Hi, We are using utag.loader.RC and utag.loader.SC calls to load and store cookies in .js extensions. The same js extension is re-used for multiple profiles. Are cookies profile specific? Or are they handled since the request would come from different domains associated with different profiles? Otherwise do we need to handle this in the Javascript code say by creating profile specific cookies? Or do we need to maintain separate js extensions for profiles. If cookies are not profile specific by default, what is the best practice to follow? Thanks, Sriram
3 REPLIES 3
Highlighted

Cookie and profiles

Tealium Employee
Technically: Cookies are not profile specific, but they are domain specific. Since you are using the Tealium method of setting cookies, they get set 1st party. So in a sense they become profile specific since the cookies are set on the current domain (1st party). Non-technically: it's not something you should have to worry about. You can't set 3rd party cookies that can be read by other domains. The RC and SC functions only read and set cookies on the current domain.
Highlighted

Cookie and profiles

Rookie Contributor
Thanks Dan. I was wondering if the dev/qa/prod environments would get information off the same cookie. Since they all belong to different domains in our case, there should be no problem.
Highlighted

Cookie and profiles

Employee Emeritus
The most common reason for the cookies being shared in a scenario like this is if they cookies are set at the domain level, but your environments only differ by subdomain.