On-site message display triggers
The triggers are simply the events upon which your on-site message (or booster) is displayed to your audience.
However, the mere occurrence of the trigger event is not enough. As a matter of fact, the booster will be shown only if all the other target conditions are also met.
Basically, when the trigger event occurs, Boostn will check if the user who fired this trigger gets through all the other filters that may have been set as well as if the time when the booster should be exposed falls within its scheduling range (if any). So, in addition to the trigger, it's also important to set the right filters and define the scheduling rules to finalize the definition of your target audience.
For now, let's focus on the different triggers available with Boostn.
🎗 Keep in mind
Triggers are alternative to each other. In other words, you'll be able to choose only one trigger event per booster. Any additional target criteria thus need to be defined using filters and scheduling rules.
First, you can choose to trigger your booster with a delay after the page loads. This means that, if you enable the delay trigger, you can set the amount of seconds to wait once the user opens the page before the booster is shown.
Another option is to trigger the on-site message when the user moves the cursor out of the browser window. This usually denotes an exit intent: the user is probably about to close the page.
This trigger event doesn't require any additional input. Just activate the corresponding option and Boostn will take care of the rest.
If you want to display the booster when the user reaches a specific point on the page, you can use the scroll trigger instead.
Specifically, activating this option requires you to set a scroll depth percentage that the user must hit in order for the trigger event to be fired.
Sometimes you need to show a message when the user requires it, for instance by clicking on a button.
This is the use case of the click trigger: identify an element of your page through a css class or its id and enable this option to display the on-site message when the user clicks on it.
Once you define the JS event that should act as a trigger, turn on this option within the configurator and fill in the required field with the name of the event you just created.