An API trigger starts a Bloomreach Engagement scenario when an outside system calls a URL with news about a real-world event, such as a canceled flight, a weather alert, or a goal scored.
Category
Bloomreach Campaigns, Bloomreach Dev
Also known as
API trigger for scenarios; external trigger; customer event filtered API trigger
You define which values the call carries. Bloomreach generates the URL and an example payload, and the scenario reads the values as {{api_trigger_params.name}} for filtering and personalization. There are two modes. In standard mode every call evaluates the whole customer base, so the allowed rate drops as the project grows: 1 call per second under 10 million profiles, down to 1 call per 100 seconds above 100 million. In customer event filtered mode the trigger first looks for a matching event in each customer's history and allows up to 100 calls per second. Bloomreach switches the feature on per request, and cloning a scenario to another project does not copy the trigger.
In practice
Choose the mode by audience size. If one event links a customer to the signal (a booking, a bet, a subscription), use the event filtered mode. It only sees events tracked after the scenario went live.
Something out of date?