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

Feedback requested on utility with event-level reports' privacy params #694

Open
csharrison opened this issue Feb 2, 2023 · 1 comment

Comments

@csharrison
Copy link
Collaborator

csharrison commented Feb 2, 2023

The privacy of event-level reports are parametrized primarily by three factors:

  • How many attribution reports can be generated by an ad impression
  • How many bits of metadata attribution reports can embed
  • How many distinct reporting windows are available. Note that more windows allows for shorter delays in the API if conversions occur in early windows.

We’re looking into whether our current parametrization makes sense, so we’re looking for information about:

  • Which of these aspects are most important to you (e.g. you’d trade off bits of metadata with more reporting windows, or a stack ranking of these dimensions)
  • Example parameterizations which would satisfy your critical MVP use-cases

Note that we're open to feedback about both the CTC and VTC use-cases / params.

@csharrison
Copy link
Collaborator Author

FYI here is a calculator for how the flip probability changes based on an epsilon parameter (in the existing parameterization this is set at 14):
https://docs.google.com/spreadsheets/d/1Eh8Vzpju2odDN6ivA6_vZcbtMtU3LzuD0pOePnKjuAc/edit?usp=sharing

Feel free to copy this spreadsheet and play around with the values to get a sense of how this changes based on the above parameters.

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

No branches or pull requests

1 participant