Hey @edthenet , @nateangell , @tinyfly , @geekbleek , @seanvarnham, @eslpics, @kriswen and everyone,
Just an update here!
I have checked in with our team and we’d first like to clarify that the cookies set by HubSpot analytics scripts do now have the SameSite flag set (and have since February). We would not expect users to be seeing that chrome warning specifically about the js.hs-analytics at this point.
The likely root cause here is that users are seeing warnings referring to either hubspot.com or app.hubspot.com related to HubSpot app cookies (such as login/auth cookies which a user would see on their own HubSpot website if they’re logged into HubSpot in that same browser) or possibly cookies related to HubSpot API requests from assets they’ve embedded on their website.
Having said that, HubSpot analytics passes the values we need as query parameters on requests, so because our tracking doesn’t expect the cookie to be present in the header this does not affect our tracking functionality.
Additionally, I’d also like to suggest for you to try loading your website incognito to confirm if you still see those HubSpot warnings or not. If you do not see them in incognito, this can helps confirm that they’re related to being logged into HubSpot, and not related to the website itself.
Do let me know if there’s any further concerns. I’d be happy to address them 