You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There appears to be a discrepancy in the documentation regarding the unit of measurement for the recency value in the browserSignals object within generateBid().
The browserSignals.recency value inside generateBid() specifies the duration in minutes since the user joined the interest group.
Observation
Based on the values observed in generateBid(), it appears that milliseconds is the more likely correct unit of measurement.
Request for Clarification
Could the correct unit of measurement for the recency value be confirmed and the documentation updated accordingly to ensure consistency across all references?
This clarification would be beneficial for developers implementing the Protected Audience API to avoid potential misinterpretations or errors in their code.
The text was updated successfully, but these errors were encountered:
Thank you for bringing this to our attention. Milliseconds is in fact the correct units for recency. We've update the documentation to correct the units. I'm closing this issue as I think we've addressed it. If you have further concerns, feel free to file another issue. Also, @jungyanl, please add your name and affiliation to your GitHub profile.
There appears to be a discrepancy in the documentation regarding the unit of measurement for the
recency
value in thebrowserSignals
object withingenerateBid()
.Conflicting Information
In the Protected Audience API documentation, it states:
However, in the Extended Private Aggregation Reporting documentation, it states:
Observation
Based on the values observed in
generateBid()
, it appears that milliseconds is the more likely correct unit of measurement.Request for Clarification
Could the correct unit of measurement for the
recency
value be confirmed and the documentation updated accordingly to ensure consistency across all references?This clarification would be beneficial for developers implementing the Protected Audience API to avoid potential misinterpretations or errors in their code.
The text was updated successfully, but these errors were encountered: