Open nikunj101 opened 3 years ago
Another one I'm late on, I would +1 this, we have quite a few clients who have been resistant to using JS libraries on their sites for any number of reasons. With Shared Storage having evolved to support response header based operations, it seems like this would be a logical extension...I'd assume performance would be better here as well.
Yes, +1 also, assuming one could express everything in an IG with Structured Field Values.
+1 on adding header based support for managing IG memberships on device.
Specifically, Chrome should support JoinAdInterestGroup, LeaveAdInterestGroup and ClearOriginJoinedAdInterestGroups in a lightweight header based solution (following other sandbox APIs like Topics, Attribution Reporting API and Shared Storage).
The TURTLEDOVE explainer focuses on providing a JS based API
joinAdInterestGroup
for adding users to interest groups. It might be useful to support non-JS APIs also. For instance, cookies today can be set via JS and also via HTTP response headers. An example use case is when advertisers want Adtech providers to handle the logic of adding users to interest groups, but they don’t want to embed external javascript libraries on their website. One thing to think about for such non-js APIs could be around how to implement access-controls like limiting the API call to only interest-group owner authenticated websites as suggested in the explainer.Disclaimer: Teams from across Google, including Ads teams, are actively engaged in industry dialog about new technologies that can ensure a healthy ecosystem and preserve core business models. Online discussions (e.g on GitHub) of technology proposals should not be interpreted as commitments about Google ads products.