patcg-individual-drafts/private-aggregation-api

Issues

• Measuring buyer’s timeout

  #119 opened 8 months ago by ardianp-google
  3

• Enforce contribution budgets at the origin level

  #145 opened 3 months ago by ningwangpanda
  3

• Broken links in Private Aggregation API

  #157 opened 2 months ago by dontcallmedom-bot
  0

• Consider splitting contributions into multiple reports instead of truncating

  #81 opened a year ago by alexmturner
  13

• Reach whitepaper feedback

  #153 opened 3 months ago by menonasha
  0

• Providing global configuration for AdTechs

  #143 opened 3 months ago by ningwangpanda
  2

• Improving support for debugging (without debug mode)

  #131 opened 5 months ago by alexmturner
  2

• "Preview" job fails for users without write access

  #148 opened 3 months ago by dmcardle
  0

• More precisely define the contribution budget and window in the spec

  #141 opened 4 months ago by alexmturner
  0

• Questions on the private aggregation API and Aggregation Service scalability

  #115 opened 4 months ago by nurien2
  2

• Improve the payload encoding efficiency

  #116 opened 8 months ago by alexmturner
  0

• Concrete epsilon values

  #114 opened 9 months ago by martinthomson
  2

• Effects of k-anonymity not described well in the spec

  #132 opened 5 months ago by brusshamilton
  0

• Feedback on Contribution bounding value, scope, and epsilon

  #23 opened 2 years ago by alexmturner
  11

• Is it possible to send a negative value in contributeToHistogram()?

  #125 opened 6 months ago by romanych
  2

• Debug Mode Availability for Latency Stats?

  #104 opened 7 months ago by maleangrubb
  5

• Potential Bug in the debug mode latency stats implementation

  #121 opened 7 months ago by maleangrubb
  4

• Enabling Debug Reports in Private Aggregation API in Mode B.

  #110 opened 7 months ago by michal-kalisz
  3

• Consider padding the payload

  #56 opened a year ago by alexmturner
  7

• Consider tying `enableDebugMode()` availability to third-party cookie eligibility

  #57 opened a year ago by alexmturner
  3

• Knowing the publisher domain for Fledge

  #14 opened 10 months ago by alois-bissuel
  2

• Consider adding a custom 'label' to allow more flexible batching

  #92 opened a year ago by alexmturner
  4

• Meeting: Supporting Reach Measurement

  #19 opened a year ago by alexmturner
  9

• Private Aggregation API one-week test summary [05.2023]

  #82 opened a year ago by michal-kalisz
  1

• aggregation_coordinator_origin underspecified (underdefined??)

  #107 opened a year ago by miketaylr
  2

• Support for Blobs in sharedStorage worklets

  #83 opened a year ago by CGossec
  9

• Design support for multiple aggregation services

  #78 opened a year ago by alexmturner
  0

• Consider reducing the delay for reports with a context ID

  #80 opened a year ago by alexmturner
  2

• Status of this document

  #59 opened a year ago by chrisn
  0

• What is a delay after which report is sent?

  #77 opened a year ago by xottabut
  3

• Report verification for Protected Audience

  #79 opened a year ago by alexmturner
  0

• Extending shared storage API to support advanced reach reporting

  #17 opened 2 years ago by EvgSkv
  1

• Scale estimation for usage in FLEDGE

  #20 opened 2 years ago by alexmturner
  4

• Mitigating data loss and delays due to batching

  #24 opened 2 years ago by alexmturner
  1

• Register .well-known URIs

  #67 opened a year ago by alexmturner
  0

• Reliant specs and their layering

  #43 opened a year ago by yoavweiss
  1

• Ergonomics: `contributeToHistogram` could accept an array of contributions

  #70 opened a year ago by yoavweiss
  1

• Extended Private Aggregation API availability & Status

  #72 opened a year ago by maleangrubb
  1

• `sendHistogramReport` is not an accurate name

  #44 opened a year ago by yoavweiss
  7

• Clarify reporting origin

  #29 opened a year ago by alois-bissuel
  1

• Fetch based design as a considered alternative

  #42 opened a year ago by yoavweiss
  2

• enableDebugMode() should use a debugKey

  #46 opened a year ago by alexmturner
  0

• Updating references to FLEDGE

  #37 opened a year ago by alexmturner
  0

• Consider reducing maximum number of contributions per report

  #32 opened a year ago by alexmturner
  2

• Batch contributions for the same reporting origin together

  #15 opened 2 years ago by alexmturner
  0

• Why are you using well-known URIs here?

  #18 opened 2 years ago by mnot
  4

• FLEDGE integration

  #12 opened 2 years ago by jonasz
  2

• Consider adding immediately sent duplicate reports for debugging

  #10 opened 2 years ago by alexmturner
  0

• Improve debugging

  #8 opened 2 years ago by alexmturner
  0

• Provide more detail on expected report format

  #6 opened 2 years ago by alexmturner
  0