OpportunityTriggered

Every attribution flow in Siren starts with an opportunity. When a customer visits a site through an affiliate link, applies a coupon, or interacts with any other tracked touchpoint, the system creates an opportunity record and fires OpportunityTriggered. This is the entry point for the entire engagement and conversion pipeline.

The event is identified as opportunity_triggered and lives in the Siren\Opportunities\Core\Events namespace.

What does this event carry?

The event provides two pieces of data: the full Opportunity model and a trigger string that identifies what caused the opportunity to be created.

use Siren\Opportunities\Core\Events\OpportunityTriggered;

$opportunity = $event->getOpportunity();
$trigger = $event->getTrigger();

The trigger string tells you the source of the opportunity. A customer clicking an affiliate link produces a different trigger than a customer entering a coupon code at checkout. This distinction matters because engagement trigger strategies use it to decide how to handle the opportunity.

What happens when it fires?

Engagement trigger strategies evaluate the opportunity and decide whether to create engagement records. The ReferredSiteVisit strategy, for example, listens to this event and creates engagements for the collaborator whose referral link was used. If the collaborator participates in multiple programs, the strategy may produce multiple engagement records from a single opportunity.

If the opportunity is later found to be invalid (due to duplication, expiration, or failed validation), the system fires OpportunityInvalidated to clean up any engagements that were created.

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