## Overview - Better analytics for users to track ROI - Better analytics for Minds staff to track backlogs - Smarter logic to ensure backlog constantly remains under 48 hours - Allow anyone to boost any post on the site, not just their own - Make it more clear how to opt-in to Open mode (add to onboarding) - Create clear definitions for safe vs. open content (Apple + Google terms) - Boost Partners: ## Goals - [ ] Campaigns / Creator - [ ] Ability to create a campaign (https://gitlab.com/minds/engine/issues/1201) - [ ] ~~Ability to target a boost~~ (Using blacklist / whitelist instead) - [ ] ~~Hashtags (https://gitlab.com/minds/engine/issues/1166)~~ - [ ] ~~Channel (https://gitlab.com/minds/engine/issues/1167)~~ - [ ] Max threshold of 5000 views per day per boost (https://gitlab.com/minds/engine/issues/1168) - [ ] Max spend per day (https://gitlab.com/minds/engine/issues/1169) - [ ] Redesign boost console to be consistent with analytics UX (https://gitlab.com/minds/front/issues/2251) - [ ] Rationalize both legacy and new campaign boost systems and interoperability (https://gitlab.com/minds/engine/issues/1136) - [ ] Integrate boost moderation queue with campaigns (https://gitlab.com/minds/engine/issues/1170) - [ ] Publisher - [ ] Ability to join the program (https://gitlab.com/minds/front/issues/1887) - [ ] Ability for channels and groups to deliver boosts on their feeds / pages / media assets (https://gitlab.com/minds/engine/issues/1135) - [ ] Ability to serve boosts on blogs, images and videos - [ ] Record boost delivery earnings (https://gitlab.com/minds/engine/issues/1171) - [ ] Boost earnings in analytic earnings dashboards (https://gitlab.com/minds/engine/issues/1173) - [ ] Blacklist / Whitelist (https://gitlab.com/minds/engine/issues/1172) ## Questions to resolve - Who decides which boosts are delivered? - How does channel targeting work? - Is OnChain always an option for all types of boosts? ## Guy's Notes *This is a Work In Progress proposal. It is open for discussion and subject to change.* The ad hoc boost system has got us this far, but it's abilities are limited. I am proposing a new boost delivery system. The boost system needs the capability to deliver: * Newsfeed Content * Sidebar Content * Channel Content The boost system needs to respect the privacy of users: * A user is assigned a boost identifier to allow anonymous tracking within minds.com * All interaction with the boost system uses the boost identifier not the user id * User can view all data associated with their assigned boost identifier at any time via boost console * User can disassociate with a boost identifier and associate with a new one at will * Explicit acceptance before any action that could compromise privacy is executed (e.g. user clicking a link to a third party site on a targeted boost could reveal their identity) The boost system needs to use targeting to deliver relevant content and satisfy any regulatory compliance: * Country level targeting (minimum requirement for compliance) * User Age or some form of verification flag targeting filter (required for compliance for some categories) * Hashtag allow/deny list * Group allow/deny list * Channel allow/deny list The boost system needs to collect data to (im)prove ROI for advertisers and improve relevancy of content: * Country of user (see above) * Impressions (count + time duration) * Interactions (expand/click/thumbsup/thumbsdown/subscribe/remind/comment) The boost system needs to collect data to detect and prevent fraud: * IP address * GeoIP data obtained from IP address (country, connection type, proxy type) * Device metrics for bot identification and classification (OS, Browser, Metrics collected from browser e.g. screen width, height, fonts) The boost system will use a fully transparent algorithm to balance supply and demand. There will be a level of revenue sharing between Minds and the creators of the content that boosted content appears alongside. ## Milestones | Milestone | Link | | ------ | ------ | | Boost Refactor | https://gitlab.com/groups/minds/-/milestones/37 | | Boost Partners | https://gitlab.com/groups/minds/-/milestones/72 | ## Merge Requests | Link | | | ------ | ------ | | https://gitlab.com/minds/engine/merge_requests/235, https://gitlab.com/minds/front/merge_requests/387 | Boost Campaigns (Specific Functionality needs adding on to existing Boost implementation | | TBC | Boost Partner | ## Mockups | | | | ------ | ------ | | Feed design | https://invis.io/KWU1X9IEB2U#/393838935_Boosted_Post, https://invis.io/KWU1X9IEB2U#/393843178_Boosted_Post_Variations | ## Launch Boards | | | | -------------- | -------------------------| | Boost refactor | https://gitlab.com/groups/minds/-/boards/1424550?milestone_title=Boost%20Refactor%20%23mvp& | | Boost Partners & Campaigns | https://gitlab.com/groups/minds/-/boards/1424552?milestone_title=Boost%20Partners%20%23mvp | ## Developers | Developer | Focus | | ------ | ------ | | @gthouret | backend + frontend | | TBC | mobile |