3 ms·
Post from April, FLEDGE is renamed to Protected Audience API. https://privacysandbox.com/intl/en_us/news/protected-audience-api-our-new-name-for-fledge https://
by jauntywundrkind 3y ago
Post from April, FLEDGE is renamed to Protected Audience API. https://privacysandbox.com/intl/en_us/news/protected-audience-api-our-new-name-for-fledge https://privacysandbox.com/intl/en_us/news/protected-audienc...
Docs for Protected Audience API: https://developers.google.com/privacy-sandbox/relevance/protected-audience https://developers.google.com/privacy-sandbox/relevance/prot...
It feels like there's a bunch more pieces to the puzzle too. There's Topic API, which by itself only tells a site more about users, but does so in a supposedly privacy preserving way. There's dozens of efforts listed on https://developers.google.com/privacy-sandbox/relevance/protected-audience-api/feature-status https://developers.google.com/privacy-sandbox/relevance/prot... , mostly slated for 2023 & seemingly not updated in a while (with abundant broken links too). It's a bit wild that third party cookies are deprecated even though it seems like then promised fair privacy preserving replacement for ads is maybe still being built?