What is CHIPS?

Key Takeaways

[Music] hello chip stands for cookies having independent partition State and it introduces new cookie behavior that improves user privacy and security it allows developers to opt a cookie into partition storage with separate cookie jars per top level site in this video I'll explain how it works why we need it and when you should use it without partitioning thirdparty cookies can enable services to track users and join their information from across many unrelated top level sites this is known as cross-site tracking you can identify thirdparty cookies by their same side non value chips related website sets or storage access API will be the only way to read and write cookies from cross-side Context such as ey frames when third party cookies are blocked so make sure to audit your use of cookies so your sites are prepared to run without thirdparty cookies let's see how chips Works chips introduces a new cookie attribute partitioned to support cross-side cookies that are Partition by top level context all partition cookies must also be set with secure attribute to ensure they are only set and sent or secure protocols a partition third party cookie is tied to the top level site where it's initially set and cannot be accessed from elsewhere this way cookie set by a third party service can only be read within the same embedded context of the top level site where they were initially set in this example the cookie comes from storefinder do site which hosts a map of stores that enables a user to save their favorite store by using chips when brand a. site embeds store finder do site the value of my favorite cookie store cookie is 123 then if brand bsite also embeds storefinder site they will set and send their own partitioned instance of my favorite store cookie in this example the cookie set by the storefinder on brand bsite has the value of 456 this means that embedded Services can still save Sate but do not have shared cross-side storage that would allow crossy tracking use cases for chps include thir part chat embeds map embeds or payment embeds sub resource CDN load balancing headless CMS providers sandbox domains for serving untrusted user content and more chips is easy to implement it's just adding another attribute to cross-site cookies so if you have a service that's embedded in a third party context check if chips satisfies your use case if your site is embedding a third party service like this you don't need to make changes to any cookies but do check with your service provider that your dependencies will continue working when third party cookies are blocked chips is an important step to Help Services make a smooth transition to a future without third party cookies it is really the way cookies should work by default but backwards compatibility is an important part of the web by having an additional attribute chips provides an optin to more restrictive more secure type of cookie Behavior to get ready for the future without cross-side tracking audit your use of cookies and plan the actions needed if your site is impacted for cross-side cookies which store data on a per side basis chips is likely the right solution to learn more about chips check out our documentation and demos thanks for watching up [Music]