Triggered Element Rules Guide

Triggered rules control when dashboard-controlled elements can appear on a site. Rules are configured per element from Website UX > UX Elements > Triggered.

Each triggered element has one primary rule. Some elements also support additional conditions, page rules, and schedules. Nobi shows an element only when the primary rule qualifies and every configured condition also matches.

Use On page load when an element should be available as soon as the page is ready. This is most useful for Floating Bar and Compact Button because they are launcher-style elements and do not consume the one non-exit prompt budget.

Use After time on page when the visitor should spend a minimum amount of active visible time on the page before Nobi appears. Hidden-tab time should not qualify by itself.

Use On scroll depth when Nobi should wait until the visitor reaches a configured percentage of the page. This works well for content pages, product pages, and landing pages where scroll depth signals interest.

Use On exit intent for high-intent moments, usually with Popup. On desktop, Nobi looks for upward movement toward the top of the viewport. Exit intent has an independent session limit and can still appear once after a non-exit prompt has already appeared.

Use When idle when the visitor stops interacting for a configured amount of time. Idle time resets after movement, scrolling, typing, or touch activity.

Use Returning visitor when Nobi has reliable prior visitor context for the shopper. This should not fire for a first-time visitor just because a new shopper ID was created.

Use Visitor arrives from search engine when the session started from Google, Bing, or another search engine. Campaign context such as search term or campaign name can help tailor the prompt when it is available.

If LLM visitor behavior appears in the dashboard, use it only when the merchant wants Nobi to react to higher-level behavior classification. Availability may depend on the merchant setup and enabled data sources.

For testing, use short thresholds, clear sessionStorage.nobi_proactive_engagement, refresh the test page, and confirm the element appears only after the configured rule qualifies. Test exit intent on desktop by moving the mouse out through the top edge of the viewport.