Do you envision (let's say the V1 of) this system to serve primarily on Web 2 media or Web 3 media?
It would seem that in order to siphon users from Web 2 it would need to serve on Web 2 media. Wed 2 media / user attention today is monopolized by gated publisher platforms and tech giants. So for this to work does it requi…
Do you envision (let's say the V1 of) this system to serve primarily on Web 2 media or Web 3 media?
It would seem that in order to siphon users from Web 2 it would need to serve on Web 2 media. Wed 2 media / user attention today is monopolized by gated publisher platforms and tech giants. So for this to work does it require the Google/FB/Twitters of the world to use this system to serve ads (and why would they)?
As a Web 3 -> Web 3 ads system (or as a precondition for economically viable Web 3 media to exist) I get it. The Web 2 -> Web 3 part seems fussier
Also - this might be a naive question but for that head of APAC buying FB ads, assuming it's a browser game, why can't they measure their CAC via the standard pixel?
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).
Very interesting.
Do you envision (let's say the V1 of) this system to serve primarily on Web 2 media or Web 3 media?
It would seem that in order to siphon users from Web 2 it would need to serve on Web 2 media. Wed 2 media / user attention today is monopolized by gated publisher platforms and tech giants. So for this to work does it require the Google/FB/Twitters of the world to use this system to serve ads (and why would they)?
As a Web 3 -> Web 3 ads system (or as a precondition for economically viable Web 3 media to exist) I get it. The Web 2 -> Web 3 part seems fussier
Also - this might be a naive question but for that head of APAC buying FB ads, assuming it's a browser game, why can't they measure their CAC via the standard pixel?
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).