ConversionRenewed

Subscription businesses need renewals to carry the same attribution as the original sale. When a subscription renewal payment is detected, the system fires ConversionRenewed instead of ConversionInitialized. The difference is fundamental: while ConversionInitialized starts from a live opportunity, ConversionRenewed starts from the original engagement records that were created during the initial sale.

The event is identified as conversion_renewed and lives in the Siren\Conversions\Core\Events namespace.

What does this event carry?

The event carries the array of original Engagement records from the initial sale, a Transaction model for the renewal payment, a conversionType string, and optional binding information (bindingId and bindingDataType) for linking to external records.

use Siren\Conversions\Core\Events\ConversionRenewed;

public function handle(Event $event): void
{
    $originalEngagements = $event->getOriginalEngagements();
    $transaction = $event->getTransaction();
    $type = $event->getConversionType();
    $bindingId = $event->getBindingId();
    $bindingDataType = $event->getBindingDataType();
}

Why reuse the original engagements?

The engagement reuse preserves the original attribution chain. The collaborator who was credited with the initial sale continues to earn on renewals without needing a new opportunity or engagement cycle. This is the correct behavior for subscription programs: a customer who signed up through an affiliate link six months ago should still generate commissions for that affiliate when their subscription renews.

What happens downstream?

After renewal conversions are built, the system fires RenewedConversionsAwarded rather than ConversionsAwarded. RenewedConversionsAwarded is the renewal counterpart to ConversionsAwarded and carries the same shape of data: an array of Conversion models, the original engagements, the Transaction, the Incentive and IncentiveResolver, the Program, and the conversionType. Downstream listeners that handle obligation creation and engagement management listen to both events.

See the Conversion Events overview for how this event fits into the full conversion pipeline.