- From: Bosko Milekic via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Feb 2022 20:54:29 +0000
- To: public-patcg@w3.org
> If Twitter wants to use Facebook's match keys, that means all the users they show adverts to also need to be logged in to Facebook. This means Twitter needs to incentivise its users to log in to Facebook which directly benefits Facebook. I don't see how that's true. If Twitter is the publisher, then it can ask their advertisers to register _trigger_ events referencing only twitter's match keys. There is no need for the facebook match keys in that scenario, especially since the ads are running on twitter and so the lack of twitter user ID implies no possible match with advertiser _target_ events. For non-FB smaller publishers, the proposal provides an important theoretical benefit, in that a publisher can choose to register _source_ events leveraging facebook, twitter, and other third-party keys. In an IPA implementation supporting multiple match keys, this ultimately benefits the publisher as it increases potential match rates with advertiser data. It remains to be seen what the motivation could be for a match key provider to act as such, but presumably "having an advertising business" would be one motivating reason. I believe that making the match keys usable by other parties in that context is more fair than doing the opposite. -- GitHub Notification of comment by bmilekic Please view or discuss this issue at https://github.com/patcg/proposals/issues/2#issuecomment-1039546994 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 February 2022 20:54:31 UTC