Update README.md
Browse files
README.md
CHANGED
@@ -66,7 +66,9 @@ companion paper](https://arxiv.org/abs/2502.12103)
|
|
66 |
|
67 |
This dataset represents a 100M anonymised sample of 30 days of Criteo
|
68 |
live data retrieved from third-party cookie traffic on Chrome. Each line corresponds to one impression (a banner)
|
69 |
-
that was displayed to a user.
|
|
|
|
|
70 |
|
71 |
- campaign x publisher x (user x day) granularity with respective ids, to match Chrome Privacy Sandbox scenarios and both
|
72 |
display and user-level privacy.
|
@@ -108,7 +110,6 @@ display and user-level privacy.
|
|
108 |
- We include a display order from 1 to K for display on the same day
|
109 |
for the same user.
|
110 |
|
111 |
-
CriteoPrivateAd is split into 30 parquets (one per day from 1 to 30) in day_int={i} directory.
|
112 |
The displays-per-user histograms can be deduced from event_per_user_contribution.csv. It is useful to build importance sampling ratios and user-level DP, as it is detailed in the companion paper.
|
113 |
|
114 |
|
|
|
66 |
|
67 |
This dataset represents a 100M anonymised sample of 30 days of Criteo
|
68 |
live data retrieved from third-party cookie traffic on Chrome. Each line corresponds to one impression (a banner)
|
69 |
+
that was displayed to a user. It is partionned by day (`day_int`) to facilitate exploration, model seeding and train/validation/test split.
|
70 |
+
|
71 |
+
For each impression, we are providing:
|
72 |
|
73 |
- campaign x publisher x (user x day) granularity with respective ids, to match Chrome Privacy Sandbox scenarios and both
|
74 |
display and user-level privacy.
|
|
|
110 |
- We include a display order from 1 to K for display on the same day
|
111 |
for the same user.
|
112 |
|
|
|
113 |
The displays-per-user histograms can be deduced from event_per_user_contribution.csv. It is useful to build importance sampling ratios and user-level DP, as it is detailed in the companion paper.
|
114 |
|
115 |
|