attribution-reporting-api icon indicating copy to clipboard operation
attribution-reporting-api copied to clipboard

Detecting Invalid Traffic with Attribution and Aggregate Reporting

Open SpaceGnome opened this issue 4 years ago • 5 comments
trafficstars

Detecting invalid traffic (IVT) is an essential part of the ads ecosystem and often relies on:

  • Human Analysis for manual investigations, discovering new attacks and developing new IVT models
  • Training and deploying Automated IVT detection models

However, the use of aggregated reporting within Attribution Reporting API with Aggregate Reports makes the above IVT use cases challenging. We’ve written up a proposal called ASTRAPIA to address these key IVT detection use cases (although the ASTRAPIA proposal is currently written for FLEDGE, it could also be generalized for Attribution Reporting with Aggregate Reporting too).

We look forward to further discussing ASTRAPIA or other ideas for supporting Attribution Reporting and IVT detection either here or as an issue in https://github.com/google/ads-privacy/issues. Thanks!

SpaceGnome avatar Sep 16 '21 18:09 SpaceGnome

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

csharrison avatar Nov 15 '21 00:11 csharrison

Thanks @csharrison - let me plan to add this to the agenda for December.

SpaceGnome avatar Nov 15 '21 19:11 SpaceGnome

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

csharrison avatar Nov 29 '21 21:11 csharrison

Yes, that sounds great @csharrison!

SpaceGnome avatar Nov 29 '21 23:11 SpaceGnome

Detecting invalid traffic (IVT) is an essential part of the ads ecosystem and often relies on:

  • Human Analysis for manual investigations, discovering new attacks and developing new IVT models
  • Training and deploying Automated IVT detection models

However, the use of aggregated reporting within Attribution Reporting API with Aggregate Reports makes the above IVT use cases challenging. We’ve written up a proposal called ASTRAPIA to address these key IVT detection use cases (although the ASTRAPIA proposal is currently written for FLEDGE, it could also be generalized for Attribution Reporting with Aggregate Reporting too).

We look forward to further discussing ASTRAPIA or other ideas for supporting Attribution Reporting and IVT detection either here or as an issue in https://github.com/google/ads-privacy/issues. Thanks!

Duplicate of #

Abdullah9aleh avatar Dec 20 '21 14:12 Abdullah9aleh