Private Aggregation API (and Extended API) Availability

[maleangrubb]

Hello,
During prototyping some use of the Private Aggregation API (and the extended Private Aggregation API) I ran into some confusion regarding the rollout of some of the new method names discussed in a June 1 update to https://developer.chrome.com/docs/privacy-sandbox/private-aggregation/

While prototyping, some of the methods and functionality seemed to not be available (were called, but no responses from Chrome received in Stable, Canary, or Beta), specifically privateAggregation.contributeToHistogram and privateAggregation.contributeToHistogramOnEvent.

Additionally, I attempted to configure both a test seller and test buyer for receiving "latency-stats" & "interest-group-counts" as discussed in https://github.com/WICG/turtledove/blob/main/FLEDGE_extended_PA_reporting.md#triggering-reports with no results. Is that functionality available?

For a quick overview of how that was set up, I had the test buyer set up to add:

sellerCapabilities: { '*': ['interest-group-counts', 'latency-stats'] },

to the interest group in navigator.joinAdInterestGroup() and set up the test seller to request "latency-stats" and "interest-group-counts" in the auctionConfig by adding the following to the auctionConfig:

auctionReportBuyers: { interestGroupCount: { bucket: 0n, scale: 1, }, totalGenerateBidLatency: { bucket: 2n, scale: 1, }, },

[JensenPaul]

@alexmturner might be able to help. For Chrome implementation bugs/issues I might advise filing a bug via crbug.com which will help us diagnose this by asking useful questions like the Chrome version being used and if you can provide a URL that reproduces the problem.

[alexmturner]

Hi @maleangrubb, did the javascript functions exist (i.e. were not undefined)? If they were undefined, you may be using an Chrome version before the changes or without the flags necessary to enable them. But, if they were defined, something else is going on: this functionality should all be available (with the latest status available here).

You should be able to view any pending reports at the chrome://private-aggregation-internals debug page. If that page is open when a report is sent/attempted to be sent, you will also see whether it sent successfully or had a network error of some kind.

Happy to take a look at a URL that reproduces the problem, but yes crbug.com is probably the better venue for this :)