Expand my Community achievements bar.

SOLVED

Impact of Disabling DemDex Cookie

Avatar

Level 1

Hello - is it possible to disable the Demdex Cookie from firing and populating a UUID without breaking our ability to tie or measure users between our internal Experience Cloud tools (i.e. Adobe Analytics and Adobe Target)?  I understand this is not a traditional third party cookie, but I have some concerns with firing an ID that is being populated on both my domain and of domains that are not of my own.


Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

If you only have one domain, it should be less of an issue... The real power of the Visitor ID service is to stitch users across all domains owned by an organization.

 

So, basically, if you don't add the Visitor ID service, your implementation should just use the "old" s_vi identification on your one site.

View solution in original post

5 Replies

Avatar

Community Advisor

If you don't use the Demdex server, it would be like going back to the old method od setting first party s_vi cookies per domain.

 

If you have multiple domains, you won't be able to cross identify users between the sites, as each site will track the user with a unique id per domain.

Avatar

Level 1

Thanks Jennifer.  Does this mean that if we do not have multiple domains, then this won't be an issue for us?

Avatar

Correct answer by
Community Advisor

If you only have one domain, it should be less of an issue... The real power of the Visitor ID service is to stitch users across all domains owned by an organization.

 

So, basically, if you don't add the Visitor ID service, your implementation should just use the "old" s_vi identification on your one site.

Avatar

Level 1

Hello Apoly,

 

If i understand your question correctly then your concern is about 'demdex cookie/information is getting used by other domains'.

 

As per this document- https://experienceleague.adobe.com/docs/id-service/using/intro/id-request.html . Demdex services uses 'Adobe Organization ID', so if you do not own other domain then it will not have same 'Adobe Organization ID' as your domain. And eventually on both domain demdex cookie will work independently.

I would suggest to check this link- https://experienceleague.adobe.com/docs/id-service/using/intro/id-request.html, where Adobe team has explained how Demdex service call work for Same Domain, Cross Domain (other domains that you own), Cross domain (other domains that you do not own).

Avatar

Level 1

Thanks Abishek!  You are correct regarding my concern.  This article is helpful, I will review it with my team. 

What is tripping me up a bit is when you said "Demdex services uses 'Adobe Organization ID', so if you do not own other domain then it will not have same 'Adobe Organization ID' as your domain. And eventually on both domain demdex cookie will work independently."  I noticed as I was browsing around the internet on other site with Adobe Analytics that the demdexID given on my site was the same on another site.  This was quoted in the article on the last sentence "the demdex ID remains the same for this visitor because it’s contained in a third-party cookie and persists across different domains."  So this is expected behavior?