Translate IVT from source to trigger

[baz1]

Hello,

An important feature that the Google Ad Traffic Quality team would like the APIs to support is the ability to translate IVT (Invalid Traffic) decisions from source to trigger. We currently rely on some defenses that, in some cases, mark conversions as invalid when attributed to an invalid click. Such translation also needs to be accessible for IVT identified at various latencies.

In the current state of the attribution reporting APIs, such IVT translation is supported out-of-the-box in the event-level API. The only solution on the aggregate side would be to make the IVT decision at click time, and opt-out of using the API for invalid clicks, which does not satisfy the requirements below).

The requested feature would support the following capabilities in the aggregate API:

• Conversion counts can be re-queried 3 times, to account for late-IVT
• The latest re-computation could happen up to one month after the source event
• For each computation, the AdTech organization can provide a list of valid or invalid source events to include/exclude in the aggregates
• Optionally, also be able to measure the amount of invalid conversions, instead of just valid conversions