Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

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

Jones2222
Level 1
Level 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

1 Accepted Solution
Varun_Kalra
Correct answer by
Community Advisor
Community Advisor

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

View solution in original post

2 Replies
shweta_singh
Employee
Employee

Hi @Jones2222 ,

 

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

 

Regards,

Shweta

Varun_Kalra
Correct answer by
Community Advisor
Community Advisor

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

View solution in original post