search

WICG / floc

This proposal has been replaced by the Topics API.
https://github.com/patcg-individual-drafts/topics
Other
934 stars 90 forks source link

FLoC calculation on publishers' websites only #82

Open Myrtle opened 3 years ago

Myrtle commented 3 years ago

Hi!

(Greg Truchetet From Teads here)

We were reading this article yesterday and something is specified that was not fully obvious before. It is said that:

For the FLoC origin trial in Chrome 89, websites that don't opt out will be included in the FLoC calculation if Chrome detects that they are sites which load ads.

So it means only the publishers' websites are going to be taken into account if they didn't opt-out. The advertisers' websites are going to be ignored. This is not completely true I guess but we tend to that. Can you give more information on the rationale behind this decision? One of the reasons we have in mind would be to preserve the "interest-based" nature of the cohorts and to not "pollute" them with intents, letting FLEDGE exclusively covering this topic. It is also stated "for the trial", do you plan to try to include the advertisers' traffic in the computation at some point or this information was not important more than that? :)

Thank you!

jkarlin commented 3 years ago

Hmm, that article should probably read "ads or ad related resources". So advertisement sites will indeed often be included as they load ad script to report statistics such as conversions. The rationale is that we wanted to restrict pages included in the FLoC calculation in the OT to roughly where we'd expect to see them in the future once it's fully launched and ad-tech is using it, namely sites that are interested in advertising.

michaelkleber commented 3 years ago

Good point, thank you @Myrtle. Hey @samdutton, can we get that web.dev article changed to say "will be included in the FLoC calculation if Chrome detects that they are sites which load ads or ads-related resources"? I'm sure other people will have the same question.

Myrtle commented 3 years ago

Thank you for your quick replies @jkarlin and @michaelkleber, adding the ads-related resources precision sounds a good plan indeed. :)

samdutton commented 3 years ago

Thanks @Myrtle – meant to reply that I fixed this last week (in this PR).

johansmith90 commented 3 years ago

I was wondering if you could clarify a little bit further as to the precise definition of ads-related resources? For example, is Google Analytics Javascript considered to be an ads-related resource? What about embedded Youtube iframes? I read the Chromium documentation about Ad Tagging, but was not able to find an exhaustive list of ads-related resources therein. Thank you kindly in advance for your time and help.

michaelkleber commented 3 years ago

Hi @johansmith90: Check out the answer from our Dev Rel folks on Twitter: https://twitter.com/rowan_m/status/1383380295336878091

The precise list we use starts from EasyList but then goes through some crunching before ending up in Chromium, so using the browser dev tools to see exactly what's ads-related on any particular page is probably the easiest way to answer all your questions.

MH621003 commented 2 years ago

Hello, 👋. I wish you both well and bless you for the year..