Skip to content

Commit

Permalink
Fix generateBid()'s broser signal's recency unit to milliseconds
Browse files Browse the repository at this point in the history
  • Loading branch information
qingxinwu authored Jan 9, 2025
1 parent 7f754f0 commit 24af79a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion FLEDGE_extended_PA_reporting.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ with an arbitrary `event_key` within `generateBid`, `scoreAd`, `reportWin`, and
We consider the scenario where a buyer wants to learn the click-through rate of ads when a user has
been in an interest group for a given time.

To generate the bucket that represent interest group age, the buyer may implement `getImpressionReportBucket()` and `getClickReportBucket()` functions which return buckets that map an interest group and the time the user has spent in that interest group to a 128-bit integer as `BigInt`. The `browserSignals.recency` value inside `generateBid()` specifies the duration in minutes since the user joined the interest group.
To generate the bucket that represent interest group age, the buyer may implement `getImpressionReportBucket()` and `getClickReportBucket()` functions which return buckets that map an interest group and the time the user has spent in that interest group to a 128-bit integer as `BigInt`. The `browserSignals.recency` value inside `generateBid()` specifies the duration in milliseconds (rounded to the nearest 100 milliseconds) since the user joined the interest group.

Once the buckets have been derived, the buyer can call Private Aggregation inside `generateBid()`:

Expand Down

0 comments on commit 24af79a

Please sign in to comment.