FYI: Moving Source Deactivation Step After Top Level Filter Matching

424 views
Skip to first unread message

Akash Nadan

unread,
Mar 25, 2024, 5:41:08 PMMar 25
to Attribution Reporting API announcements

Hi everyone,


We are planning to move the source deactivation step to after the top level filtering matching step starting in M124.


Currently source deactivation takes place after filter matching checks, rate limit/noise checks, and report generation. In certain scenarios, this current flow may allow the API caller to determine if a source was noised. In order to prevent this privacy gap we are planning on moving the source deactivation step to after the filtering matching step.


Moving the deactivation step to earlier in the algorithm may result in API callers getting different reports in certain circumstances (or no report where previously there would have been a report). This will only occur in specific scenarios, which should be rare.


This change does not require any changes from API callers.


Please reach out if you have any questions.


Thanks,

Akash Nadan


Reply all
Reply to author
Forward
0 new messages