[meetings] Agenda Request: Experiment to better understand the effect of DP on advertising decision making (#155)

eriktaubeneck has just created a new issue for https://github.com/patcg/meetings:

== Agenda Request: Experiment to better understand the effect of DP on advertising decision making ==
## Agenda+: Experiment to better understand the effect of DP on advertising decision making

We’ve been exploring how to measure the effect of Differential Privacy at different parameterizations, and are seeking feedback on a test that we’ve designed. We are attempting to isolate the effect of adding noise on decision making. More specifically, given some decision making process D(x) (for some input variables x), how does D(x’) change for noised x’?

We build this [small game](https://dp-game.vercel.app/) which simulates conversion measurement results from hypothetical campaigns. Those results are then duplicated and have Laplace noise added to make them differentially private. These results are all presented to the user, in random order, with a simple binary decision: increase spend or decrease spend. After the user completes the round, it will measure how often the same decision was made for both x (the true simulated data) and x’ (the noised version of x).

We expect that as ε increases, the ability to make the same decision should approach 50% (pure random chance.)



## Time
45-60 min
For this agenda item, we want to cover three areas:
1. An overview of the game and the test we want to run with it. (15-20 min)
2. Feedback on the design of the game (e.g. parameterization, simulation process.) (15-20 min)
3. Feedback on running an experiment (e.g. who to recruit, how many participants we’d want, help finding participants.) (15-20 min)


### Links

[Differential Privacy Game](https://dp-game.vercel.app/) (early prototype, [open issues here](https://github.com/eriktaubeneck/dp-game/issues) if you find bugs!)


Please view or discuss this issue at https://github.com/patcg/meetings/issues/155 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 18 October 2023 16:55:27 UTC