You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
Detecting invalid traffic (IVT) is an essential part of the ads ecosystem and often relies on:
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!
The text was updated successfully, but these errors were encountered: