Some cookies are misusing the recommended “SameSite“ attribute

Hi @mayur1234,

Thanks for reaching out. Site Kit doesn’t have any integrated CORs or cookie related features however many cookie related plugins or hosting features may have configurations that can impact Site Kit or third party snippet behavior.

If you’re not sure how you’ve defined any CORs policy, or privacy/cookie configurations you can help determine any plugin related feature by using the Health Check & Troubleshooting plugin. We have instructions on the plugin website in relation to this.
https://sitekit.withgoogle.com/documentation/troubleshooting/using-troubleshooting-mode/

I’m also happy to check your set up if you wish to share your Site Health information. Note that we can only assist with Site Kit queries, so any checks I perform will be for possible plugins that may allow for CORs or cookie related changes.

Hi,

Thanks for your Reply,

I send you screenshot of Site Health Information Kindly check below Link. Thanks for the help about my issue.

Site Health

Hi @mayur1234,

Thanks for sharing a screenshot of your Site Health status. This differs from your the Site Health information requested (Tools > Site Health > info > Copy site info to clipboard)

You can use this form to share your Site Health information privately if preferred.

Hi,

I send the information via your form please check the same. Thanks

Many thanks for sharing your Site Health information. I can see you have the HTTP Headers plugin active. It’s possible you have some CORs/samesite policy active from here, which could be impacting any Tag Manager or other Google service scripts from executing on your site. You can check this by temporarily disabling this before checking for the same browser console errors once more.

As you also have the Health Check & Troubleshooting plugin active you could check for the same error with only Site Kit active, while using troubleshooting mode. You’ll find details on this below:
https://sitekit.withgoogle.com/documentation/troubleshooting/using-troubleshooting-mode/

I’ve also checked your site at present and I don’t see any such console errors on the front end of your site, so maybe the issue no longer occurs. I ran a check on your site using the tagassistant.google.com service and I also see both your Google Analytics tags firing as expected. You can perform the same check if you wish.

Let me know if you run into the same error again from your side, and if so how you get on with the suggested troubleshooting check above.

Hi,

Thanks for Reply,

I Installed HTTP header plugin Today after see this issue but my problem is not solved when I activate this plugin and apply samesiteorigin “none”, secure I see some solution they said analytics tag means any java script not covered by this plugin so you have to apply manually for javascript.

Now I disable HTTP plugin and check again there have show same error as below.

Some cookies are misusing the recommended “SameSite“ attribute 5
Cookie “_ga_341PPGRYGS” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:150:1046
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:150:1046
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:35:486
Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:35:486
Cookie “cmdShowOfferCookie” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite a485157d6986d3a81b67898ac68f0c09.js:5

Thanks for sharing these additional insights. The browser console warnings you’re seeing are from within Firefox, and they are just a warning for future behavior of the SameSite attribute.

As mentioned above, your Analytics scripts are firing as expected, with no action required.

Let me know if you have any questions with the above. Note that you can define your own SameSite rules using a third party plugin if you wish, with these plugins typically having their own documentation to assist you.

Hi James,

Thanks For the clarificatin and Thanks for your kind help to resolve this issue.