Additional Private Aggregation API breaking changes for Protected Audience API
Kevin Lee
Private Aggregation is making more breaking changes in M115, in additional the previously announced breaking changes.
The following changes are planned to go live on Canary on Saturday May 27th 2023. They will also be available with the M115 Beta and Stable releases (first Beta release planned for Wednesday May 31st 2023).
sendHistogramReport() is being renamed to contributeToHistogram()
reportContributionForEvent() is being renamed to contributeToHistogramOnEvent() (only relevant for reports from Protected Audience auctions).
enableDebugMode()’s debug_key parameter is being renamed to debugKey.
You must update your code to ensure that the Private Aggregation API continues to work. Outdated Chrome instances will still use the old names, so you should ensure backward compatibility to collect all reports. We recommend using feature detection in your code with if ('contributeToHistogram' in privateAggregation)).
Other changes
We’d also like to highlight two other changes coming in M115:
Contribution budgeting is changing from a “per-origin per-day” scope to a “per-site per-10-min” scope, with a looser “per-site per-day” backstop; see the GitHub issue for more detail.
Contributions from Protected Audience auctions will now be batched together to reduce report volume, see the explainer for more detail.
If you have any questions or comments, reply to this post or open an issue in the Privacy Sandbox Dev Support repository on GitHub.