Doubleclick, Amazon-Adsystems and Flashtalking cookies suddenly listed under demdex

[weobvWEBVweibfv]

Hi,

today three cookies suddenly appeared and are listed under https://xyz.demdex.net as you can see in the Chrome console screenshot below. The new cookies are:

- IDE (.doubleclick.net)

- ad-id (.amazon-adsystems.com)

- ad-privacy (.amazon-adsystems.com)

- flashtalkingad1 (.flashtalking.com)

I didn't change any settings in AAM and these cookies haven't been used on the site before. Any idea where they are coming from and if they are at all related to AAM?

Thank you very much!

[dhwoolsey]

Can you help me with what you mean by "under demdex?" These cookies are not listed as being set by the demdex.net domain, so I'm not sure I follow what you mean by "under demdex". It's possible that these are coming as a result of newly enabled ID syncs. Did you ask customer support to setup any new destinations recently? Do you have an organization ID so we can look this up for this organization? Or a URL where we can see this? 

[weobvWEBVweibfv]

Hi @dhwoolsey ,

thank you for your reply!

The URL is https://www.mcdonalds.com/de/de-de.html

and https://mcdonaldsprom.demdex.net 

These destinations are set up in AAM, but they were set up years ago.and we didn't have these cookies on the website before. No changes or new setups have been made recently.

With "listed under demdex" I mean the are listed like this in chrome developer console, so they seem to be related to AAM.

[dhwoolsey]

Thanks for the additional info. I was able to check your account on the backend and I'm seeing destinations for Flashtalking, Amazon Advertising, and Google 360. The cookies you are seeing are a result of the ID syncs that we enabled as part of these destinations. At some point in time, when these destinations were set up, these ID syncs were enabled. I can't speak to why you never noticed them before, but these have likely been active for a long time. Without them, your destinations wouldn't work very well.

If you open an incognito browser, visit your page as a new user, and then use the developer tools to look at the 2nd call to ID service (the 2nd call to dpm.demdex.net/id?), you'll see in the response the ID sync URLs that we fire. Id syncs work by our destination iframe calling these URLs, passing them our AAM UUID, and then them doing a 302 redirect back to demdex.net where they pass us their ID. It is possible that these partners updated the actions their servers do and when we make a call to them, they are dropping net new cookies. That's just a guess, though. Point is, these are working as designed and I can't really speak as to why you haven't noticed them before. If you need more information, go ahead and open a ticket with Customer Care and we'll get those questions answered. 

[weobvWEBVweibfv]

Thank you for the explanation!

I just tried to open a ticket, but it seems AAM is not linked to my account and is not shown under products although it's the same email address. Do you know, how I can fix this?https://experienceleague.adobe.com/?support-solution=General&support-tab=open-ticket&lang=en#support

I also sent an email last week to amsupport@adobe.com but didn't get a reply.

[dhwoolsey]

Yeah, not sure what's going on there. Is there another user in the org that could log it under something like Analytics or AEP and just explain in the ticket that it's an AAM issue? If that's possible, then the Service Desk should be able to re-label the ticket and route to the correct team. The email doesn't work anymore since we went to the Admin Console so you will need to log it via that method.