{"id":115311,"date":"2024-04-25T09:22:44","date_gmt":"2024-04-25T07:22:44","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/google-otlozhil-prekrashhenie-podderzhki-storonnih-cookie-v-chrome"},"modified":"2024-04-25T09:22:44","modified_gmt":"2024-04-25T07:22:44","slug":"google-otlozhil-prekrashhenie-podderzhki-storonnih-cookie-v-chrome","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/google-otlozhil-prekrashhenie-podderzhki-storonnih-cookie-v-chrome","title":{"rendered":"Google has postponed the end of third-party cookie support in Chrome.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has announced another adjustment to its plans to terminate support for third-party cookies in the Chrome browser, which are set when visiting sites different from the current page's domain. Initially, support for third-party cookies was planned to be discontinued by 2022, then the deadline was pushed to mid-2023, and later it was further moved to the fourth quarter of 2024. Due to the need for additional agreements and the unpreparedness of the ecosystem, it has been decided not to disable support for third-party cookies in 2024 either. A new planned date for discontinuation has not yet been announced. <\/p>\n
Third-party cookies are used to track user movements across websites in advertising network codes, social media widgets, and web analytics systems. The cookie-related changes are being advanced as part of the Privacy Sandbox initiative, aimed at achieving a compromise between users' need for privacy and the desire of advertising networks and websites to track visitor preferences. Earlier attempts to replace tracking cookies in Chrome faced resistance in the community and criticism that the methods replacing tracking cookies do not solve all issues and create new risks, such as creating conditions for user discrimination and introducing an additional factor for covert identification and tracking of user movements. <\/p>\n
Instead of tracking cookies, the following APIs are proposed: <\/p>\n
\n
FedCM (Federated Credential Management) allows for the creation of unified identification services that ensure privacy and work without third-party cookies. <\/li>\n
Private State Tokens allow for differentiating between users without using cross-site identifiers and sharing user authentication information across different contexts. <\/li>\n
Topics (which replaces the FLoC API) allows the definition of user interest categories, which can be used to identify groups of users with similar interests without identifying individual users through tracking cookies. Interests are calculated based on user activity in the browser and stored on the user's device. With the Topics API, an ad network can obtain general information about specific interests without having information about the user's specific activity. <\/li>\n
Protected Audience, a solution for retargeting tasks and assessing one's own audience (working with users who have previously visited the site). <\/li>\n
Attribution Reporting, allows for evaluating advertising effectiveness metrics such as clicks and conversion (a purchase on the site after clicking). <\/li>\n
Storage Access API, can be used to request user permissions to access the Cookie storage if third-party Cookies are blocked by default. <\/li>\n<\/ul>\n<\/li>\n