Sparrow - Revision history

AdminUser at 16:12, 12 January 2021

2021-01-12T16:12:37Z

AdminUser at 02:38, 12 January 2021

2021-01-12T02:38:52Z

AdminUser at 02:31, 12 January 2021

2021-01-12T02:31:05Z

AdminUser at 02:29, 12 January 2021

2021-01-12T02:29:23Z

AdminUser at 20:44, 11 January 2021

2021-01-11T20:44:08Z

AdminUser: Created page with "The goal of Google's Privacy Sandbox is prevent marketers from engaging a particular audience in a particular context. Criteo's SPARROW propos..."

2021-01-11T20:43:37Z

Created page with "The goal of Google's Privacy Sandbox is prevent marketers from engaging a particular audience in a particular context. Criteo's SPARROW propos..."

New page

The goal of Google's [[:Category:Privacy Sandbox|Privacy Sandbox]] is prevent marketers from engaging a particular audience in a particular context.

Criteo's SPARROW proposal provides the same functionality as Google's [[Turtledove]], but allows for multiple organizations to provide this trusted "gatekeeper" service rather than just Google.<ref>https://github.com/WICG/sparrow</ref>

Google acknowledges that Criteo's proposed SPARROW improve Google's [[Turtledove]] by acknowledging the need for server-side processing. This trusted server hosts bidding models and executes auction logic. Relative to the in-browser solution proposed by TURTLEDOVE, SPARROW provides more flexibility with bidding and consumes fewer browser resources.<ref>
https://github.com/google/ads-privacy/tree/master/proposals/dovekey</ref>

== Impact ==
By limiting the number of organizations that can offer gatekeeper services, this does not provide publishers with open market choices.

By disclosing audience information to Google, publishers and buyers are leaking their intellectual property associated with that web client (e.g., high value customer) to the gatekeeper organization. Given the potential conflict of interest, Criteo suggests that gatekeepers cannot compete with their any of their clients.

== Open Questions ==
* If different buyers send their models to different gatekeepers, how many gatekeepers can one publisher query to retrieve auction information?

== References ==

<references />

[[Category:Glossary|Sparrow]]
[[Category:Privacy Sandbox|Sparrow]]

@@ Line 13: / Line 13: @@
 == Open Questions ==
 * If different buyers send their models to different gatekeepers, how many gatekeepers can one publisher query to retrieve auction information?
 * What is the time-delay in providing the data necessary for publishers to optimize their revenue?
 * What is the time-delay in providing the data necessary for marketers to optimize their media spend?
 * How scalable and costly is centralizing the processing of the ecosystem into a few organizations, when buyers often update large models (tens of gigabytes) multiple times per day?
 == References ==

@@ Line 15: / Line 15: @@
 * What is the time-delay in providing the data necessary for publishers to optimize their revenue?
 * What is the time-delay in providing the data necessary for marketers to optimize their media spend?
 == References ==

@@ Line 9: / Line 9: @@
 By limiting the number of organizations that can offer gatekeeper services, this does not provide publishers with open market choices.
-By disclosing audience information to Google, publishers and buyers are leaking their intellectual property associated with that web client (e.g., high value customer) to the gatekeeper organization. Given the potential conflict of interest, Criteo suggests that gatekeepers cannot compete with their any of their clients.
+By disclosing audience information, publishers and buyers are leaking their intellectual property associated with that web client (e.g., high value customer) to the gatekeeper organization. Given the potential conflict of interest, Criteo suggests that gatekeepers cannot compete with their any of their clients.
 == Open Questions ==

@@ Line 3: / Line 3: @@
 Criteo's SPARROW proposal provides the same functionality as Google's [[Turtledove]], but allows for multiple organizations to provide this trusted "gatekeeper" service rather than just Google.<ref>https://github.com/WICG/sparrow</ref>
-Google acknowledges that Criteo's proposed SPARROW improve Google's [[Turtledove]] by acknowledging the need for server-side processing. This trusted server hosts bidding models and executes auction logic. Relative to the in-browser solution proposed by TURTLEDOVE, SPARROW provides more flexibility with bidding and consumes fewer browser resources.<ref>
+Google acknowledges that Criteo's proposed SPARROW is an improvement on Google's [[Turtledove]] by acknowledging the need for server-side processing. This trusted server hosts bidding models and executes auction logic. Relative to the in-browser solution proposed by TURTLEDOVE, SPARROW provides more flexibility with bidding and consumes fewer browser resources.<ref>
 https://github.com/google/ads-privacy/tree/master/proposals/dovekey</ref>