RSS and Atom feeds

Connect feeds under Content → RSS feeds. The parser accepts RSS <item> and Atom <entry>, unwraps CDATA, and reads common title, link, category, description, and image fields. Title-only feeds can be enriched from Open Graph.

Opt-in tags

In Auto (tagged articles only) mode, only tagged items send automatically. Untagged items still appear in Suggestions.

Most third-party feeds carry no such tag. If you connect a feed you do not control, expect this mode to send nothing at all. Pick Auto (all new articles) instead.

Either form is accepted (case-insensitive; value must be true):

xml

<item>
  <title>Story headline</title>
  <link>https://example.com/story</link>
  <engagenudge:nudge>true</engagenudge:nudge>
</item>

xml

<item>
  <title>Story headline</title>
  <link>https://example.com/story</link>
  <nudge>true</nudge>
</item>

Prefer the namespaced form when your CMS can emit custom elements. Other values (missing, false, empty) do not opt the item into auto-push. Tagged items also bypass category/keyword allowlists on ingest.

Behavior by feed mode

Feed mode	Tagged item	Untagged item
Suggest (default)	Suggestions + Nudge candidate badge	Suggestions
Auto (tagged articles only)	Auto-send (cap + min delay still apply)	Suggestions only
Auto (all new articles)	Auto-send	Auto-send if it passes allowlists

Auto-push still enforces daily cap, minimum delay, and Decision Engine suppressions (fatigue, budget, confidence floor).

Sending anyway

Each feed has Send even when the recommendation says no. With it on, the Decision Engine's soft gates. Audience fatigue, the daily send budget and the confidence floor, no longer stop the feed, and the campaign's decisionJson records Override: Feed override so the send shows up as an override in your restraint receipts.

These are never overridable, with the toggle on or off:

the feed's own daily cap and minimum delay
an empty or unreachable audience
the DPA, the send pause, and plan or billing limits

Outcomes

Every article the poller handles is recorded as one outcome. One of pushed, suggested, suppressed or blocked, with the reason (cap, delay, fatigue, budget, confidence, no_audience, billing, dpa, paused, untagged, filtered) and the setting behind it.

The feed card shows the last 24 hours ("25 fetched · 0 sent · 0 held back"), expands to the ten most recent events, and reads GET /v1/sites/:siteId/feeds/:feedId/outcomes for the detail.

A failed poll now names its cause on the card: invalid_url, http:<status>, fetch:timeout, fetch:blocked, fetch:dns, fetch:failed or parse:no_items (a 200 that contained no <item> or <entry>). A good poll clears it.

Dashboard