Event Execution Order

This page lists every Siren event in the order it fires, organized by flow type. It is a flat lookup table you can keep open in a tab while debugging the pipeline. For narrative explanations of why each event exists and how the stages connect, see The Attribution Pipeline overview. For full payload and listener documentation, follow the links on each event name to its detail page.

Standard Sale Flow

The main pipeline from referral click to payout.

1. OpportunityTriggered. Customer visits via referral link. Opportunity record created.
2. EngagementsTriggered. Engagement trigger strategies create credit claims per program.
3. SaleTriggered. Extension detects a purchase and produces the commerce event.
4. TransactionCreateRequested. Mutable event. Listeners can modify transaction details before persistence.
5. TransactionCreated. Transaction record persisted to database.
6. ConversionInitialized. Conversion pipeline begins processing.
7. ProgramGroupConversionTriggered. (If program groups apply) Winning program identified among mutually exclusive group.
8. ConversionsAwarded. Credit assigned per qualifying program.
9. EngagementAwarded. Individual engagement awarded credit during conversion.
10. EngagementCompleted. All engagements for the opportunity processed.
11. ObligationIssued. Business records what it owes the collaborator (draft status).
12. TransactionCompleted. Payment gateway confirms the charge. May fire immediately or after a delay depending on the gateway.
13. ConversionApproved. Conversion passes review (auto on payment confirmation, or manual by admin).

Steps 12-13 can be asynchronous. TransactionCompleted fires when the payment gateway confirms, which may be immediate or delayed. ConversionApproved can also be triggered manually by an admin.

Fulfillment & Payout Flow

Shared by all flows. Triggered when an admin initiates a fulfillment run, not immediately after conversion approval.

1. FulfillmentCreated. Payout batch initiated.
2. FulfillmentStatusChanged. Fulfillment transitions through lifecycle (pending, processing, completed).
3. PayoutCreated. Individual disbursement line item built per collaborator.
4. PayoutPaid. Collaborator receives payment (terminal event).
5. ObligationCompleted. Obligation marked fulfilled. Payout ID written back.

Coupon Attribution Flow

Diverges from standard sale at the beginning.

1. CouponApplied. Customer uses coupon at checkout. System looks up coupon owner.
2. EngagementsTriggered. Engagements created from coupon ownership.
3. SaleTriggered. Sale completes with coupon attribution.
4. Continues from step 4 of Standard Sale Flow (TransactionCreateRequested onward).

Lead Flow

Uses LeadTriggered instead of SaleTriggered. No transaction details, no TransactionCompleted.

1. OpportunityTriggered. Customer visits via referral link. Opportunity record created.
2. EngagementsTriggered. Engagement trigger strategies create credit claims per program.
3. LeadTriggered. Form submission or signup action detected (no monetary value).
4. ConversionInitialized. Conversion pipeline begins processing.
5. ConversionsAwarded. Credit assigned using lead-specific incentive types.
6. ObligationIssued. Business records what it owes the collaborator (draft status).
7. ConversionApproved. Manual admin approval required (no auto-approval since there is no TransactionCompleted).

Renewal Flow

Starts from existing engagement records. Uses ConversionRenewed instead of ConversionInitialized.

1. RenewalTriggered. Subscription renewal payment detected. Traces back to original transaction.
2. ConversionRenewed. Conversion pipeline begins from original engagement records.
3. ObligationIssued. Business records what it owes the collaborator (draft status).
4. TransactionCompleted. Payment gateway confirms the charge.
5. ConversionApproved. Conversion passes review (auto on payment confirmation).

Refund Flow

Short reversal flow.

1. RefundTriggered. Completed order reversed (cancellation, refund, or deletion).
2. ConversionRejected. Conversions tied to the refunded transaction are denied. Obligations cleaned up.

Distribution Flow

Separate pipeline for scheduled, metric-based rewards.

1. MetricsTriggered. New metric data recorded (fires continuously as activity happens, between distribution periods).
2. DistributionHeartbeatInitialized. Scheduled trigger fires.
3. DistributionCompleted. Distribution period processed. Reward pool calculated.
4. AllocationCompleted. Individual collaborator’s share determined.
5. ObligationIssued. Allocation becomes an obligation (enters fulfillment pipeline).

MetricsTriggered fires continuously as activity happens. Steps 2-5 fire on the heartbeat schedule.

Manual Attribution

Bypasses normal engagement flow entirely.

1. ManualAttributionRequested. Admin manually attributes conversion to a collaborator.
2. ConversionsAwarded. Credit assigned per qualifying program.
3. ObligationIssued. Business records what it owes the collaborator (draft status).

System Events

Non-pipeline events that fire independently.

• CollaboratorSubmissionReceived. New collaborator registration request (mutable).
• CollaboratorAccountReady. Collaborator account fully set up.
• CustomEventTriggered. Custom event ingested through the event API.
• StudentCompletedLesson. Student finishes a lesson in a connected LMS.
• RecipeApplyRequested. Recipe configuration applied (mutable).
• OpportunityInvalidated. Opportunity rejected (duplicate, expired, validation failure). Pipeline terminates.