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

Outcome-based Turtledove #52

Closed
jonasz opened this issue Sep 8, 2020 · 2 comments
Closed

Outcome-based Turtledove #52

jonasz opened this issue Sep 8, 2020 · 2 comments

Comments

@jonasz
Copy link
Contributor

jonasz commented Sep 8, 2020

Hi all,

At RTB House we have formalized some of our thoughts on "outcome-based Turtledove", an idea first discussed in #5.

https://github.com/jonasz/outcome_based_turtledove

Benefits include:

  • More accurate bidding possible.
  • Mathematical guarantees on microtargeting prevention.
  • Decoupling of microtargeting prevention and bidding mechanisms.

Please let us know what you think, and we will be happy to discuss this idea further.

Best regards,
Jonasz

@michaelkleber
Copy link
Collaborator

Thank you! I appreciate the thought you've put into what a mathematical measure of "sufficient diversity" could look like. I'll need to take some time to understand it.

I very much like your idea for a "mechanism of fallback creatives", which is a great way to roll out a change in the creative being shown to an audience without worrying about a lull in ability to buy. This was really worrying me during our discussion in #5, and I think you've found the right answer here.

@JensenPaul
Copy link
Collaborator

Closing this issue as it represents past design discussion that predates more recent proposals. I believe some of this feedback was incorporated into the Protected Audience (formerly known as FLEDGE) proposal. If you feel further discussion is needed, please feel free to reopen this issue or file a new issue.

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