In Native Ads, an ad (saved as a post, hidden, declining rewards) is universal, within the Steem ecosystem. Its definition (properties, type, etc) is self-contained, also stored on the post (as JSON metadata).
This means one ad can be submitted to any Steem community that enables Native Ads; a "community" being an abstract term for anything from groups formed around interests, to entire platforms serving niche purposes.
A real world example:
I use a poll as the ad type in this example, though an implementation hasn't been designed yet for Hivemind. It's just an example.
- I make an ad; an opinion poll on a crypto, say Bitcoin.
- It asks a simple question: What's the longest that you've ever waited for a Bitcoin transaction to confirm?
- More than 3 days
- More than 24 hours
- More than 6 hours
- I haven't used Bitcoin before
Submissions
I submit it to the following crypto-related social communities (i.e. found on Steemit.com, etc):
- Bitcoin News
- Crypto Traders
- Bitcoin Cash
I also submit to other non-crypto social communities (also on Steemit.com, et al.):
- Venezuela
- Sports Betting
Then I submit it to external, single-community platforms, that are monetizing using Native Ads. These don't need to have the full communities implementation, just a community to accept ads with (I'll write a different post on this):
- Block explorers
- Fee estimators and other tools
- Crypto freelance platform
- Travel platform
Results
I get results organized by the communities I submitted to. Also detailed with the Steem accounts that interacted with the poll.
What I get is an array of opinion data, that is potentially valuable to researchers, for example.
This was just a simple example to show how advertisers could reach multiple Steem communities using Native Ads.
I'm developing a testbed to experiment with new Hivemind features. To see the code, check out the branches on my fork of Hivemind on GitHub.
For an overview of Native Ads and how it will work, read this doc.