-
Notifications
You must be signed in to change notification settings - Fork 176
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
Unlimited aggregatable reports with trigger context ID #1449
Unlimited aggregatable reports with trigger context ID #1449
Conversation
Please also reference #1183 in the PR description. |
Done. |
We should also update |
Done. |
58001bf
to
3e1743a
Compare
@@ -4149,7 +4149,7 @@ To <dfn>trigger aggregatable attribution</dfn> given an [=attribution trigger=] | |||
1. If the result of running [=check if attribution should be blocked by rate limits=] | |||
with |trigger|, |sourceToAttribute|, and |rateLimitRecord| is not null, | |||
return it. | |||
1. If |sourceToAttribute|'s [=attribution source/number of aggregatable attribution reports=] value is equal to [=max aggregatable reports per source=][0], then: | |||
1. If |sourceToAttribute|'s [=attribution source/number of aggregatable attribution reports=] value is equal to [=max aggregatable reports per source=][0] and |trigger|'s [=attribution trigger/trigger context ID=] is null, then: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we update the name and/or definition of max aggregatable reports per source
to make it clear that it only applies without trigger context IDs?
The current hard limit on aggregatable reports per source might be too small for
some use-cases. Allowing consumers to configure it allows for more flexibility
in handling the utility implications of higher limits that would also garner
more constraints due to privacy.
(See also #1183)
Preview | Diff