In Chrome 80 the following change will become default behavior: https://www.chromestatus.com/feature/5088147346030592

===

Evolv cookie filters generally involve our third party resource (Evolv snippet) checking the value of a first party cookie to determine if a user should be entered into an experiment. Starting in Chrome 80, Evolv will not be able to read first party cookies by default. In order to allow Evolv to read these cookies, they have to be set with SameSite=None and Secure.

Alternately, Evolv offers a User Attributes filter that uses the window.AscendUser object value to determine if a user should be entered into an experiment. This object can be populated by first party JS with values from the first party cookies. Once this JS object is populated, third party scripts can access the values as if they could read the first party cookie directly.

https://help.evolv.ai/en/articles/2653619-user-attributes

Did this answer your question?