search

WICG / turtledove

TURTLEDOVE
https://wicg.github.io/turtledove/
Other
522 stars 226 forks source link

Warn developers when k-anon filters an ad candidate #1214

Open JacobGo opened 3 months ago

JacobGo commented 3 months ago

With FledgeEnforceKAnonymity gradually rolling out to Chrome stable per docs, I've already observed several instances of confusion and lost productivity when debugging unexpectedly null runAdAuction() results for tiny, test-only buyers due to k-anon filtering.

While the solution so far has been to just disable the feature on the command line while testing, developers should receive a debug signal from the browser perhaps in the DevTools Interest Groups panel or in the JS console when this filtering occurs, especially if this filtering removed all otherwise accepted ad candidates. If we expect this to happen frequently, to avoid console clutter the browser might log each filtered candidate in the IG panel and only once in the console iff there was no winner and k-anon filtered at least one candidate.

Adjacently, I had to dig deeply to find https://github.com/WICG/turtledove/issues/867#issuecomment-2073916461 indicating that production observability of k-anon may be done through private aggregation reporting. It would be helpful to include this detail in the k-anon developer guide (although as a nit I believe it is the browser, not the seller, that rejects the bid in this case).

dmdabbs commented 1 week ago

Hello @JacobGo.

I'm doing some testing in Canary. When starting Chrome sans cmdline flags or with --enable-features=FledgeEnforceKAnonymity, I see browserSignals.kAnonStatus="notCalculated" in reportWin. I'm expecting to see kAnon enforced. Am I missing a magic incantation?

JacobGo commented 1 week ago

Hey David, I haven't been able to recreate the magical incantation of flags that Chrome used to start enforcing k-anon on my test browser profile back in June. One suggestion might be to include FledgeConsiderKAnonymity alongside FledgeEnforceKAnonymity though.