A trigger is the node that starts an automated scenario and decides when customers enter the flow.
Category
Bloomreach Campaigns
Also known as
scenario trigger; event trigger
It answers the first question of any automation: what makes this automation begin. Bloomreach Engagement offers event triggers (On event: a purchase, a cart abandon), time triggers (Now, On date, On date attribute, Repeat), and the API trigger for external systems. There is no native “enters a segment” trigger: segment-based automation is built by pairing a scheduled Repeat trigger with a condition, or by tracking segmentation-change events and triggering on those.
In practice
Match the trigger to the intent. Event triggers are for timely, one-to-one reactions; scheduled triggers filtered by segment suit slower lifecycle transitions. Getting this wrong is why some automations feel late and others fire too often.
Discuss this term
A question, a bug, or outdated info? Tell us — it goes straight to the team, and we keep the glossary current.