Aggregation service, ARA browser retries and duplicate reports about aggregation-service HOT 2 CLOSED

Hi @CGossec,

From the Attribution Reportin API Handbook, we can confirm that reports are sent when a browser is online. And should reports fail to send the first time, the report is retried after 5 minutes. And after the 2nd failure, the report is retried again after 15 mins. Should that fail again, the report will not be sent.

With that in mind, we do recommend to wait a bit for late arriving reports to be able to collect all reports for batching. Late reports can be measured by checking the scheduled_report_time and when the report was received. This can help estimate roughly how long you may want to wait for late arriving reports

For duplicate reports (reports with same shared ID), as of the moment, Aggregation Service does not maintain a record of individual processed reports. It is recommended to filter out duplicate reports before sending to Aggregation Service. You can use report scheduled_report_time (rounded to hour) to batch them.

Aggregation Service does keep track of shared ID which is a hash of different fields (api version, reporting origin, destination site, source registration time, scheduled report time). You can also keep track of what has been batched by the fields used in shared id. That way, should a duplicate report arrive late and the reports for the same specific fields has already been batched, you can skip the report as the report will fail due to privacy budget.

from aggregation-service.

Hi @CGossec ,

I'll proceed to close this down. But do let us know should you still have more questions.

Thanks!

from aggregation-service.