Activity Feeds

The activity feed is the running history that appears on every major detail screen in Siren. Open a collaborator, a conversion, an obligation, a fulfillment, an engagement, or a transaction and the activity feed shows you, in chronological order, everything Siren has recorded about that record.

Each entry in the feed is a note. A note is a single timestamped record of something that happened, like “an obligation was issued for this conversion” or “this payout was marked paid.” The feed for any given record is the collection of notes that are linked to it, oldest at the bottom, newest at the top.

What writes to the feed

You don’t write notes by hand. Siren writes them automatically as things happen across the system. When an obligation is issued, a conversion is approved, a payout is created, a refund is triggered, or anything else worth remembering occurs, Siren records a note and surfaces it wherever it’s relevant.

That last part is the point. The same event often touches several records at once — a payout involves a collaborator, an obligation, a fulfillment, and a transaction — and the note shows up on every one of their activity feeds. You don’t have to track down which record the story lives on. Open whichever one you’re already looking at and it’s there.

What the feed is for

The activity feed exists to answer the question “what happened to this record?” without having to piece together the story from multiple screens or reach for a developer to check the logs.

A collaborator emails in asking why a conversion they expected to see hasn’t paid out yet. Open the conversion, scan the feed, and the answer is usually right there. Maybe the conversion was rejected. Maybe the obligation was issued but hasn’t been rolled into a fulfillment yet. Maybe a refund came through and reversed it.

A bookkeeping reconciliation doesn’t match what you sent out last cycle. Open the fulfillment, read the feed, and every obligation that was included and every payout that was generated is on the record with a timestamp.

A program manager wants to spot-check that the incentive pipeline is working correctly after a configuration change. Open a recent conversion and the feed shows the full sequence of events that led from the engagement to the obligation.

The feed is also where you’ll catch silent failures. If a conversion was approved but no obligation appears in its feed, something in the pipeline didn’t fire as expected, and that absence is often the first signal.

How to read an entry

Each entry is a short, plain-language description of the event, a timestamp, and links to the related records. An obligation-issued note on a collaborator’s feed will link to both the obligation and the conversion that caused it, so you can click straight through to either. Notes don’t carry editorial content or commentary. They’re a factual record of what Siren did, not a place for manual annotation.

For developers: The activity feed is backed by the notes resource. Each entry is a note record stored with a blueprint key (for example, obligation_issued) and resolved into rendered content at read time. The REST API exposes notes through GET /notes with a sourceType and sourceId filter. See the resource reference for field selection, the available blueprint keys, and how the resolver system hydrates notes into display content.