← Back to release summary

Protected Audience: Downsampled forDebugOnly & Increase number of component ads

Category
Miscellaneous
Type
New or changed feature
Status
Proposed (Chrome Proposed)
Intent stage
None

Summary

Downsampled forDebugOnly: The forDebuggingOnly.reportAdAuctionWin() and forDebuggingOnly.reportAdAuctionLoss() (fDO) APIs were added to the Protected Audience (PA) API to allow debugging from within bidding and scoring scripts in PA auctions.  We originally intended on removing these APIs at third-party cookie deprecation (3PCD) time, but received feedback that they were essential for   doing root cause analysis in escalation situations (i.e. critical crash).  We now plan to heavily downsample the API at 3PCD time as follows: they will only send a report with a 1/1000 probability.  Furthermore, if a report is sent, the browser will not send another for 3 years (“lockout”), and if a report is not sent, future calls to the fDO API from the calling origin will be ignored for 2 weeks 90% of the time and 1 year 10% of the time (“cooldown”).  To avoid biasing towards new browser installs (which aren’t in lockout or cooldown), we may place new browser installs initially in a shorter lockout period. For now, until 3PCD, we’ll expose whether a fDO caller is in the “lockout” or “cooldown” periods. Increase number of component ads: Today, PA allows selection of ads containing 20 component ads (aka product level ads).  We plan to increase this number from 20 to 40 as we received feedback that ads with higher numbers of components were critical (e.g. ones that rotate through 3 sets of 12).

Standards & signals

Explainers: https://github.com/WICG/turtledove/pull/1003

View on chromestatus.com