Need for batching Aggregatable report in multiple batches

[logicad]

The proposal of Aggregation Service ARA prevents the same aggregatable report to be batched multiple times. (“No duplicates” rule). This prevents us from reprocessing the report for the next use cases.

1. Aggregatable reports will have some delays beyond 1 hour that are due to user actions. At the same time, there is a general need in getting the report as fast as possible as it becomes available, so we would like to process the report a couple of times to ensure we capture the full report that might be missed out by processing it too early.

   1. ex) We want a report from the previous month on the 1st of each month. By processing on the morning of the 1st of the month, some Aggregatable reports might be missed out due to the delay beyond 1 hour. We would then need to reprocess this again the next day to ensure we capture the conversions fully from the previous month.

2. If there are any kind of system errors during the end to end processes, we rerun the report generating process from the start. The “no duplicates” rules will prevent us from any reprocessing that will be required due to any small system errors, and need to build a less error prone system that is very costly.

What are Chrome’s recommendations or plans to meet these needs?

[wualbert17]

FYI, the Aggregation Service team is currently looking into supporting requerying, which could help with this use case. If you're interested, please take a look at privacysandbox/aggregation-service#71.