WICG/attribution-reporting-api Issues

Last updated Nov 23, 2024, 5:44:56 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#85 Consider adding event-level data for conversion data as opposed to impression data ❌
#176 Aggregate privacy budget tracking / management is difficult ❌
#352 Consider adding padding to payload ❌
#373 Consider allowing intra-source filtering to stop generating aggregatable reports ❌
#461 Explainer could be clearer on filtering operation support ❌
#485 Feedback on epsilon for summary reports ❌
#545 Documenting supported app<->web attribution flows ❌
#586 Consider adding deduping at an aggregation key level ❌
#656 Attribution API issues ❌
#694 Feedback requested on utility with event-level reports' privacy params ❌
#710 Report verification ❌
#724 ‘Extra Report Delay’ for Aggregate API ❌
#806 Editorial: more precise triggering of background requests ❌
#839 Support header registrations on redirects in spec ❌
#880 Multiple Reporting Origins ❌
#900 Flex-event explainer is vague on prioritization ❌
#901 Flex-event explainer doesn't describe handling of trigger debug keys ❌
#905 Flex-event explainer should have an example of report output using defaults ❌
#907 Refine handling of zero-valued max_event_level_reports ❌
#908 Spec should non-normatively explain why event-source expiries are rounded ❌
#1026 Unable to test noise addition using the local aggregation service tool ❌
#1173 Spec is vague on scheduled_report_time serialization ❌
#1216 Header validator should use bigint instead of number for numStates ❌
#1230 Add documentation about event-level epsilon to the main explainer ❌
#1265 Flex event explainer doesn't describe how debug reports are affected ❌
#1266 Flexible event-level explainer doesn't describe how "Max event-level reports per attribution destination" is affected ❌
#1278 Flexible event-level explainer doesn't describe how randomized response is affected ❌
#1279 Feedback on consolidating Coordinator Services ❌
#1287 Consider only calling attributed reporting origin limit once per trigger ❌
#1357 Online-to-Offline attribution ❌
#1381 Proposal for registering triggers in S2S ❌
#1401 Event-level report prioritization and deduplication interact unintuitively ❌
#1405 Specification is inconsistent with regard to handling of non-monotonic time ❌
#1437 [feature request] Batched source events ❌
#1452 Allow separate privacy budgets for embedded domains ❌