Private Aggregation API breaking changes for Protected Audience API

891 views
Skip to first unread message

Kevin Lee

unread,
May 17, 2023, 12:50:09 PM5/17/23
to FLEDGE API announcements

To reflect the Protected Audience name change, Private Aggregation API will contain the following breaking changes in the M115 Stable release:

  1. The reporting endpoint is changed from /.well-known/private-aggregation/report-fledge to /.well-known/private-aggregation/report-protected-audience

  2. The api property value of the aggregatable report payload is changed from fledge to protected-audience


You must update your code to ensure that the Private Aggregation API continues to work with the Protected Audience API. Users  in an outdated Chrome instance will still send their report to the legacy endpoint, so you should ensure backward compatibility to collect all reports. 


The new endpoint and api property value will be available for testing on Monday, May 22nd in M115 Canary and Dev channels.


If you have any questions or comments, reply to this post or open an issue in the Privacy Sandbox Dev Support repository on GitHub.


Reply all
Reply to author
Forward
0 new messages