ID Service, 1st-party aam_uuid cookie and AAM SSF | Community
Skip to main content
Jones2222
Jones2222
October 2, 2020
Solved

ID Service, 1st-party aam_uuid cookie and AAM SSF

  • October 2, 2020
  • 2 replies
  • 2589 views

Hi there,

 

We're wondering about the benefits of switching to 1st-party aam_uuid cookie if we're already using the visitor ID service (with CNAMEs) and have server-side-forwarding enabled.

 

Does anybody knows more?

 

Thanks in advance and best,

Jones

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 Varun_Kalra

Hi Jones,

 

Since aam_uuid gets written as a first party cookie but by third party domain, so it's in third party context, and Safari should delete that in 24 hours. But, with cname implemented for ID service, there is no harm in keeping aam_uuid as well.

Just make sure that you have s_ecid cookie being set as first party:

https://docs.adobe.com/content/help/en/id-service/using/reference/ecid-library-methods.html

 

Thanks,

Varun Kalra

2 replies

S
Adobe Employee
shweta_singhAdobe Employee
Adobe Employee
October 7, 2020

Hi @jones2222 ,

 

One advantage would be that, it will mitigate the impact of IT 2.2 in safari specifically.

 

Regards,

Shweta

Varun_Kalra
Varun_KalraAccepted solution
Level 9
October 19, 2020

Hi Jones,

 

Since aam_uuid gets written as a first party cookie but by third party domain, so it's in third party context, and Safari should delete that in 24 hours. But, with cname implemented for ID service, there is no harm in keeping aam_uuid as well.

Just make sure that you have s_ecid cookie being set as first party:

https://docs.adobe.com/content/help/en/id-service/using/reference/ecid-library-methods.html

 

Thanks,

Varun Kalra

    Terms & ConditionsAccessibility statement

    Loading footer...