ConversionApproved

Conversions do not immediately result in payouts. They go through a review step first, either automated or manual. When a conversion passes that review, the system fires ConversionApproved, signaling that the conversion is legitimate and its associated obligations should move forward.

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

What does this event carry?

The event carries a single Conversion model representing the conversion that was approved.

use Siren\Conversions\Core\Events\ConversionApproved;

public function handle(Event $event): void
{
    $conversion = $event->getConversion();
}

What happens when it fires?

The primary downstream listener is MarkObligationsAsPending. When a conversion is approved, this listener transitions the conversion’s associated obligation from draft to pending status. The distinction between draft and pending is significant: draft obligations are invisible to the fulfillment system, while pending obligations become eligible for inclusion in the next fulfillment run.

This two-step process (create as draft, then promote to pending on approval) gives admins a window to review conversions before they become financial commitments. Auto-approval rules can skip this window for trusted conversion types, but the event fires in both cases.

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