Difference between revisions of "Turtledove"
m |
m |
||
| Line 1: | Line 1: | ||
| − | The goal of Google's [[:Category:Privacy Sandbox|Privacy Sandbox]] is prevent marketers from engaging a particular audience in a particular context. | + | The goal of Google's [[:Category:Privacy Sandbox|Privacy Sandbox]] is prevent marketers from engaging a particular audience in a particular context.<ref>https://github.com/michaelkleber/turtledove</ref> |
TURTLEDOVE (“Two Uncorrelated Requests, Then Locally-Executed Decision On Victory”) proposal attempts to enable consumer retargeting without any marketers receiving any identifier.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> | TURTLEDOVE (“Two Uncorrelated Requests, Then Locally-Executed Decision On Victory”) proposal attempts to enable consumer retargeting without any marketers receiving any identifier.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> | ||
| − | The proposed mechanism requires the web client to store some the attribute information marketers would want to use as an input into audience creation or auction management. | + | The proposed mechanism requires the web client to store some the attribute information marketers would want to use as an input into audience creation or auction management. As the name implies, the web client performs two separate local auctions based solely on context or solely on audience information. The winner of these is sent to the publisher. |
== Impact == | == Impact == | ||
By removing this ability, this has the risk of preventing organizations from detecting [[Non-human Traffic|non-human traffic]]. Another potential impact of removing this information is a degraded end user experience. | By removing this ability, this has the risk of preventing organizations from detecting [[Non-human Traffic|non-human traffic]]. Another potential impact of removing this information is a degraded end user experience. | ||
| + | |||
| + | == Open Questions == | ||
| + | * What is the impact on web experiences given many client devices do not have the same processing power of the servers that currently select which content to render? | ||
| + | * How does the local client auction support publisher custom logic, such as factors other than price to select which ad to render? | ||
== References == | == References == | ||
Revision as of 15:28, 12 January 2021
The goal of Google's Privacy Sandbox is prevent marketers from engaging a particular audience in a particular context.[1]
TURTLEDOVE (“Two Uncorrelated Requests, Then Locally-Executed Decision On Victory”) proposal attempts to enable consumer retargeting without any marketers receiving any identifier.[2]
The proposed mechanism requires the web client to store some the attribute information marketers would want to use as an input into audience creation or auction management. As the name implies, the web client performs two separate local auctions based solely on context or solely on audience information. The winner of these is sent to the publisher.
Impact
By removing this ability, this has the risk of preventing organizations from detecting non-human traffic. Another potential impact of removing this information is a degraded end user experience.
Open Questions
- What is the impact on web experiences given many client devices do not have the same processing power of the servers that currently select which content to render?
- How does the local client auction support publisher custom logic, such as factors other than price to select which ad to render?