Shigeki Ohtsu

SW error when accessing via SXG

3

**Describe the bug** ampbyexample has a ServiceWorker error when accessing via SXG. Please refer console.log in the attached screenshot below.

It seems that a third-party token can not be valid as the wrong origin when it is written in the document as the first-party origin token. If so, please clarify...

Multiple attribution domains under one eTLD+1

7

Note that words here follow old terminology. In Chrome 89, a conversion destination is stored as a schemeful site of eTLD+1. We have multiple service domains under one eTLD+1, and...

Yahoo! JAPAN's Feedback of Origin Trial

8

We, Yahoo! JAPAN, had started a large-scale origin trial (OT) of CMAPI in our production ad services to test CMAPI performances compared to our existing measurements by 3p cookie, through...

Clarify cache and viewport behavior in view-through event

1

The current explainer of event-level reports for views does not mention if the attribution source is registered when it is viewed after back navigation with BFCache. It should also add...

Consider the case of the same priority in event and navigation

1

For example, in the case of `Ad View and Click` , both source type event(view) and navigation(click) have the same priority. Usually, a user clicks the ad after viewing and...

FLoC features after OT

3

FLoC OT was already finished, but some users still test FLoC with manually enabled options. I had an issue that they have the wrong cohort id from unexpected histories when...