jonasz / product_level_turtledove

8 stars 0 forks source link

Product ids in reporting #5

Open JeremyMorvan opened 4 years ago

JeremyMorvan commented 4 years ago

Combinatorics associated with a protected reporting (e.g. by differential privacy or k-anonymity) would certainly make most product ids unlikely to appear in reports.

How do you think this proposal should be incorporated within TURTLEDOVE or SPARROW reporting?

jonasz commented 4 years ago

In general, I think that creating aggregate reports on the product level (as opposed to the creative level) would be a natural and effective reporting strategy when leveraging product-level mechanisms in Turtledove.

Combinatorics associated with a protected reporting (e.g. by differential privacy or k-anonymity) would certainly make most product ids unlikely to appear in reports.

I was wondering, when you mention combinatorics, do you see a need for reporting aggregates for the collections of products displayed in ads: 1) "an ad containing product 17, 24, 88 and 113 was shown N times",

as opposed to reporting aggregates for each product separately?

2) "Product 17 appeared in X impressions, product 24 in Y impressions, ..."