Send a Nudge

You can compose from the dashboard or from your CMS via the REST API.

Before a live send

DPA accepted in Settings → Privacy
Sends not paused for the site
Your plan’s audience cap allows the send
At least one test device if you want a test first

A test only reaches test devices. It does not start the 14-day trial. A live send reaches the eligible audience and is the first-live-send clock for trial.

Compose

Open Campaigns or pick a story from Content.
Use a URL so EngageNudge can preview title, body, and image, or write the message manually (title, body, destination URL).
Review the send/no-send recommendation. You can still send from the dashboard when you need to.

RSS auto-push will not force a send when the decision is skip, unless the feed has the override turned on.

Automating from RSS

Content → RSS feeds polls every 5 minutes. Each feed has one of three modes, and the mode is the setting that decides whether anything is ever sent:

Suggest (default). New articles wait in Suggestions until you send or dismiss them.
Auto (tagged articles only). An article sends by itself only if the feed marks it with <engagenudge:nudge>true</engagenudge:nudge> (or <nudge>true</nudge>). The tag may arrive after publication: a mark added within a day of an article appearing still sends it. Feeds you do not control almost never carry that tag, so in practice this mode keeps everything in Suggestions.
Auto (all new articles). Every new article that passes your allowlists sends by itself.

Every article the poller handles is recorded, and the feed card shows the last 24 hours: how many were fetched, how many were sent, and how many were held back with the reason and the setting behind it. Expand it to see the ten most recent articles. If a poll fails, the card names the cause. A 404, a timeout, or a URL that is not a feed. Instead of only saying it failed.

Send even when the recommendation says no lets a feed send through the soft gates (audience fatigue, the daily send budget, the confidence floor). It is logged as an override in your restraint receipts. The feed's daily cap and minimum delay, plan limits, the send pause and consent still apply. Those are never overridable.

Test, send, schedule, stop

Test: notification on test devices only.
Send: live audience. Optional idempotency if you send from an API.
Schedule: pick a future time. The scheduler fans out on the same path as live send.
Stop: halt an in-flight run from the campaign or run view.

From a CMS