Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detecting Invalid Traffic with Anonymization and Aggregated Reporting #35

Open
SpaceGnome opened this issue Sep 16, 2021 · 2 comments
Open

Comments

@SpaceGnome
Copy link

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 anonymization and aggregated reporting within PARAKEET 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 PARAKEET too).

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

@SpaceGnome
Copy link
Author

Can we add the topic of Invalid Traffic detection requirements for PARAKEET to the October 6 call? Thanks!

@KeldaAnders
Copy link
Contributor

@SpaceGnome, confirming that we have added this to the agenda for Oct 6th.
-#3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants