standards-positions icon indicating copy to clipboard operation
standards-positions copied to clipboard

Attribution Reporting API

Open akashnadan opened this issue 1 year ago • 6 comments

WebKittens

No response

Title of the spec

Attribution Reporting

URL to the spec

https://wicg.github.io/attribution-reporting-api/

URL to the spec's repository

https://github.com/WICG/attribution-reporting-api

Issue Tracker URL

No response

Explainer URL

No response

TAG Design Review URL

https://github.com/w3ctag/design-reviews/issues/724

Mozilla standards-positions issue URL

https://github.com/mozilla/standards-positions/issues/791

WebKit Bugzilla URL

No response

Radar URL

No response

Description

The Attribution Reporting API makes it possible to measure when an ad click or view leads to a conversion on an advertiser site, such as a sale or a sign-up. The API doesn't rely on third-party cookies or mechanisms that can be used to identify individual users across sites. The API enables two types of attribution reports:

  • Event-level reports associate a particular event on the ad side (a click or view) with coarse conversion data. To preserve user privacy, conversion-side data is coarse, and reports are noised and are not sent immediately. The number of conversions is also limited.
  • Aggregatable reports provide a mechanism for rich metadata to be reported in aggregate, to better support use-cases such as campaign-level performance reporting or conversion values.

akashnadan avatar Apr 25 '23 23:04 akashnadan

  • Added concerns: venue because this should probably be moved to the PAT CG. (Same goes for PCM, of course.)
  • Added concerns: interoperability because, while I really hope we manage to converge PCM and this as much as possible, to the extent we don't we'll likely have interop problems.

hober avatar Apr 26 '23 20:04 hober

Also request for WebKit position on Cross App and Web Attribution Measurement, which is an extension to the Attribution Reporting API.

Cross App and Web Attribution Measurement

WebKittens

No response

Title of the spec

Attribution Reporting

URL to the spec

https://wicg.github.io/attribution-reporting-api/#cross-app-and-web

URL to the spec's repository

https://github.com/WICG/attribution-reporting-api

Issue Tracker URL

No response

Explainer URL

https://github.com/WICG/attribution-reporting-api/blob/main/app_to_web.md

TAG Design Review URL

w3ctag/design-reviews#724

Mozilla standards-positions issue URL

mozilla/standards-positions#791

WebKit Bugzilla URL

No response

Radar URL

No response

Description

Currently, the Attribution Reporting API supports attributing events within a single browser instance. This proposal expands the scope of attribution to allow attributing conversions that happen on the web to events that happen off the browser on the same device, within other applications such as mobile applications, or vice-versa.

The proposal here takes advantage of OS-level support for attribution. In particular, it gives the developer an option to allow events on the mobile web to be joinable with events in Android’s Privacy Sandbox, although support for other platforms could also be implemented in the future.

linnan-github avatar Jan 24 '24 15:01 linnan-github

@linnan-github your comment is rather confusing. What are you trying to achieve?

annevk avatar Jan 24 '24 15:01 annevk

@linnan-github your comment is rather confusing. What are you trying to achieve?

We're also requesting WebKit position on Cross App and Web Attribution Measurement, which is an extension to the Attribution Reporting API. Updated the comment to be clear, thanks!

linnan-github avatar Jan 24 '24 16:01 linnan-github

Could you either fold that into the original request or open a new issue? Our system isn't equipped to handle additional requests in subsequent comments.

It also seems a bit weird to add that request without responding to the feedback @hober already gave on the initial proposal.

annevk avatar Jan 24 '24 16:01 annevk

Could you either fold that into the original request or open a new issue? Our system isn't equipped to handle additional requests in subsequent comments.

It also seems a bit weird to add that request without responding to the feedback @hober already gave on the initial proposal.

Opened a new issue https://github.com/WebKit/standards-positions/issues/307 for this request, thanks!

linnan-github avatar Jan 24 '24 17:01 linnan-github