EngagementAwarded

Creating an engagement is not the same as awarding it credit. When EngagementsTriggered fires, engagement records are created and sit in an active state, waiting. Later, when a sale or lead comes through, the conversion system evaluates which engagements should receive credit based on the program’s resolver strategy (shared pool, top score wins, and so on). Each engagement that receives credit produces an EngagementAwarded event.

The event is identified as Engagement_awarded and lives in the Siren\Engagements\Core\Events namespace.

What does this event carry?

This event carries richer data than most attribution events because it needs to communicate the full reward context. Listeners receive the Engagement model, an optional Transaction model, an Incentive instance that describes the reward structure, and an IncentiveResolver that can calculate the actual reward amount.

use Siren\Engagements\Core\Events\EngagementAwarded;

$engagement = $event->getEngagement();
$transaction = $event->getTransaction();
$incentiveType = $event->getIncentiveType();
$resolver = $event->getIncentiveResolver();

The transaction is optional because not every conversion involves a financial transaction. Lead-based programs award engagements without a sale, so getTransaction() returns null in those cases.

The incentive and resolver together provide the complete calculation context. The Incentive describes the reward structure (percentage-based, flat rate, tiered), while the IncentiveResolver can compute the actual dollar amount the collaborator earns. This saves listeners from re-deriving the reward logic themselves.

What happens when it fires?

Because each engagement is awarded individually, a single conversion can produce multiple EngagementAwarded events if multiple engagements receive credit. This happens when a program uses a shared-pool resolver that splits credit among several collaborators, or when a customer’s purchase spans multiple programs.

See the Attribution Events overview for how this event fits into the full attribution pipeline.