Baseline Attribution Reporting API Menu Element in Privacy Sandbox Analysis DevTools panel

[amedina]

Feature Request

Description: Today, ad conversion measurement often relies on third-party cookies. The Attribution Reporting API (ARA) enables to collect such measurements in a privacy-preserving way; that is, without third-party cookies. Specifically, this API enables advertisers and ad tech providers to measure conversions in the following cases:

• Ad clicks and views.
• Ads in a third-party iframe, such as ads on a publisher site that uses a third-party ad tech provider.
• Ads in a first-party context, such as ads on a social network or a search engine results page, or a publisher serving their own ads.

Motivation: The goal of this feature is to include an Attribution Reporting API Menu Element in the DevTools PS Analysis panel, initially surfacing information from chrome://attribution-internals, and progress from there to enable users of the extension to learn about the API in an user-friendly way, and debug its use cases.

The ARA Menu Element can also capture information and insights provided in prior demos such as this and this.

Acceptance Criteria:

• [ ] Attribution Reporting API tab
• [ ] Add API Info Card
• [ ] Show information from chrome://attribution-internals/
• [ ] Show information from Demo (if applicable)
• [ ] Allow to modify the topics (check if this would be possible)

Additional Information:

• Attribution Reporting
• Why Chrome plans to ship the Attribution Reporting API
• Private Attribution
• Interoperable Private Attribution

[mohdsayed]

I am thinking how we would get data from chrome://attribution-internals/. I did a quick attempt by injecting a script into that page through the service worker, but it seems to function properly on all tabs except for this one.

chrome.tabs.onUpdated.addListener((tabId, changeInfo, tab) => {
  if (
    changeInfo.status === 'complete' &&
    tab.url === 'chrome://attribution-internals/'
  ) {
    chrome.scripting
      .executeScript({
        target: { tabId: tabId },
        func: () => {
          // Do window operations here.
        },
      })
      .then((result) => {
        // work with the result.
      });
  }
});

throws the following error

Uncaught (in promise) Error: Cannot access a chrome:// URL

Looks like accessing internal pages like chrome://attribution-internals/ have limitations due to the security restrictions imposed by Chrome extensions.

[apasel422]

I am thinking how we would get data from chrome://attribution-internals/.

I am actively working on exposing Attribution Reporting data and events in the DevTools protocol, e.g. source-registration events.