Booost Docs
ENIT booost.networkApp

Docs 19 of 19

Content sources, topics and what the coloured tags mean

Workflow → Sources is the list of feeds a content workflow reads. Every source carries a beat, and the beat decides which campaigns read it.

Adding a source

  1. Open Workflow → Sources.
  2. Pick from the catalogue — 349 curated feeds across 120 beats and 12 macro-areas. The beat you searched with is saved along with the source.
  3. Or paste a link, for anything the catalogue does not have. Booost works out the type and finds the RSS feed even if you paste the homepage.
  4. Check the colour of the beat tag. That is the part that matters.

What the tags mean

Why the colour matters: the match is exact

The beat is the link between a source and a campaign. The "Content sources" node has a beat field, and the match is exact: a source tagged sales-development is read by a campaign filtering on sales-development, and by no other.

There is no fuzzy matching and no synonyms: sales-dev and sales-development are two different beats.

Sources and Topics answer two different questions

It is worth not confusing them.

A topic you keep becomes an allow-list: the moment you keep even one, subjects outside the list are dropped. So a topic left at "undecided" changes nothing until you decide.

Two shortcuts lead to the same list. In the Topics tab, the chips under Suggested from your sources are the catalogue topics your sources already cover: one click and the topic is kept. And the window that opens when you pick a content template (What do you want to write about?, see Workflow) starts from the other end: you pick the topics, then Booost proposes the sources that cover them.

How relevance decides what gets written

Once your sources are grouped into news items, the model gives each group a score from 0 to 100: how close it is to your content pillars (the ones in My Profile, or the implicit ones from your sources' beats). The topics you keep are part of that question too, so the model knows what you chose to write about.

Near the threshold that score wobbles: the same material can get 80 in one run and 30 in the next. So the threshold is not a line but a band, 15 points on each side of the Topic relevance field of the Cluster topics node (40 by default, so from 25 to 55):

Set the field to 0 and relevance drops nothing. The run view lists the groups that were dropped, each with its score, so a post that never arrived has a reason you can read.

The same news never becomes two posts

The "Content sources" node has an "Only new items" switch, on by default: before articles are grouped by topic, it drops the ones this account has already seen in a previous run. The "seen" mark is not set by this node — it is set by topic clustering, and only on the articles that actually become a post: one dropped just because that day's budget was full stays in the feed and gets another chance next run.