-
Notifications
You must be signed in to change notification settings - Fork 159
Issues: WICG/attribution-reporting-api
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Choice of parameters in the aggregation API
possible-future-enhancement
Feature request with no current decision on adoption
#249
opened Oct 11, 2021 by
alois-bissuel
Consider adding event-level data for conversion data as opposed to impression data
possible-future-enhancement
Feature request with no current decision on adoption
#85
opened Nov 18, 2020 by
csharrison
False-positive event reporting conflicts with fraud prevention
anti-fraud / auth
possible-future-enhancement
Feature request with no current decision on adoption
#111
opened Feb 22, 2021 by
eriktaubeneck
Integration-minimalistic reporting for advertisers
possible-future-enhancement
Feature request with no current decision on adoption
#119
opened Mar 11, 2021 by
piwanczak
aggregate reporting helper service threat model
aggregate
anti-fraud / auth
#157
opened Jun 4, 2021 by
erik-anderson
Aggregate privacy budget tracking / management is difficult
possible-future-enhancement
Feature request with no current decision on adoption
#176
opened Jul 8, 2021 by
csharrison
event_attribution_reporting_clicks.md is very hard to follow.
documentation
#188
opened Jul 19, 2021 by
MattMenke2
Description of our usage of the measurements APIs
developer-input
Question/feedback raised by a developer and posted here on their behalf for public discussion
#191
opened Jul 22, 2021 by
BasileLeparmentier
Clarify cache and viewport behavior in view-through event
documentation
#211
opened Sep 9, 2021 by
shigeki
Preventing conversion fraud: trust token integration w/ event-level API
anti-fraud / auth
possible-future-enhancement
Feature request with no current decision on adoption
#13
opened Nov 7, 2019 by
csharrison
Network Partition Key for reports is not specified
documentation
#220
opened Sep 14, 2021 by
MattMenke2
Aggregation Service: GROUP BY support
possible-future-enhancement
Feature request with no current decision on adoption
#256
opened Oct 18, 2021 by
JonathanAquino-NextRoll
What are your expectations of feature development and feature testing for the aggregation service?
#327
opened Feb 16, 2022 by
palenica
Does "batch disjointness" offer enough flexibility?
possible-future-enhancement
Feature request with no current decision on adoption
#331
opened Feb 16, 2022 by
palenica
Are there changes to the aggregation model that could make it useful for training machine learning models?
possible-future-enhancement
Feature request with no current decision on adoption
#332
opened Feb 16, 2022 by
palenica
Consider adding padding to payload
possible-future-enhancement
Feature request with no current decision on adoption
#352
opened Mar 4, 2022 by
alexmturner
When rounding source_registration_time, would adtech want to specify the timezone
Looking for feedback
possible-future-enhancement
Feature request with no current decision on adoption
#356
opened Mar 10, 2022 by
palenica
Consider allowing intra-source filtering to stop generating aggregatable reports
possible-future-enhancement
Feature request with no current decision on adoption
#373
opened Mar 28, 2022 by
johnivdel
App-to-Web Click Source Registration
app-to-web
developer-input
Question/feedback raised by a developer and posted here on their behalf for public discussion
#1313
opened May 31, 2024 by
jfggit
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.