Hi,
In reference to the last call, during which I mentioned that we have three different reporting origins (https://ash.creativecdn.com, https://ams.creativecdn.com, https://sin.creativecdn.com) and some problems related to them. This division is primarily based on geographical factors and is also related to our internal and external infrastructure, legal reasons, and the performance of our platform.
During that call, we identified an issue with registering ARA in response to FFAR requests when the origin of ad was different from the FFAR origin. This problem was related to CORS and can be fixed on our side - thank you @csharrison for the suggestion!

However, there are still two issues we would like to address:

• The recently introduced limitation of Max source reporting origins per source reporting site prevents us from registering ARA source from different reporting-origin for a single publisher origin. Would it be possible to extend this limit to 3?

• What would be the reporting origin for proposed in the issue 289 pending reports registered in the bidding function (registerPendingAggregatableSource) and approved on the banner event? For the Private Aggregation API, the reporting origin is the IG owner.

Thanks in advance,
Michal