Google has released their Chrome 80 update, which brings new restrictions on which sorts of cookies can be used in a third-party context. Enforcement of the new rules will begin the week of February 17th, so there’s just under two weeks left to prepare.
We posted about the update in January (read it here), but we wanted to provide some additional context and instructions for the partners who are hosting links on their websites and social properties.
How do I know if Chrome 80 will affect me?
Once enforcement begins, Chrome 80 will only allow cookies to be used in a third-party context (that is, everywhere except the Impact tracking servers) if they are marked as both “SameSite=none” and “secure”. We handled the SameSite bit on our end, but if you are hosting any Impact tracking links, you will need to review them to be sure that they are secure. In other words, you should make sure that your tracking links have an “s” after the “http”.
Note: We expect to release a hotfix the week of February 10 that will automatically redirect any HTTP tracking links to HTTPS, which means that your links will keep tracking no matter what. However, this will introduce a redirect which will in turn increase your links’ latency marginally. To ensure optimal load times for your tracking links, we still recommend that you make all your tracking links secure.
Some of My Links Are Not Secure — What Do I Do?
If you find any unsecure (http) tracking links, you just need to add an “s” to turn them into secure links. The quickest way to do this is to use your CMS’s global find and replace function, if it has one.
What Else Do I Need To Do?
Nothing! As long as your tracking links start with “https,” you’re good to go. If you have any questions, please reach out to firstname.lastname@example.org and we’ll help you out.