This may really be a bug report rather than a question, please refer me to the correct place if this is not it.
The Chrome developer console issued the following warning:
A cookie associated with a cross-site resource at http://mixpanel.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032
I was looking into how to add a "SameSite=None" attribute to the MixPanel cookie, but quickly realized that maybe this shouldn't be my problem.
Should I adjust the cookie to have the new attribute myself, or is that MixPanel's problem?
Specifics: Windows 10, Chrome version 77.0.3865.90, my website if it's relevant.
Best answer by fredl
It looks like what you're seeing is the result of your own mixpanel.com cookie being sent along with the lib's tracking requests to api.mixpanel.com, i.e. you're seeing this because you're a mixpanel.com user, but your users won't see it and it won't affect your app's own tracking (you can test on incognito). Hope this helps!