Skip to content
This repository has been archived by the owner on Oct 30, 2020. It is now read-only.

Product ids in reporting #5

Open
JeremyMorvan opened this issue Jul 29, 2020 · 1 comment
Open

Product ids in reporting #5

JeremyMorvan opened this issue Jul 29, 2020 · 1 comment

Comments

@JeremyMorvan
Copy link

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
Copy link
Owner

jonasz commented Aug 11, 2020

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?

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

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

No branches or pull requests

2 participants