Google has long had a plan to phase out third-party cookies (cookies) in Chrome, and replace them with the solution they released Privacy protection.
Report now the edge That the first phase of phasing out third-party cookies in Chrome is almost complete, and that on July 24, the search giant will begin making the necessary APIs available to developers.
To use the APIs, you must have Chrome version 115.
While Apple and Mozilla turned off third-party cookies by default long ago, Google wanted an alternative that would allow, among other things, anonymous targeting of ads.
However, many believe that Privacy Sandbox is not much better than third-party cookies, and Google has not been able to involve Apple or Mozilla in this initiative. The W3C Standards Organization is Not impressed eithermeaning technology no It protects users’ privacy well enough.
«Thus, Google is alone in the Privacy Sandbox.»
Thus, Google is alone in the Privacy Sandbox.
Privacy Sandbox APIs are now available to developers API threadsOne of which ranks users’ interests based on the websites they browse, but without sharing the information directly with advertisers.
Then you have one Attribution reporting API which measures when ad clicks or impressions appear Transfers – That is, someone buys something or performs an action based on the advertisement.
Finally, you have a file Protected Audience API (formerly FLEDGE) which makes it possible to show you relevant ads based on your previous interaction with the advertiser – what is often called Remarketing In the language of marketing. For example, you may have clicked on an advertisement on a website or a link in an email, and then a few days later you may see an advertisement for something similar on a completely different website.
All of this must be done in a way that protects privacy better, according to Google, than third-party cookies.
Only some developers will get all the APIs
According to The Verge, the APIs will only go live for a limited number of developers now on July 24, after which they will be gradually rolled out.
Also, only a few will have access to it everyone APIs at a time, so that Google can more easily detect and isolate errors related to specific APIs.
Over the next week, about 35 percent of Chrome browsers will have access to the APIs, then that percentage will rise to 60 percent in August and to about 99 percent by the time Chrome 116 is expected to be available in mid-August.
You can read more about this at This blog From Google, which also has other news about Chrome 115.
“Web specialist. Lifelong zombie maven. Coffee ninja. Hipster-friendly analyst.”