They could! But they'd have to fire it in game at the appropriate point. And presumably pass along chain-related state--value of the NFT, or whatever else the user did--to FB.
They could! But they'd have to fire it in game at the appropriate point. And presumably pass along chain-related state--value of the NFT, or whatever else the user did--to FB.
kk. For on-chain events I can imagine a world where advertisers don't need to do any instrumentation and attribution will just work (and that will be wonderful). For off-chain events (which as you rightly argue are also important) I guess I haven't grasped how a web3 advertiser is fundamentally different from a web2 advertiser (who also need to instrument events etc).
The bit that gets me excited about the intersection of web3 and ads is does it open the door to a better agent of the user in terms of representing their preferences for what data can be used by whom for what purposes and giving that control into the hands of the user, instead of today being hypocritically represented by their device / browser vendors
Yes, for v1 of such a system, you don't need device-side SDKs that track attribution events...you can use existing (clunky) tooling around chain querying to get most of what you need.
Re: the future of web 3 and data privacy, it's not clear who would emerge as the obvious user champion. Most (normie) users won't care enough to bother (as they don't in web 2), but someone in the stack will offer privacy as a product (even if only for marketing purposes).
They could! But they'd have to fire it in game at the appropriate point. And presumably pass along chain-related state--value of the NFT, or whatever else the user did--to FB.
But yes, you could kludge it.
kk. For on-chain events I can imagine a world where advertisers don't need to do any instrumentation and attribution will just work (and that will be wonderful). For off-chain events (which as you rightly argue are also important) I guess I haven't grasped how a web3 advertiser is fundamentally different from a web2 advertiser (who also need to instrument events etc).
The bit that gets me excited about the intersection of web3 and ads is does it open the door to a better agent of the user in terms of representing their preferences for what data can be used by whom for what purposes and giving that control into the hands of the user, instead of today being hypocritically represented by their device / browser vendors
Yes, for v1 of such a system, you don't need device-side SDKs that track attribution events...you can use existing (clunky) tooling around chain querying to get most of what you need.
Re: the future of web 3 and data privacy, it's not clear who would emerge as the obvious user champion. Most (normie) users won't care enough to bother (as they don't in web 2), but someone in the stack will offer privacy as a product (even if only for marketing purposes).