What is Happening and Why?
On February 4, 2020, Google Chrome is changing the security around the use of third-party cookies. First of all, what are third-party cookies? A cookie is considered third-party if it has a different domain from the main website. For example, if the domain is “fusionSpan.com” and Pardot (a marketing automation tool) is using a cookie to track website visits, that cookie would be considered a third-party cookie since it was set by Pardot, a “third-party.” Third-party cookies may also be stored as a result of a user’s interaction with chatbots, buttons, forms, etc.
With the new update from Google Chrome, third-party cookie tracking will not work unless updates are configured.
How Should My Organization Prepare for this Release?
Your organization’s webmaster will have to update the website to designate cookies for third-party access. Specifically, the “SameSite=None;” and “Secure” attributes will need to be present. See this article from Google Chrome for more technical details. In addition, your website will need to use HTTPS, which provides encryption between the web server and your browser.
If you use:
- Pardot, you will need to add the new SameSite attribute and ensure that the tracker domain being used is SSL-enabled.
- Marketing Cloud, Salesforce is working within the application to ensure this change does not affect website tracking for Marketing Cloud cookies. Updates to Marketing Cloud will be effective no later than February 7, 2020.
- HubSpot, you will need to add the SameSite attribute and ensure you are using an SSL-enabled domain.
- Google Analytics, you don’t need to do anything because these are considered first-party cookies, not third-party cookies.