Hi,

For approximately 6% of all attempts to register ARA sources, we encounter the source-storage-limit. For PCs, it reaches 10% (for phones, it's about 3%).
For some source websites (often those for which we display the most ads), it goes above 20% (up to a maximum of 33%).

As ARA is only being tested on a small scale, and more ad tech companies are likely to use it as 3rd-party cookies phase out, this problem is becoming more noticeable. Especially, bigger players with lots of ads and partners could hit the limit, preventing new registrations until old ones expire.

Maybe a good solution would be to introduce a storage limit that also considers the reporting origin. Additionally, it seems important to have a mechanism that allows overwriting or deleting previous registrations.

Another idea is to define separate limits for different types of ARA sources (event, navigation). For instance, an event-type event can be registered multiple times, even without any user interaction, unlike navigation events.

Best regards,
Michal