Does Chrome’s SameSite cookie policy influence Piwik PRO tracking?

On February 4, 2020, Google will update a Chrome browser and introduce a new approach to cookies (the SameSite update). Website owners will need to label the third-party cookies. Otherwise, the third-party cookies won’t work in the Chrome browser.

Does the SameSite update influence your tracking? No, it doesn’t. Here’s why:

  • Piwik PRO uses the first-party cookies. They will be set in the Chrome browser as usual.
  • From an 11.0.0 version, we add a parameter SameSite=Strict to container cookies. The SameSite=Strict restricts cross-site sharing altogether, even between different domains that are owned by the same business. This means that our cookies are labeled with a parameter that informs browsers that they are not meant to be shared.
  • From an 11.0.2 version, we add a parameter SameSite=Lax to tracking cookies. The `SameSite=Lax` informs browsers that cookies are only set when the domain in the URL of the browser matches the domain of the cookie for the same-site requests or top-level navigation.
  • In versions earlier than 11.0.0, cookies will be set as usual. The only issue you may experience is that in the browser console, you may see warnings. We recommend upgrading your product to the latest version.

For more about Chrome’s SameSite cookie policy, read: “Cookies default to SameSite=Lax” and “Reject insecure SameSite=None cookies

Was this article helpful?

Technical Support

If you have any questions, drop us a line at

We’re happy to help!