Re: [meetings] Agenda Request - Measurement use-cases deep dive and requirements (#51)

@csharrison I agree that we should focus the conversation, given there is only 1 hour. However, I think the core question at hand right now is: "What is the first use case that the Working Group should work to standardize?"

We have been working in the general direction of some form of cross-site attribution measurement as that first use case (something in the area of _Private Click Measurement_ / _Attribution Reporting API_ / _Interoperable Private Attribution_,) but I don't think we yet have formal consensus on that use case, nor do we have the specific details of the functionality that the use case would need to support. Open questions I'm still aware of:
1. Clicks vs an API call to report an impression
2. Same device vs Cross Device
3. Privacy constraints (k-anonymity / differential privacy)
4. Privacy budget and the _grain_ at which it's allocated/managed
5. Acceptable delays in reporting
6. Attribution methodology (last touch, multi touch, etc)
7. (I'm certainly missing others...)

I'm doubt we will be able to reach consensus on all of these in the meeting, but it does seem prudent that we reach consensus on the use case the Working Group should tackle, find members to participate in that Working Group, and task them with the right questions to formulate an opinion (or options) on.

I don't mean to say we need to solve "Attribution Measurement" before we begin talking about the optimization use case, but I do believe that it's important for the group to unblock and begin more formal work on that use case (or decide that it's not the right first use case) before we begin work on others. Once we have consensus on that first use case, and the Working Group can work on it in parallel, this group can consider additional use cases. Also, the optimization use-case seems to rely on attribution (at least in the formulations I've seen.)

-- 
GitHub Notification of comment by eriktaubeneck
Please view or discuss this issue at https://github.com/patcg/meetings/issues/51#issuecomment-1128988386 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 17 May 2022 15:07:13 UTC