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

[#1]

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

[#2 · Accepted solution]

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

[#3]

Hi @Jones2222 ,

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

Regards,

Shweta