Big news: Microsoft Edge is launching its own privacy-preserving ads API that is modeled on Google Chrome's PA API, but has some key differences that improve upon PA. https://lnkd.in/e6EtEyjY A main difference is Edge's Ad Selection API (ASAPI) only runs in Trusted Execution Environments (TEEs) and has no on-device component (to start). PA API can work in either, but most of the current development is on-device which presents a number of concerns, including latency. ASAPI also supports multi-size and multi-slot auctions, which is a big weakness of PA API that needs to be addressed. A huge benefit is ASAPI allows for ad creatives to be dynamically updated, unlike PA, which requires them to be loaded when the interest group is set. Another nice feature of the TEE setup in ASAPI is they are open to running TEEs on platforms beyond Google and Amazon, which has been a sticking point for a lot of adtech firms supporting PA API. But perhaps the best feature of ASAPI (from what I've read so far) is that it is largely feature- and syntax-compatible with PA so it will be easy for adtech, publishers, and advertisers to support if they have already built to PA. Really nice work here from the Edge team - this pushes the ball forward in a very positive way!
Thanks for the engagement, Paul. FYI the acronym we've been using internally is AdS ??
i cant stop saying “A sappy pappy” in my head now (ASAPI & PAAPI)
5.35% market share, but big news for a small fish nonetheless and directional guidance on where things are going. Maybe Open AI will help them grab more browser market share... Thanks as always for sharing Paul.
Collective sigh of relief with that second to last paragraph!
OMG
Big news indeed
Wasn’t it Avis that said, “We’re No. 2. We try harder.”? ??
Thanks for this great summary Paul! What an exciting development.
Tech Leading Privacy Sandbox implementation at MSA, Developing Ad Selection API
12 个月Hey Paul Bannister want to point out a subtle difference in privacy model, that underlies the features you described and allows others: AdS takes the stance that processing cross site signals within the "opaque process" is ok provided there are DP/K output gates on the process. This is what ultimately helps support some of the features you described, and we think will allow for more effective demand in the Private Auction, ultimately leading to more usage of these APIs with the goal of steering away from other ultimately PII or fingerprinting based solutions. No doubt this will be the source of lots of discussion, but it's part of the goal of iterating towards a better set of tradeoffs (better pareto curve, to be super nerdy).