Introducing Activity Feeds
Every major record in Siren now carries a timestamped history of what the system did to it. What that changes for disputes, refunds, and weekly review.
Running an incentive program means answering a lot of “what actually happened to this specific record?” questions. Why didn’t this commission pay out. What did that refund really reverse. Where did this collaborator’s conversion end up. Answering those questions used to mean five or ten minutes of clicking between admin screens before the full story finally came together. That friction is the real reason weekly reviews get skipped and dispute investigations drag on longer than they should.
Every major record in Siren now has an activity feed on it. Open a conversion, an obligation, or a collaborator and you’ll find a chronological log of everything Siren did to that record. Fulfillments, engagements, and transactions all have feeds too.
The feed writes itself. As Siren moves records through the attribution and payout pipeline, each lifecycle event gets recorded and linked to every other record the event touched. A refund that reversed a conversion on Tuesday shows up on every feed that refund touched. You can walk in from any of those records and end up in the same story.
The feed isn’t a new capability. Siren has always recorded these events. What changed is that the record of them now lives on the record itself, instead of being something you reconstruct across several screens.
The workflows that get better
The most immediate payoff is dispute resolution. A collaborator emails asking where their commission went. The sale went through and the conversion got approved, but the payout isn’t showing in their history and nothing jumps out to explain it. The old path was ten minutes of clicking between the conversion, the engagement, the opportunity, and the transaction before the refund from last week finally surfaced. The new path is one screen. Open the conversion, scroll the feed, and the refund is right there in sequence with its timestamp. You reply in two minutes with a specific answer instead of a guess.
The bigger shift is that the feed is an artifact the collaborator can see too. It’s system-authored, timestamped, and has no editorial spin, which changes the tone of every conversation about a rejected or reversed conversion. You’re pointing at a recorded timeline instead of volunteering your recollection, and that lands differently with a collaborator who thinks they got shorted. The fraud-prevention post that went out alongside this release leans on the same mechanic. The feed turns weekly review from a chore into a habit, which is the other workflow this release makes practical.
Beyond disputes, the feed catches problems where Siren did exactly what it was supposed to do and the outcome still isn’t what you expected. Say an engagement fires for a customer whose opportunity invalidates a day later because they turned out to be a collaborator logging in. The credit rolls back quietly in the background, and the mismatch usually doesn’t surface until someone reconciles against the books weeks later. With a feed on the transaction, that reversal is sitting right there the next time anyone opens the record. Problems stop arriving as complaints and start surfacing in passing.
Say you changed a program’s rules last week, or a collaborator’s alias, or an integration. Did anything break? Open a recent conversion and read down the feed. If the sequence reads cleanly, you’re fine. If there’s a gap or a rejection you weren’t expecting, that’s where to look. Reading the record has replaced having to guess what might be wrong.
None of these are new things you can do. What’s new is that the friction dropped far enough that you’ll actually do them.
Transparency was always the point
Siren was built to be the opposite of a black box. That’s been the argument since the launch post, and it shows up again in how we’ve written about commission rates living on programs rather than collaborators, multiple programs as a visibility mechanism, and opportunities as a generalization of visits. Same case from different angles. You should be able to understand why your system paid what it paid, without trusting anyone’s word for it.
The activity feed is the next layer of the same idea. The system was already transparent in the sense that every decision was recorded and inspectable. What was missing was a surface that presented those decisions as a story you could read, instead of a puzzle you had to assemble. That’s the layer we just shipped.
Beacon tackled the friction of designing a program. Running one has its own friction, and activity feeds are aimed at that. You shouldn’t have to fight the software to understand what it’s doing.
How to try it
If you’re already running Siren, you have it. Open any detail screen on a major record and the feed is there. Nothing to configure.
If you’re building on top of Siren, the feed is backed by the notes resource in the REST API. Every blueprint, every field, and every source link is documented, so anything you want to build on top of this data can read from the same records the admin UI reads from.
The activity feeds doc is the right place to start if you want a user-level walkthrough.
If weekly reviews and dispute investigations have been piling up, this is the release to try them again. The machinery was already there. What finally shipped is the surface that matches it.
Swim fast, dream big!