Clarification on aggregated report batching and privacy budget exhaustion about trusted-execution-aggregation-service

[maybellineboon]

Hi @rameetchandok ,

Privacy Budget exhaustion issue happens when you try to batch a report whose shared ID is has already been included in a previously successful batch.

When you collect the reports in a single batch, please try to ensure that all reports with the same shared ID are in the same batch. More guidance to this are shared in the batching strategies doc.

From #35, shared ID is comprised of api version, reporting origin, destination site, source registration time (truncated by the day) and scheduled report time (truncated by the hour).

Would you be able to help confirm that all reports are batched according to the shared ID fields? Also, can you help confirm if you are separating the reports into batches that are received in production and debug endpoint?

[rameetchandok]

Hi yes all reports were batched according to shared ID fields. An important thing i missed to mention is that the reports fail if batched for 1 day, however when batched for 7 days, they pass.

Yes, we are also separating the reports into different batches that are received in production and debug endpoint

[maybellineboon]

Hi @rameetchandok ,

All reports regardless of production or debug endpoint, will need to be batched according to shared ID. If you have a batch where the shared ID both exist in production and debug, you will encounter a privacy budget exhausted error.

For example, you process the debug endpoint batch first and a specific shared ID with the following information gets processed. Any reports in the production endpoint batch with the same shared ID (below information) will return with a privacy budget exhausted error because the budget for that shared ID has already been consumed by the previous batch.

api: attribution-reporting
attribution_destination: https://privacy-sandcastle-dev-shop.web.app
reporting_origin: https://privacy-sandcastle-dev-dsp.web.app
scheduled_report_time (hour): 1704214800
source_registration_time (day): 0
version: 0.1

[rameetchandok]

Hi, but we always process debug batches 1 hour after processing non-debug batches.

[maybellineboon]

Hi @rameetchandok ,

Would you be able to help share the reports you batched? both for the single batch of 7 days and the daily batches for 7 days? Please also include the getJob requests. If you can help put all reports for the same batch in a single folder (below folder structure), this will help us.

batches
 |--7 day batch
 |--daily batch
     |--day 1 batch
     |--day 2 batch
     |--day 3 batch
     |--day 4 batch
     |--day 5 batch
     |--day 6 batch
     |--day 7 batch

[maybellineboon]

Hi @rameetchandok ,

I've downloaded your files. Would you be able to delete your comment since these files are your private files and this is visible publicly?

Also, it's better to discuss this in email. I do believe there's already an email reaching out to your team.