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.

Sign up for GitHub

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

Jump to bottom

Consider variable conversion metadata buckets #99

Closed
csharrison opened this issue Jan 13, 2021 · 2 comments
Closed

Consider variable conversion metadata buckets #99

csharrison opened this issue Jan 13, 2021 · 2 comments

Comments

@csharrison
Copy link
Collaborator

The current explainer for the event-level API discusses 3 bits of conversion data, with 5% noise applied — that is, with 5% chance, we send a random 3 bits, and the other 95% of the time we send the real conversion data. This is pretty inflexible.

Instead, we could consider a smooth trade-off between the number of unique ids on the conversion data(3 bits has 8 ids) and the amount of noise(here uniform 5%). Ad-tech can have the flexibility to choose the maximum number of ids and browsers would add noise accordingly to maintain similar levels of privacy.
@shigeki
Copy link
Contributor

shigeki commented Jan 14, 2021

It would be great for us to have this even if the noise ratio is increased since the current 3 bits are too small for us to use for the ad measurements.
We need at least 6 bits for the conversion data.

@csharrison
Copy link
Collaborator Author

We are proposing a "flexible event" API that solves this issue:
https://github.com/WICG/attribution-reporting-api/blob/main/flexible_event_config.md

Closing for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@shigeki @csharrison @maudnals