Skip to content
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

Closed

Conversation

giladbarkan-github
Copy link
Collaborator

@giladbarkan-github giladbarkan-github commented Oct 17, 2024

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

index.bs Outdated Show resolved Hide resolved
ts/src/constants.ts Outdated Show resolved Hide resolved
ts/src/header-validator/source.test.ts Outdated Show resolved Hide resolved
@apasel422
Copy link
Collaborator

Please also reference #1183 in the PR description.

@giladbarkan-github
Copy link
Collaborator Author

Please also reference #1183 in the PR description.

Done.

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
@linnan-github
Copy link
Collaborator

We should also update Max aggregatable reports per source in https://github.com/WICG/attribution-reporting-api/blob/main/params/chromium-params.md.

@giladbarkan-github
Copy link
Collaborator Author

We should also update Max aggregatable reports per source in https://github.com/WICG/attribution-reporting-api/blob/main/params/chromium-params.md.

Done.

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
ts/src/constants.ts Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
ts/src/constants.ts Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
@giladbarkan-github giladbarkan-github changed the title Add support for source max_aggregatable_reports Unlimited aggregatable reports with trigger context ID Oct 30, 2024
@apasel422 apasel422 requested a review from johnivdel October 30, 2024 19:12
@@ -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:
Copy link
Collaborator

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants