Create devtools protocol to fetch registered impressions and registered conversions

[cjzcpsyx]

Currently, the only way to inspect registered impressions or conversions will be through chrome://attribution-internal page.
However, this page can be updated frequently and will not be stable enough to be used as programatic API to be used in testing.
Is there a way to add devtool protocols to fetch all registered impressions and registered conversions?

[apasel422]

Thanks for the request. Since this repository focuses on browser-independent behavior, I believe your request should be reframed in terms of WebDriver support (something we already have a minor integration with), rather than Chromium's DevTools and Attribution Reporting Internals UI, which are browser-specific and not covered by this repository or specification.

It would also help for you to list the specific information about registered/stored sources and reports that you'd like to have access to, and what other operations you'd like to be able to perform using WebDriver. For example, I suspect that you will want to be able to send pending reports immediately.

[cjzcpsyx]

Thanks, the fields we will need to get access to are:

For Impressions:
source_event_id, status, source_origin, destination, report_to, source_type, priority, filter_data, aggregation_keys, debug_key, dedup_keys, reporting_origin, trigger_specs, max_event_level_reports, trigger_data_matching, event_level_epsilon, aggregatable_budget_consumed, debug_cookie_set, aggregatable_dedup_keys

For Conversions:
event_level_status, aggregatable_status, destination, report_to, debug_key, filters, event_triggers, aggregatable_triggers, aggregatable_values, negated_filters, reporting_origin, registration_json

These are the existing fields we use for validation, let me know if these make sense to expose thru API

[apasel422]

@cjzcpsyx Does that mean you don't need access to reports, only triggers?

[cjzcpsyx]

Yes, since reports are send to AdTech endpoint through report API. We are able to get from internal capture of the testing Adtech.
We mainly only need a way to get Source+Trigger programatically. Since these two are kept by chrome only not shared to anywhere. So far the only place having the info is chrome://attribution-internals/