privacycg / private-click-measurement

Private Click Measurement
https://privacycg.github.io/private-click-measurement/
196 stars 8 forks source link

Attribution report delay > 48hrs #100

Closed cedelman closed 2 years ago

cedelman commented 2 years ago

It's expected attribution reports send after the 24-48 reporting delay window if Safari is closed. During testing it was discovered many reports were not delivered until roughly one month later. The graph below shows a trend of a trigger data value (gray line) over time after the value was removed from trigger logic on 1/25. It is a concern so many reports deliver after 48 hours. Has this behavior been noticed in any testing for other PCM API users?

image

1) Is there a test/debug solution that can be built into PCM to track at a finer grain level to help debug? Current debug solutions automatically send reports which isn't helpful to test reporting delay. 2) Event level reports that are received much later than 48 hours may not be useful for certain reporting use cases. Could reports older than a threshold outside the 48 hour window be dropped if desired, either by default or via a config set on the source event?

johnwilander commented 2 years ago

This looks like a Safari/WebKit-specific report. This GitHub repo is for the standards discussion, not specific engine implementations. Please file at https://bugs.webkit.org and cc me. Thanks!