A cookie associated with a cross-site resource at https://app-sjf.marketo.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.
Since this warning is only applicable to third party cookies, are there any fixes for this planned on the Marketo side?
cc: Sanford Whiteman
Solved! Go to Solution.
Got it. Thanks for the quick reply Sanford.
Just wanted to confirm and be pro-active about this, to not cause any interruptions in Marketo tracking once this version goes live and wanted to make sure that there's nothing to be fixed/done from either the Website's or Marketo's end.
I have the same issue for our Marketo Landing page. To solve this we need to add
Can you please let me know where I need to put this in Marketo?
There's no equivalent. The Munchkin cookie can't be HttpOnly.
If the Marketo cookies are missing an attribute required by Chrome, doesn't that mean once the future Chrome release is out the cookies will NOT be delivered? Shouldn't Marketo add in the samesite attribute to avoid blocking the cookie if Chrome states it is required?
The point I made there is that a minority of Marketo LP domains are secure, so it's not possible to mark the cookies as secure.
For Future Googlers
The missing link at the end of @SanfordWhiteman comment ("It's not simple like that, see my responses at") is the following:
You can see it for yourself via the browser inspector: there is an empty <a> tag.