Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPARROW reporting vs. single-person ads #10

Open
michaelkleber opened this issue Jun 30, 2020 · 2 comments
Open

SPARROW reporting vs. single-person ads #10

michaelkleber opened this issue Jun 30, 2020 · 2 comments

Comments

@michaelkleber
Copy link

In your reporting proposal's section Report on Ads Served you say "the publisher receives all web bundles" that rendered on their site.

This seems hard to reconcile with the proposals on the TURTLEDOVE repo like WICG/turtledove#31 from @jonasz or WICG/turtledove#36 from @appascoe that propose ways to make a web bundle targeted at just one individual. There are privacy problems with showing the publisher the ad that says "Hey Michael Kleber, your insulin prescription is about to expire, click here to reorder!"

Are these in fact mutually exclusive desires, or do you all think there's a way to achieve everyone's goals here?

From a browser point of view, it's hard for me to get comfortable with the notion that we'd offer a mechanism that looks like it sends a message to just one person, but in fact there's a built-in way for someone else to see it.

@jonasz
Copy link

jonasz commented Jul 1, 2020

Hi Michael,

Are these in fact mutually exclusive desires, or do you all think there's a way to achieve everyone's goals here?

The use case we'd like to support is to provide great ecommerce recommendations in our ads. Being able to show user-related sensitive information is definitely not something we're looking for.

Building on that, I think we can seek solutions that allow recommendation flexibility, but protect the user from sensitive information being leaked. Some ideas:

  1. If we pursue the idea of ad component-level audience thresholds, that should already solve the concern. If desired though, we could consider strengthening the privacy guarantees by reporting to the publisher the components of the ads, not entire ads. ("Item 313 was displayed in 820 impressions, item 117 in 22001 impressions, ...")
  2. If we'd like to be able to show rare ads, we could require all potential creatives (or components thereof) to be publicly available and auditable before an impression can occur.

// 1) and 2) are separate ideas, but they are compatible.

@BasileLeparmentier
Copy link
Collaborator

Hi Michael, Jonasz,

Thanks for your message. To be fully transparent, we proposed this reporting with the idea of cohorts being the atom of this new world.

I see some ways to handle these ads on new elemental particles. First if it is only used to choose product, we could send all products that are used to target a single users and the creative id (meaning that if 10 ads were shown at user level, you would have one bundle and the products of the 10 ads together without ways of knowing which were for whom).

This is really just an idea, but yes we might need a way to handle these specifics ads, and Jonasz also gave some ideas.

We are open on any ways to both allow ads targeted at the user level whilst preserving ways for the publisher to protect its user and its brand from malicious actors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants