Enable third-party cookie access for services with consented users

[erx214]

This issue is to request a functionality to allow the usage of third-party cookie access for our service where we measure ad exposure for our panelists. For our current service we request consent from our panelists and also provide incentives. Our panelists are informed on the type of ad exposure data we receive based on their web activity.

• We suggest an option where we can set a cookie when a registered user visits our panel website.
• The cookie is set by calling a Chrome API
• Chrome will display an additional notification where the user can accept or reject the usage of the cookie/tracking
• If the user accepts the usage then Chrome will add our panel domain to an "inclusion list" which allows the domain to access it's cookies when our service is called from another top-level domain.

Additional options:

• The access can be restricted to a specific cookie name for that domain when the API is called.
• An indicator in Chrome can make the user aware an approved domain is tracking the user on a website.
• The access to the third party cookie could expire after a specific amount of days, where the expiry time will reset each time the user visits the panel website.

[hoodjoshua]

What you've described sounds very similar to the Storage Access API. However, that is generally intended for non-ads targeting/measurement use cases, where the user interacts with an embedded widget that needs access to unpartitioned state, such as cookies, for authentication purposes, and it's unclear where your use case fits in.

The relevance and measurement APIs are the recommended option for ads use cases.

[wanderview]

Can you ask your panelists to install a chrome extension which grants the appropriate cookie exceptions?