Expand my Community achievements bar.

Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
SOLVED

Is any actions required to be done through Adobe DTM/Launch for Chrome 80 SameSite cookie?

Avatar

Level 1

Could you please help us with sameSite cookie policy regards to chrome 80 release and changes required on Adobe Analytics implementation:

 1. Will the 1st party analytics implementation not affected? 

2. Is there any changes through DTM/Adobe Launch needs to be done from the company side?

3. Will "overwriteCrossDomainMCIDAndAID: true" have any impact? Reference

4. what is the update made from Adobe Analytic's server end? Details please. Reference

 

Thanks,

 

Topics

 
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

When you have a First Party cookie implementation -

1. Looks relatively safe. Tough Adobe Analytics implementations that use third-party data collection and do not use the Experience Cloud Identity Service (ECID) may see increase in new visitor (which otherwise tracked as repeat). It is suggested to keep and eye on this behaviour. 

2. All Adobe cookie updates are handled via Adobe servers and Adobe has updated their edge servers to set the appropriate cookie attributes. Adobe has released server-side updates to set their third-party cookies with the appropriate attributes. No JavaScript updates (DTM/Launch) are required for your sites. 

3. It has a positive impact to identify visitor across domain and platform. See use cases in your reference doc.

4. Answered in #2

 

In case if you are using third party cookie implementation and do not use ECID - 

1. Should move to ECID or First party cookie implementation if not already.

2. May need to update some libraries.

3. It has a positive impact to identify visitor across domain and platform. See use cases in your reference doc.

4. All Adobe cookie updates are handled via Adobe servers and Adobe has updated their edge servers to set the appropriate cookie attributes. Adobe has released server-side updates to set their third-party cookies with the appropriate attributes. No JavaScript updates are required for your sites.

Thanks!

Asheesh

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

When you have a First Party cookie implementation -

1. Looks relatively safe. Tough Adobe Analytics implementations that use third-party data collection and do not use the Experience Cloud Identity Service (ECID) may see increase in new visitor (which otherwise tracked as repeat). It is suggested to keep and eye on this behaviour. 

2. All Adobe cookie updates are handled via Adobe servers and Adobe has updated their edge servers to set the appropriate cookie attributes. Adobe has released server-side updates to set their third-party cookies with the appropriate attributes. No JavaScript updates (DTM/Launch) are required for your sites. 

3. It has a positive impact to identify visitor across domain and platform. See use cases in your reference doc.

4. Answered in #2

 

In case if you are using third party cookie implementation and do not use ECID - 

1. Should move to ECID or First party cookie implementation if not already.

2. May need to update some libraries.

3. It has a positive impact to identify visitor across domain and platform. See use cases in your reference doc.

4. All Adobe cookie updates are handled via Adobe servers and Adobe has updated their edge servers to set the appropriate cookie attributes. Adobe has released server-side updates to set their third-party cookies with the appropriate attributes. No JavaScript updates are required for your sites.

Thanks!

Asheesh