Reset MID/ECID and generate a new MID | Community
Skip to main content
ambikaTewari_ATCI
Community Advisor
ambikaTewari_ATCICommunity Advisor
Community Advisor
July 26, 2024
Solved

Reset MID/ECID and generate a new MID

  • July 26, 2024
  • 1 reply
  • 1311 views

Hi Team,

I was following this question :

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-data/ecid-reset/m-p/637393
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-questions/how-to-delete-reset-marketing-cloud-visitor-id/m-p/192887

 

I also need to delete the AMCV cookie (and this remove the mid/ecid) when user denies the consent and generate a new mid when user accepts the consent once again.

Through js code I'm able to delete the AMCV and when user accepts the consent a new mid is generated.
However when user denies and accepts the consent then first mid is triggerred again.

 

 

I could not delete the demdex cookie through js since it is a third party cookie. So wanted to check if this is possible to resent mid/ECID and generate a new MID even without deleting the demdex cookie ?
if we manage to delete both demdex + AMCV then only new mid will be generated everytime, however if demdex exists then same mid could be generated even if we delete AMCV ?


    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by bjoern__koth

    Hi @ambikatewari_atci 

    I think that is essentially what the fender cookie is for, deriving the same ECID from  the demdex cookie, using your AdobeOrgID. The third party cookie was introduced to solve exactly this issue. If you own domainA.com and domainB.com, the cookie storing the user's ECID on domainA will not be readable on domainB and without the demdex call, sending this 3rd party cookie to Adobe and in return receiving the ECID, you would not be able to reidentify the user (unless you are using the appendVisitorIDsTo functionality to append the IDs to link clicks. This will not work for direct typeins of the domains URL though)

     

    so yeah, it basically does what it was designed to. I have not come across a different way to reset it. Deleting the cookie will obviously also inflate your visitor count 

    1 reply

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    July 27, 2024

    Hi @ambikatewari_atci 

    I think that is essentially what the fender cookie is for, deriving the same ECID from  the demdex cookie, using your AdobeOrgID. The third party cookie was introduced to solve exactly this issue. If you own domainA.com and domainB.com, the cookie storing the user's ECID on domainA will not be readable on domainB and without the demdex call, sending this 3rd party cookie to Adobe and in return receiving the ECID, you would not be able to reidentify the user (unless you are using the appendVisitorIDsTo functionality to append the IDs to link clicks. This will not work for direct typeins of the domains URL though)

     

    so yeah, it basically does what it was designed to. I have not come across a different way to reset it. Deleting the cookie will obviously also inflate your visitor count 

    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...