Add View and Click Data explainer section #1279

JensenPaul · 2024-09-17T22:20:47Z

No description provided.

dmdabbs · 2024-09-18T03:11:31Z

FLEDGE.md

+ * The `attributionsrc` HTML attribute may include multiple space-delimited URLs, in which case the browser will issue a background request for each.
+
+
+When the browser sends these request(s), it will include a new `Ad-Auction-Registration-Eligible` header whose value will be exactly one of "view" or "click".


Will Protected Audience "GREASE" the request header value as ARA does?

dmdabbs · 2024-09-18T03:45:11Z

FLEDGE.md

+1. All other requests will not have the `Ad-Auction-Registration-Eligible` header.
+
+
+A server receiving the `Ad-Auction-Registration-Eligible` header may respond in such a way that indicates to the browser that this request should be counted among the events used to calculate that user's view and click counts. To do so, the server's response should include an `Ad-Auction-Register-Event` structured response header of the form:


Suggest structured response header as structured field value header.

dmdabbs · 2024-09-18T04:02:30Z

FLEDGE.md

+A server receiving the `Ad-Auction-Registration-Eligible` header may respond in such a way that indicates to the browser that this request should be counted among the events used to calculate that user's view and click counts. To do so, the server's response should include an `Ad-Auction-Register-Event` structured response header of the form:
+
+```
+Ad-Auction-Register-Event: type=[view|click]; eligible-origins=https://www.example-dsp.com,https://www.example2.com;


Is the top-level type a Dictionary?

dmdabbs · 2024-09-18T04:12:17Z

FLEDGE.md

+```
+
+ * `type`: Required. Indicates whether this event should be counted as a "view" or a "click". The browser will verify that the type of event being registered matches the type for which this request is eligible - "view" or "click" - and discard events for which this request is not eligible.
+ * `eligible-origins`: Optional. Conveys one or more origins for which this event should be included in the computed view and click counts that will be provided to UDFs in Protected Audience auctions. If omitted or blank, this event will **only** be included in the counts available to the origin that returned that `Ad-Auction-Register-Event`.


The providing origin is implicitly an eligible-origin even if not listed, yes?

dmdabbs · 2024-09-18T04:22:21Z

FLEDGE.md

+#### 3.7.4 Access Controls
+
+**For sites**: 
+ * Recording of view and click events will only be allowed provided the publisher's Permissions-Policy permits interest group additions by the providing origin ([`join-ad-interest-group` directive](https://developers.google.com/privacy-sandbox/private-advertising/setup/web/permissions-policy)) . ARA permission policy is not required.


Some publishers might see this as too expansive. They may be fine with adtechs recording views and clicks, but not joining IGs on their property.

dmdabbs · 2024-09-18T04:26:12Z

FLEDGE.md

+ * If an adtech wants to use ARA but not record Protected Audience views and clicks, they can simply exclude the Protected Audience view and click events header and/or not have its site (scheme, eTLD+1) attested for Protected Audience API.
+
+**For end users**: 
+ * View and click events are only recorded when the user control for Protected Audience is enabled. The user control for ARA is not considered.


If an end user deletes site data/QD, are the view and click and PA data included?

dmdabbs · 2024-09-18T04:31:33Z

FLEDGE.md

+
+If specified, view/click counts will be computed by summing all counts for which the providing origin is included in `viewAndClickCountsProviders`, and for which the eligible origins include the interest group owner. If not specified, the browser will by default include only those view and click events that the interest group owner provided to itself.
+
+When the buyer-defined `generateBid()` is called, two new fields - `viewCounts` and `clickCounts` - will be provided in the `browserSignals` argument, each of which will be an object that contains a field for each of the five fixed time windows.


When the buyer-defined generateBid() is called...

This is for now on-device only?

dmdabbs · 2024-09-18T04:34:24Z

FLEDGE.md

+When the buyer-defined `generateBid()` is called, two new fields - `viewCounts` and `clickCounts` - will be provided in the `browserSignals` argument, each of which will be an object that contains a field for each of the five fixed time windows.
+
+```
+viewCounts: { pastHour: 1, pastDay: 2, pastWeek: 3, past30Days: 3, past90Days: 3 }


Suggest some mention of these attributes in 3.2's browserSignals

dmdabbs · 2024-09-18T04:45:32Z

FLEDGE.md

+
+When `attributionsrc` is used:
+ * The browser will always look for view and click data on the response to the request that goes to a clickthrough URL ("href" on an `<a>` tag) or impression URL ("src" on an `<img>` or `<script>` tag).
+ * When `attributionsrc` is non-empty, the browser will also send a background request to the URL specified in the value of `attributionsrc`, and then look for view and click data on the response.


Assume that foreground and background requests will process the headers on redirects to origins whose sites are attested?

anderagakura · 2024-09-19T09:25:03Z

FLEDGE.md

+
+```
+viewCounts: { pastHour: 1, pastDay: 2, pastWeek: 3, past30Days: 3, past90Days: 3 }
+clickCounts: { pastHour: 0, pastDay: 0, pastWeek: 1, past30Days: 1, past90Days: 1 }


For measurement, would not be useful to include additional time windows? (e.g past15days)

anderagakura · 2024-09-19T10:28:24Z

FLEDGE.md

+ * `eligible-origins`: Optional. Conveys one or more origins for which this event should be included in the computed view and click counts that will be provided to UDFs in Protected Audience auctions. If omitted or blank, this event will **only** be included in the counts available to the origin that returned that `Ad-Auction-Register-Event`.
+
+
+The "providing origin" is the origin from which the `Ad-Auction-Register-Event` header was received. The browser will only record view and click events for the providing origin if its [site](https://html.spec.whatwg.org/multipage/browsers.html#obtain-a-site) (scheme, eTLD+1) is attested for Protected Audience API. Please see [the Privacy Sandbox enrollment attestation model](https://github.com/privacysandbox/attestation#the-privacy-sandbox-enrollment-attestation-model). Similarly, the browser will only retain eligible origins whose site (scheme, eTLD+1) is attested for Protected Audience API.


Without talking about measurement platform but even a tech intermediary cannot be part of viewAndClickCountsProviders , right?

orrb1

Thanks, Paul.

orrb1 · 2024-09-20T13:39:58Z

FLEDGE.md

+
+```
+<img src="https://advertiser.example/pixel"
+     attributionsrc="'https://adtech.example/register-view?metadata=...">


Please remove the extraneous apostrophe. (attributionsrc="'...")

orrb1 · 2024-09-20T13:40:11Z

FLEDGE.md

+     attributionsrc="'https://adtech.example/register-view?metadata=...">
+
+<script src="https://advertiser.example/register-view"
+        attributionsrc="'https://adtech.example/register-view?metadata=...">


Add View and Click Data explainer section

464a8ac

dmdabbs reviewed Sep 18, 2024

View reviewed changes

anderagakura reviewed Sep 19, 2024

View reviewed changes

orrb1 reviewed Sep 20, 2024

View reviewed changes

WICG deleted a comment from Saleemfarheen Oct 15, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add View and Click Data explainer section #1279

Add View and Click Data explainer section #1279

JensenPaul commented Sep 17, 2024

dmdabbs Sep 18, 2024 •

edited

Loading

dmdabbs Sep 18, 2024 •

edited

Loading

dmdabbs Sep 18, 2024

dmdabbs Sep 18, 2024 •

edited

Loading

dmdabbs Sep 18, 2024

dmdabbs Sep 18, 2024

dmdabbs Sep 18, 2024

dmdabbs Sep 18, 2024

dmdabbs Sep 18, 2024

anderagakura Sep 19, 2024 •

edited

Loading

anderagakura Sep 19, 2024

orrb1 left a comment

orrb1 Sep 20, 2024

orrb1 Sep 20, 2024

		* The `attributionsrc` HTML attribute may include multiple space-delimited URLs, in which case the browser will issue a background request for each.


		When the browser sends these request(s), it will include a new `Ad-Auction-Registration-Eligible` header whose value will be exactly one of "view" or "click".

		1. All other requests will not have the `Ad-Auction-Registration-Eligible` header.


		A server receiving the `Ad-Auction-Registration-Eligible` header may respond in such a way that indicates to the browser that this request should be counted among the events used to calculate that user's view and click counts. To do so, the server's response should include an `Ad-Auction-Register-Event` structured response header of the form:


		If specified, view/click counts will be computed by summing all counts for which the providing origin is included in `viewAndClickCountsProviders`, and for which the eligible origins include the interest group owner. If not specified, the browser will by default include only those view and click events that the interest group owner provided to itself.

		When the buyer-defined `generateBid()` is called, two new fields - `viewCounts` and `clickCounts` - will be provided in the `browserSignals` argument, each of which will be an object that contains a field for each of the five fixed time windows.

		* `eligible-origins`: Optional. Conveys one or more origins for which this event should be included in the computed view and click counts that will be provided to UDFs in Protected Audience auctions. If omitted or blank, this event will only be included in the counts available to the origin that returned that `Ad-Auction-Register-Event`.


		The "providing origin" is the origin from which the `Ad-Auction-Register-Event` header was received. The browser will only record view and click events for the providing origin if its [site](https://html.spec.whatwg.org/multipage/browsers.html#obtain-a-site) (scheme, eTLD+1) is attested for Protected Audience API. Please see [the Privacy Sandbox enrollment attestation model](https://github.com/privacysandbox/attestation#the-privacy-sandbox-enrollment-attestation-model). Similarly, the browser will only retain eligible origins whose site (scheme, eTLD+1) is attested for Protected Audience API.

Add View and Click Data explainer section #1279

Are you sure you want to change the base?

Add View and Click Data explainer section #1279

Conversation

JensenPaul commented Sep 17, 2024

dmdabbs Sep 18, 2024 • edited Loading

Choose a reason for hiding this comment

dmdabbs Sep 18, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dmdabbs Sep 18, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

anderagakura Sep 19, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

orrb1 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dmdabbs Sep 18, 2024 •

edited

Loading

dmdabbs Sep 18, 2024 •

edited

Loading

dmdabbs Sep 18, 2024 •

edited

Loading

anderagakura Sep 19, 2024 •

edited

Loading