Charlie Harrison

> I guess supporting gaussian noise instead of a laplacian one would improve the utility of the API when reporting over a few dimensions. Similarly, what we discussed before about...

1. The API provides a way to receive [aggregatable reports](https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md#aggregatable-reports). These reports are delayed for up to 1 hour before sending over the network to a particular endpoint. The limit...

+1 we should align this as best as possible with https://github.com/WICG/conversion-measurement-api/issues/261

We spoke about this in the meeting on 2021-12-13 ([minutes](https://github.com/WICG/conversion-measurement-api/blob/main/meetings/2021-12-13-minutes.md#charlie-harrison-require-html-attribute--script-access-for-conversion-pings)). If we align this we could do something like ```html ``` This would invoke a fetch just like the `attributionsrc`...

Hey @SpaceGnome would you like to present this topic in a future WICG call? See https://github.com/WICG/conversion-measurement-api/issues/80 for our meeting schedule

I added this to the agenda for our next meeting on Dec 13. Can you make it?

Thanks this is something we are considering, but we need to weigh it with the increase in complexity for the servers. The current design of a fixed histogram allows a...

No, `registerAttributionSource` and the other APIs that trigger `event` sources shouldn't require activation, it would jeopardize the view-through use-case.

Thanks @lbdvt for filing. I added a line for the Attribution Reporting API and would be happy to facilitate discussion. Let's use this issue to craft an agenda. cc @johnivdel

@apasel422 do you think you could take a look at this? I know you were discussing simplifying this doc given a lot of information is in the spec now.