Landing trigger
3 min
The Landing trigger shows a widget as soon as the page has loaded and the widget's rules have passed. Use it for widgets that should be visible right away: announcement bars, embedded widgets, welcome offers and free-shipping bars.
Available on: all platforms.
How it works
- The page loads and Personizely checks the widget's schedule and page-load rules (Pages, Frequency, Timeframe and so on).
- If the widget's content or audience needs visitor, company or cart data, Personizely waits until that data has loaded.
- The trigger fires straight away. The Target, Query string and Widgets interaction rules are checked at that moment, and if they pass the widget is shown.
Like every trigger, it shows the widget at most once per page view.
Configuration
The Landing trigger has no settings and no conditions. If you need a delay or a scroll depth, use the Time or Scroll trigger instead.
Behavior details and limitations
- It fires on every page view the rules allow. Without a Frequency rule, a Landing popup reappears on every page. Add a frequency such as "Show only once per session" or "Stop once closed".
- Embedded widgets usually use Landing. An embedded widget still needs a trigger to appear; Landing places it as soon as its placeholder is on the page.
- Bars. A top bar with the Landing trigger appears as the page loads, which can move content down briefly. See Bar widgets for the Fixed and Static behaviors.
- Single-page apps. On themes that change pages without a full reload, Landing fires again after each detected page change, if the rules still pass.
- Combining triggers. Landing fires immediately, so other triggers on the same widget never get a chance on that page while Landing's rules pass.
Examples
- Announcement bar: Bar widget, Landing trigger, Frequency "Stop once closed".
- Free-shipping progress: Callout with a Cart progress element, Landing trigger, Pages set to the cart page.
- Campaign landing offer: Popup with Landing trigger and a Query string rule "utm_source is newsletter".