Re: [web-adv] agenda 29 March

Hello Elad, nice to meet you.

We're happy to talk about these in a web-adv meeting if the group is
interested, but let me point out that there is an every-other-week call
that is specifically about the FLEDGE API.  The next call is this coming
Wednesday, March 30th; further details are posted in
https://github.com/WICG/turtledove/issues/88.

Also, please take a look at the Chrome Developer site's article about the
FLEDGE API.  The section "How does a FLEDGE ad auction work?
<https://developer.chrome.com/docs/privacy-sandbox/fledge/#how-does-a-fledge-ad-auction-work>"
might already answer all of your questions!  In particular, (1) SSP
"sellers" do indeed retain their core job of picking the winner of the
on-device auction.  The seller can pass in all the information it wants
about the surrounding page — including (3) contextual signals and (2) the
winning price of the best contextual ad, so it can only allow FLEDGE
auction winners that beat that floor.

--Michael



On Thu, Mar 24, 2022 at 5:17 PM Elad Tessler <elad.tessler@taboola.com>
wrote:

> Hi everybody, thanks for the opportunity to share our thoughts.
>
> Our team has a few questions regarding FLEDGE principles, for example:
> (1) How does FLEDGE preserve the business model of SSPs? Most of them rely
> on their ability to determine the auctions' results. If the auction runs in
> the browser, what can they do to influence it? Of course, there are many
> privacy concerns, but I'm not sure if and how FLEDGE balances between them.
> (2) Can you run FLEDGE's auction and decide not to serve the winning ad?
> Let's say that the winning bid would pay 10 cents CPM, but you have another
> bid (using Topics or other signals) that'd pay 15 cents, so forcing the SSP
> to display FLEDGE's ad will result in loss of revenue.
> (3) Can you use contextual signals as a parameter in the auction? (it
> refers to the first question regarding the auction's logic).
>
> Overall, I think that FLEDGE is a clear and good proposal for the demand
> side and users' privacy, but I'm not sure (and maybe I'm missing something)
> that it keeps the supply side business model.
>
> Thanks again!
> Elad
>
> On Thu, Mar 24, 2022 at 9:26 PM Michael Kleber <kleber@google.com> wrote:
>
>> Hi folks,
>>
>> What is the agenda item "Questions on Topics API (Elad)"?  Apologies if
>> I'm forgetting something we've been asked already.
>>
>> --Michael
>>
>>
>> On Thu, Mar 24, 2022 at 1:43 PM Wendy Seltzer <wseltzer@w3.org> wrote:
>>
>>> Hi Web Adv BG,
>>>
>>> We'll meet on 29 March, after some of the clocks have changed again.
>>>
>>> Agenda, 29 March (Tuesday, 11am Eastern / 1500 UTC)
>>>
>>> agenda+ Introductions and Agenda Curation
>>> agenda+ Questions on Topics API (Elad)
>>> agenda+ Updates on IETF activities?
>>> agenda+ Dashboard review
>>>    https://w3c.github.io/web-advertising
>>>    https://w3c.github.io/web-advertising/dashboard/
>>> agenda+ AOB
>>>
>>>
>>> Remember that you can get a calendar feed or invite for our meeting
>>> schedule at the link below -- after login with W3C credentials.
>>>
>>> Calendar and join information:
>>> https://www.w3.org/groups/bg/web-adv/calendar
>>>
>>> Join us on irc, https://irc.w3.org/ channel #web-adv
>>>
>>> Thanks,
>>> --Wendy
>>>
>>> --
>>> Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 <(617)%20715-4883>
>>> (office)
>>> Strategy Lead and Counsel, World Wide Web Consortium (W3C)
>>> https://wendy.seltzer.org/        +1.617.863.0613 <(617)%20863-0613>
>>> (mobile)
>>>
>>>
>>>
>>>
>>
>> --
>> Forewarned is worth an octopus in the bush.
>>
>>

-- 
Forewarned is worth an octopus in the bush.