Now that FLEDGE has been renamed to the Protected Audience API (see the blog post), we should update references in the API's operation. (We also should update references in the explainer and spec text -- e.g. see PR #34.)
Specifically, we're planning to replace the "api": "fledge" field in reports with "api": "protected-audience". We also plan to change the reporting path for aggregatable reports triggered in Protected Audience auctions from /.well-known/private-aggregation/report-fledge to /.well-known/private-aggregation/report-protected-audience.
Please let us know if you have any thoughts on this change!
Now that FLEDGE has been renamed to the Protected Audience API (see the blog post), we should update references in the API's operation. (We also should update references in the explainer and spec text -- e.g. see PR #34.)
Specifically, we're planning to replace the
"api": "fledge"field in reports with"api": "protected-audience". We also plan to change the reporting path for aggregatable reports triggered in Protected Audience auctions from/.well-known/private-aggregation/report-fledgeto/.well-known/private-aggregation/report-protected-audience.Please let us know if you have any thoughts on this change!