RenewalTriggered

RenewalTriggered fires when a subscription renewal payment completes. This is the most complex commerce event because it needs to trace back to the original purchase so that the same collaborator continues earning commissions on recurring revenue.

The event ID is renewal_triggered, and its fully qualified class is Siren\Commerce\Events\RenewalTriggered.

What does this event carry?

The event carries the original Transaction model from the initial sale (not the renewal), an array of transaction details for the renewal order, and optional binding fields. The original transaction is the link back to the collaborator who earned the initial referral. By referencing it, the renewal process reuses the original attribution data instead of looking up a new opportunity.

use Siren\Commerce\Events\RenewalTriggered;

$event = new RenewalTriggered(
    $originalTransaction,   // Transaction: from the initial purchase
    $transactionDetails,    // array: line items for the renewal
    $renewalOrderId,        // ?int: external renewal order ID
    'wc_order'              // ?string: external type
);

How does the pipeline react?

InitializeRenewalConversion in the conversions domain picks up this event and begins building renewal conversion records. The process mirrors the initial sale flow but uses the original transaction’s attribution data rather than performing a fresh opportunity lookup. This ensures the collaborator who referred the original customer continues to receive credit.

Renewal support is conditional in some extensions. WooCommerce, for instance, only binds the renewal transformer when WooCommerce Subscriptions is installed. Extensions that do not support subscriptions simply never fire this event.

For the full lifecycle of commerce events and how they connect to the rest of the attribution pipeline, see the Commerce Events overview.