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

Coffee Break: Join us on Wednesday, April 5th at 10am PT to chat with Ben Gaines, Director of Product Management for Adobe Analytics. Ben will be online to answer your Analytics and Adobe Summit questions.

Apple’s recent ITP changes that affect AA/CNAME


Level 2



With the recent ITP update and impact on CNAME first party cookie (below is a reference info link),


Would like to see if Adobe have any roadmap to handle this?


Meanwhile, as a workaround, would like to explore to add some code to the web server and generate the ECID (on server side) and then send the cookie with ECID as part of the web server HTTP header. My understanding is that ITP will not touch those cookie in this scenario.


Would like to see if anyone have done something similar and can shed some lights here?






3 Replies



Hi @John_Man ,


If you have a CNAME and use the visitor ID service — your implementation would not be affected.

The s_ecid cookie is essentially used to restore values to the AMCV cookies (MID), which is the cookie Adobe will use to identify visitors.
It came as a response to the Safari ITP situation where client-side cookies are deleted every 7 days.

The AMCV cookie currently relies on the document.cookie API and is set via "client-side." Safari favors cookies that are set from a customer's server therefore it is affected by ITP 2.1.

When safari deletes the AMCV cookie, we can use the ECID cookie to create a new AMCV cookie with the same ID. In addition, the ecid cookie is only set on the domain that matches the tracking server.



Level 2
Hi HemanginiS, the link ref mentioned that "As part of the Big Sur updates, an s_ecid cookie set via CNAME is also held to a seven-day expiry."


Yes, that's correct. At present, s_ecid also has 7 day expiration in this case.