← Back to release summary

Fenced Frames M120 functionality updates

Category
Miscellaneous
Type
No developer-visible change
Status
Enabled by default (Chrome 120)
Intent stage
None

Summary

1) Additional format option for Protected Audience ad size macros In the Protected Audience API within the Privacy Sandbox, there is an opt-in feature that allows you to macro the size of the ad that wins the auction into the ad’s url, like: https://ad.com?width={%AD_WIDTH%}&height={%AD_HEIGHT%} (See https://github.com/WICG/turtledove/pull/417 for more details.) To be more consistent with other types of macros in Protected Audience, like those used by deprecatedReplaceInURN and registerAdMacro, in M120 we’re adding the ability to use ${AD_WIDTH} and ${AD_HEIGHT} as the format for the macros in addition to the current format. 2) Automatic beacons will now send to all registered URLs. Previously, only destinations specified when calling setReportEventDataForAutomaticBeacons() receive automatic beacons, even if that destination called registerAdBeacon() for "reserved.top_navigation" in their worklet. Now, any destination that called registerAdBeacon() for "reserved.top_navigation" will get an automatic beacon, but only destinations specified in setReportEventDataForAutomaticBeacons() will get automatic beacon data along with the beacon. The "once" parameter in setReportEventDataForAutomaticBeacons() will now determine whether the data is sent out once, rather than determine if the entire beacon is sent once.

Standards & signals

View on chromestatus.com