Difference between revisions of "Turtledove"
Jump to navigation
Jump to search
(Created page with "The goal of Google's “Privacy Sandbox:” is prevent marketers from engaging a particular audience in a particular context. TURTLEDOVE (“Two Uncorrelated Requests,...") |
|||
| Line 1: | Line 1: | ||
| − | The goal of Google's “[[:Privacy Sandbox | + | The goal of Google's “[[Category:Privacy Sandbox|Privacy Sandbox]]” is prevent marketers from engaging a particular audience in a particular context. |
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> | ||
Revision as of 18:40, 11 January 2021
The goal of Google's “” is prevent marketers from engaging a particular audience in a particular context.
TURTLEDOVE (“Two Uncorrelated Requests, Then Locally-Executed Decision On Victory”) proposal attempts to enable consumer retargeting without any marketers receiving any identifier.[1]
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.
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.