Siren

RenewalTriggered

Fires when a subscription renewal payment completes. Traces back to the original purchase for continuing attribution.

WordPress plugin

Last updated: October 26, 2026

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|string|null: external renewal record 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. Easy Digital Downloads fires it for Recurring Payments renewals, LifterLMS fires it for each payment after the first on a recurring order, and North Commerce fires it for each paid subscription or payment plan renewal order. Siren Cloud fires it for each paid billing-cycle invoice of a Stripe subscription whose first payment it recorded. Extensions that do not support subscriptions never fire this event. In the WordPress integrations, when the subscription’s first order has no transaction in Siren, such as a subscription that started before Siren was installed, the integration doesn’t fire the event, and the renewal pays no one. On Siren Cloud, a Stripe renewal whose first payment Siren didn’t record is recorded as a sale instead when the customer is already linked to a referral or a product owner claims it.

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

Your privacy choices

Account, checkout and chat you request work without optional tracking. Choose whether to allow these other uses on this website.

You can change or withdraw your choices at any time using “Privacy choices.” We remember your choice for 180 days. Read our privacy policy.