Discussion - debugging support for summary reports

[hostirosti]

We are working on adding the possibility to generate debug summary reports from encrypted aggregatable reports with the AWS based aggregation service. This capability will be time-limited and be phased out at a later time.

We would like to hear from you what capabilities you'd like to see in these debug summary reports.

Some ideas we are considering:

• return unnoised metric and noise that would have been applied to the metric with the given epsilon
• return metrics that have not been listed in the output domain with an annotation hinting to the omission

Questions:

• What helps you to understand the inner workings of the system better and helps you to develop experiments using the attribution reporting APIs?
• How are you currently generating your output domains and what tools would help you to simplify this process?