Goals

• Campaigns / Creator
  • Ability to create a campaign (engine#1201)
  • Ability to target a boost (Using blacklist / whitelist instead)
    • Hashtags (engine#1166)
    • Channel (engine#1167)
  • Max threshold of 5000 views per day per boost (engine#1168 (closed))
  • Max spend per day (engine#1169)
  • Redesign boost console to be consistent with analytics UX (front#2251)
  • Rationalize both legacy and new campaign boost systems and interoperability (engine#1136 (closed))
  • Integrate boost moderation queue with campaigns (engine#1170 (closed))
• Publisher
  • Ability to join the program (front#1887)
  • Ability for channels and groups to deliver boosts on their feeds / pages / media assets (engine#1135)
  • Ability to serve boosts on blogs, images and videos
  • Record boost delivery earnings (engine#1171)
  • Boost earnings in analytic earnings dashboards (engine#1173)
• Blacklist / Whitelist (engine#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
engine!235, front!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

added issue front#1886 (closed)

added issue front#1887

added scoped labels

mentioned in epic &3 (closed)

changed the description

changed the description

changed the description

changed the description

changed title from Boost to Boost

changed title from Boost to Boost

changed title from Boost Partners to Boost Partners

@gthouret @michaelfbradley @markeharding @jotto141 The missing part of Boost right now is rationalizing the Boost Console, Boost Prompt with the Boost Campaigns feature.

https://www.minds.com/boost/console/newsfeed/history Should realistically use the same structure and design as the new analytics and pro consoles https://www.minds.com/analytics/dashboard/traffic.

The way boosts look in feeds, on channels, in videos, on blogs all need mocking up along with console and prompt.

changed the description

@gthouret can you go through the checkmarks at the top of this epic so we can understand what is finished and what isn't?

I'm going to have to redo quite a bit of what's already been done here so not able to check any of those points.

added epic &100 (closed) as child epic

Added link to epic where I'm recording future ideas that I want to transpose into this epic once those future ideas are agreed on.

There are issues right now with boost delivery, what looked like simple issues quickly turned into deeper, more complex issues the more I got into them.

My strategy is to resolve those live issues as a priority before I start breaking it down. I've got to get the fundamentals of delivering boosts done right before I can start adding all the features we want.

Currently working on:

• Fix for duplicate boosts in feed (front#2190 (closed))
• Fix for no items/not enough items returned from Boost fetch request (engine#1067 (closed))

Next up is putting up is finishing getting the current boost campaign work working and up on a review site so we have a starting point to evaluate from. (engine#930 (closed))

Ok, we still need to be able to put an accurate timeline in place. @michaelfbradley will have designs for you today on how boosts will look in the feed, and as you know we are applying the Analytics template theme to the Boost Console. Let's meet tomorrow to discuss so please put some thought into an accurate timeline.

changed the description

changed the description

added issue engine#1134

added issue engine#1135

added issue engine#1136 (closed)

added issue front#2251

Hey @gthouret - You can find the new Boosted Post layouts here. &92 (comment 245949636)

If anything is unclear, or you have questions at all, please do let me know.

@ottman Happy to discuss with you. I'll send you a meeting request.

added epic &103 (closed) as child epic

FYI &103 (closed) is the collection of issues (mostly technical debt) I need to trudge through before I can move forward with this.

Let's do another meeting Monday at 1030 in dev room.

Sorry I'm not going to be able to make that. I can do later on Tuesday - 1600 est or early on Wednesday?

removed the finish date

changed finish date to Dec 18, 2019

marked the task Ability to schedule boosts in the future as completed

changed the description

changed the description

mentioned in epic &100 (closed)

changed the description

added issue engine#1172

added issue engine#1171

added issue engine#1169

added issue engine#1168 (closed)

added issue engine#1167

added issue engine#1170 (closed)

added issue engine#1166

changed the description

changed the description

added issue engine#1180

added issue engine#1181

added issue engine#1183

changed the description

added issue engine#1201

changed finish date to Jan 21, 2020

changed finish date to Jan 28, 2020

changed finish date to Feb 25, 2020

added scoped label

added issue front#2343

added issue front#2147

@michaelfbradley please share the most recent boost mocks here so we can plan the next push. Thanks!