Agenda Request - Cross device attribution options

[csharrison]

Agenda+: Cross device attribution options

I want to discuss the possible ways we could support cross device attribution, along with risks/benefits of various approaches. I want to touch on:

• Choices for how device graphs are used and shared (ecosystem defined, vendor defined, etc)
• Privacy / security / utility implications for various choices
• Possible auxiliary guardrails we could consider

Given that no one in our poll voted against supporting cross device (!), here I am making a baseline assumption that we want to support this. As such, I'd like to dive into how we should support it.

Possible outcomes for this discussion:

• Confirming our high level support for the use-case (i.e. we should jot this down in the doc here)
• Overall group preferences for device graph management
• Group appetite for additional guard rails against abuse

Time

60 mins. Maybe more :)

Links

This section of the IPA explainer goes into some nice non-trivial implications of the IPA model for cross device:
https://github.com/patcg-individual-drafts/ipa/blob/main/IPA-End-to-End.md#unbounded-scope-of-incoming-information
There are a few issues filed against IPA that touch on this:

• Restrictions on match key providers patcg-individual-drafts/ipa#42
• Permissioning layer for match keys patcg-individual-drafts/ipa#39

For a different model of how to do x-device (browser vendor defined device graph), see our old (archived) proposal for ARA:
https://github.com/WICG/attribution-reporting-api/blob/main/archive/cross_device.md

[csharrison]

I'd still like to have this conversation at the F2F.