Fixed calculation
The default. Emit a single score for the triggering collaborator at a configured value.
Last updated: June 3, 2026
Fixed is the default calculation strategy. One trigger produces one credit, and the credit lands on the collaborator who caused the trigger. No fanout, no layers, no walking a group, just a single row at a single configured value. If you’ve used Siren without thinking about calculation strategies, you’ve been using Fixed.
How it works
A trigger fires the engagement type (or metric type) the calculation is attached to. Fixed emits one result that credits the triggering collaborator at the value you configured. That’s the whole mechanic.
The triggering collaborator is the person Siren resolves from the event itself: the affiliate whose link drove the sale, the user who completed the action, the account tied to the metric being recorded. Fixed doesn’t look at any group around them. It doesn’t check structure. It doesn’t care whether the collaborator belongs to a collaborator group at all.
Because Fixed only ever emits one row per trigger, it carries no capability requirements. It works with every structure and shows up in the picker for every program and distributor.
When to use it
Fixed is the default, and most programs never need anything else. Reach for it whenever the credit should land on exactly one person, the one who triggered the event. That covers a standard per-sale commission, where an affiliate refers a sale and gets paid, as well as per-action point awards, where someone completes a tracked action and earns the points for it. It also covers any single-recipient payout where no upline or downline is involved.
If you want the trigger to credit more than one person (the referrer’s sponsor, a team lead, members further down a chain), you want a cascade instead. See upline cascade and downline cascade, or read choosing a calculation strategy for the full comparison.
Configuration
Fixed has one field.
value(integer): the score awarded to the triggering collaborator.
How that score becomes a payout depends on the structure it feeds. On a program, that is the program’s incentive structure. On a distributor, it is the distribution structure. With a direct, fixed-per-incentive structure the score is taken literally, so the value you set is the amount paid out. With a performance-weighted pool, the score becomes a weight that sets the collaborator’s share of the pool relative to everyone else’s contributions for the period.
Either way, Fixed itself just emits the number you configured. What that number means downstream is the structure’s job.