SameSite by Default Cookies: What Publishers Need to Know

In February 2020, Google announced that it would be making a major change to the way cookies work. This change, known as SameSite by default cookies, is designed to improve user privacy and security.

SameSite cookies are a type of cookie that can be used to control how cookies are shared between websites. There are three different SameSite values:

• SameSite=Strict: Cookies with the SameSite=Strict value can only be sent to the website that set them.

• SameSite=Lax: Cookies with the SameSite=Lax value can be sent to the website that set them and to top-level navigation requests (such as when a user clicks on a link to another website).

• SameSite=None: Cookies with the SameSite=None value can be sent to any website.

Prior to the SameSite by default update, cookies were set to SameSite=None by default. This meant that cookies could be shared between websites, even if the user was not aware of it.

However, this also meant that cookies could be used to track users across multiple websites without their consent. This is a privacy concern, and it’s one of the reasons why Google is making the SameSite by default update.

Why is SameSite by default important?

The SameSite by default update is important because it will help to protect user privacy and security. By setting cookies to SameSite=Lax by default, Google is making it more difficult for websites to track users across multiple websites without their consent.This is a good thing for users, because it gives them more control over their privacy. It’s also a good thing for publishers, because it will help to build trust with their users.

How can publishers prepare for the SameSite by default update?

There are a few things that publishers can do to prepare for the SameSite by default update:

• Audit your cookies: The first step is to audit your cookies to see which ones need to be set to SameSite=None. This is important because cookies that are set to SameSite=None may not work properly after the update.

• Update your cookie policies: You should also update your cookie policies to reflect the changes that Google is making. This will help to inform your users about how their data will be used.

• Test your website: Once you have updated your cookies and cookie policies, you should test your website to make sure that everything is working properly. This includes testing your website on all major browsers.

The SameSite by default update is a major change to the way cookies work. However, it’s an important change that will help to protect user privacy and security. Publishers can prepare for the update by auditing their cookies, updating their cookie policies, and testing their website.