-
Notifications
You must be signed in to change notification settings - Fork 173
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
[Event-level] Noise level and intermediate reporting windows #734
Comments
This feels very reasonable to me, @alois-bissuel . Thanks for the suggestion, I agree it only makes sense to "pay for" the windows that you could possibly use for a given source. I think the only major consideration to me is spec/implementation complexity, which we can investigate. |
@alois-bissuel would you be willing to discuss this in the next meeting on Monday? |
With pleasure! |
Great, I think this dovetails nicely into our recent publication of the flexible event-level configurations, which we are hoping to discuss as well: This proposal is a "lite" version of that design which attempts to offer much more flexibility. |
Thanks @alois-bissuel for sharing the proposal. This is a very interesting idea to achieve configurability in the event API. This proposal would be very useful for Google ads as this gives us 2 benefits
|
Hello,
The noise level is fixed for clicks (ie navigation sources) at 0.24%.
If we follow the randomized response mechanism described in the Differential privacy section, the noise level depends on the number of possible output states of the API, which itself depends on the number of intermediate reporting windows.
If we use an attribution window of less than 2 days, the number of possible state is
((8+3) choose 3) = 165
. According to the randomize response mechanism, the noise level with the selected epsilon value of 14 should be 0.01372% (which is far from the 0.24% for three intermediate windows).For two intermediate reporting windows, the number of possible states is 969 and the noise level should read 0.08051%.
Would it be possible to change the noise level based on the attribution window length? Otherwise I think this puts users of the event-level API who choose it to report only on short attribution windows at a disadvantage.
The text was updated successfully, but these errors were encountered: