- From: Charlie Harrison via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jun 2022 02:39:28 +0000
- To: public-patcg@w3.org
Here's a (somewhat ad-hoc) list of use-cases we can prioritize, and possibly reduce down if we can immediately reject some use cases as infeasible. - Basic functionality (probably table stakes?) - Support click-through conversions - Support view-throughs / opportunities - Aggregate conversion counts - More complicated queries - Aggregate value sums - Dynamic queries (as opposed to fixed queries / buckets embedded in the browser reports like in ARA / PCM) - Multiple breakdowns - Flexible sensitivity management (i.e. [exploit advanced dp composition](https://github.com/patcg/private-measurement/issues/16#issuecomment-1163291805)) - Adaptive queries - Attribution scope - App <-> web - Cross device - cross publisher / cross channel - online-to-offline conversions - Attribution function - Last-touch attribution - “simple” multi-touch (rules-based) - “complex” multi-touch (DDA, shapley, etc) - Third party reporting (probably need to break this down into constituent use-cases...) - Full fledged ML training / optimization (e.g. agg service runs a DNN) - Near-real time reporting I think many of these are likely achievable in an MVP, and hopefully more in any extensions we want to add. -- GitHub Notification of comment by csharrison Please view or discuss this issue at https://github.com/patcg/meetings/issues/56#issuecomment-1163859341 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 June 2022 02:39:30 UTC