Nan Lin

@aroy-nextdoor The source_event_id is allowed to encode an arbitrary information about the ad impression, including things like creative id. Just to clarify, are you asking about collecting event-level reports to...

Thanks for the feedback. One question though, even if you choose to aggregate event-level reports by creative id, what additional information would you expect to get besides the total number...

Another consideration is future extensibility and backwards compatibility. If we support trigger-level bucket for now, and later want to support use cases that need key/value level bucket, we would end...

Please resolve the merge conflicts as well, thanks.

We should also update `Max aggregatable reports per source` in https://github.com/WICG/attribution-reporting-api/blob/main/params/chromium-params.md.

> To clarify, there are two axes on which the same reporting origin can register multiple navigation sources from the same navigation: > > 1. Background _and_ foreground chains >...

@hengtang Per https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-transitional-debugging-reports, the `SameSite` attribute (default value `Lax`) of the `ar_debug` cookie should be set to `None`, which I don't see in the `Set-Cookie` string you shared. Could you...

@feifeiji89 Please resolve the conflict with the main branch, thanks.

Please update https://github.com/WICG/attribution-reporting-api/blob/main/verbose_debugging_reports.md to include the new verbose debug report type as well. cc @akashnadan