Skai Customers, Are You Worried About Google Phasing Out Third-Party Cookies? Don’t Be. You Are Already Compliant

Google is improving its privacy and security protection for its users which has left many marketers wondering and worried about how it will impact standard business practices, particularly when it comes to third-party cookies. 

The good news for Skai clients is that conversion tracking is already compliant to the new way that Google will be treating third-party cookies. 

The Google third-party cookies announcement

As part of its release of Chrome 80, Google will start enabling users to clear all cross-site cookies and instead leave single domain cookies in order to preserve their login and settings configurations. As reported in the Skai blog post, Q&A with Skai’s Chief Product Officer on the Cookieless Future of Marketing,

“While popular browsers such as Safari and Firefox had already placed some restrictions on third-party cookies, together they represented just 22% of browser usage. This limited, but didn’t fully kill, marketers’ reliance on third-party cookies. However, because Chrome is the most popular browser with 64% of web usage, advertisers now must find a new way forward.” 

Source: https://gs.statcounter.com/browser-market-share

With this move, Google hopes to improve user privacy and provides better transparency and control over tracking on sites that set third-party cookies.

To provide users with more transparency into which sites set cookies and why, Chrome will enforce that each cookie uses a parameter called SameSite, along with a secure declaration for cookies that are cross-site.

Chrome users may choose to block third-party cookies, thus limiting the way sites can collect data on their behavior. This will impact the ability of marketers to measure which ads were clicked and led to a conversion.

Skai clients are already compliant: the technical details

1. Skai cookies now comply with the requested declaration of the Same-site attribute. Third-party cookies labeled as SameSite=None, and secured (follow the HTTP request)
2. Skai’s integration with 3rd party vendors is also in compliance by securing our redirect to our client’s vendor.
3. For clients using our Universal publisher solution and Skai’s proprietary click redirect, clients are already supported by the redirect mechanism. However, we recommend you simply update the redirect in your site to make it secure, by changing the HTTP to HTTPS. Using the HTTPS protocol is also a best practice that has been recommended by Google for some time. 

For more information, ask your Skai rep

Have more questions? Want to double-check anything? 

Reach out to your Skai rep if you have any questions.

Book a Meeting of Skai