Turtledove - Revision history

Bleparmentier at 14:07, 12 July 2021

2021-07-12T14:07:18Z

Jkoran at 01:07, 13 June 2021

2021-06-13T01:07:02Z

Jkoran at 18:47, 5 February 2021

2021-02-05T18:47:31Z

Jkoran at 18:45, 5 February 2021

2021-02-05T18:45:35Z

Jkoran at 14:31, 4 February 2021

2021-02-04T14:31:08Z

Jkoran at 14:12, 4 February 2021

2021-02-04T14:12:37Z

AdminUser at 15:28, 12 January 2021

2021-01-12T15:28:07Z

AdminUser at 18:41, 11 January 2021

2021-01-11T18:41:52Z

AdminUser at 18:41, 11 January 2021

2021-01-11T18:41:19Z

AdminUser at 18:40, 11 January 2021

2021-01-11T18:40:37Z

@@ Line 4: / Line 4: @@
 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. 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 [[Fenced Frames|Fenced Frame]] ad slot on the publisher.
+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 almost solely on audience information. In the audience auction, some contextual information can be sent inside the browser to select ads, but is extremely limited by the complexity of having everything in a javascript code. The winner of these is sent to [[Fenced Frames|Fenced Frame]] ad slot on the publisher.
 Google has suggested measuring the effectiveness of TURTLEDOVE proposal under the [[Fledge]] project.

@@ 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.<ref>https://github.com/michaelkleber/turtledove</ref>
@@ Line 5: / Line 6: @@
 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 [[Fenced Frames|Fenced Frame]] ad slot on the publisher.
 == Impact ==
 TURTLEDOVE removes transparency and control from publishers, by requiring the final auction in a given ad slot to be conducted by Google.
-In addition to removing price transparency and introducing a time-delay to publishers in how well their websites are performing, TURTLEDOVE also impacts the publishers ability to appropriately understanding and managing:
+In addition to removing price transparency and introducing a time-delay to publishers in how well their websites are performing, TURTLEDOVE also impacts publishers ability to appropriately understanding and managing:
 Traffic quality (TQ) - is this a legitimate request from a real user or [[Non-human Traffic|non-human traffic]]?
@@ Line 22: / Line 24: @@
 Another potential impact of removing this information is a degraded end user experience.
-Because Turtledove mandates the browser determines the final auction and relies on Fenced Frames, publishers cannot compare in real-time the monetization of the ad slot by Google vs competing ads sourced via other mechanisms. For example, if a publisher has other demand sources, such as an internal sales team, these will need to forward their highest desirable ad to Google for it to compare against the winning ad among the context-only ad and the audience-only ad it processes within the auction.
+Because TURTLEDOVE mandates the browser determines the final auction and relies on Fenced Frames, publishers cannot compare in real-time the monetization of the ad slot by Google vs competing ads sourced via other mechanisms. For example, if a publisher has other demand sources, such as an internal sales team, these will need to forward their highest desirable ad to Google for it to compare against the winning ad among the context-only ad and the audience-only ad it processes within the auction.
 == Open Questions ==

@@ Line 22: / Line 22: @@
 Another potential impact of removing this information is a degraded end user experience.
-Because Turtledove mandates the browser determines the final auction and relies on Fenced Frames, publishers cannot compare in real-time the monetization of the ad slot by Google vs competing ads sourced via other mechanisms. For example, if a publisher has other demand sources, such as an internal sales team, these will need to forward their highest desirable ad ad to browser for it to compare against the winning ad among the context-only ad and the audience-only ad it processes within the auction.
+Because Turtledove mandates the browser determines the final auction and relies on Fenced Frames, publishers cannot compare in real-time the monetization of the ad slot by Google vs competing ads sourced via other mechanisms. For example, if a publisher has other demand sources, such as an internal sales team, these will need to forward their highest desirable ad to Google for it to compare against the winning ad among the context-only ad and the audience-only ad it processes within the auction.
 == Open Questions ==

@@ Line 3: / Line 3: @@
 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. 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.
+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 [[Fenced Frames|Fenced Frame]] ad slot on the publisher.
 == Impact ==
@@ Line 20: / Line 21: @@
 Another potential impact of removing this information is a degraded end user experience.
 == Open Questions ==

@@ Line 10: / Line 10: @@
 Traffic quality (TQ) - is this a legitimate request from a real user or [[Non-human Traffic|non-human traffic]]?
 DSP qualification - which DSPs are interested in this request?
 Bid solicitation - which DSPs will place a bid on this request?
 Ad Quality (AQ) - which bids are eligible given the publisher's requirements?
 Valuation - which bid is most valuable to the publisher at this moment?<ref>https://github.com/JoelPM/prebid-td/</ref>

← Older revision		Revision as of 18:41, 11 January 2021
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.

	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>

← Older revision		Revision as of 18:40, 11 January 2021
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.

	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>