Proactive Triggers

Proactive triggers send a localized visitor-facing message when a supported browser condition is met. They are configured under Triggers, not under Widget settings.

Supported trigger typesCopy Anchor Link

The dashboard currently supports five trigger types:

• Time on page: fire after the visitor has remained on the page for a configured number of seconds.
• Visited page: fire when the current page matches a configured page pattern.
• Exit intent: fire when the browser detects exit intent.
• First visit: fire for a first-time visitor.
• Proactive invitation: combine time on page with an optional page URL, returning-visitor requirement, and exit-intent requirement.

Create a triggerCopy Anchor Link

Open Triggers and choose New trigger. Configure:

1. an internal name and optional description;
2. the trigger type and its type-specific conditions;
3. whether the trigger may fire when no operator is online;
4. the visitor-facing message for your enabled locales;
5. whether the trigger is active.

By default, a trigger fires only while an operator is online. Enable Fire when no operators are online only when the resulting message also makes sense for the offline flow.

Page matching and timingCopy Anchor Link

Time on page uses a duration in seconds. Visited page accepts a page pattern such as /pricing*.

The Proactive invitation type can combine a delay with a specific page URL and optional returning-visitor or exit-intent requirements. Use it when a single behavior condition is too broad.

Programmatic auto-openCopy Anchor Link

Convor.init() also supports the autoOpen browser override with never, 5s, 30s, and exit-intent. That is a page-level widget override, not a dashboard trigger rule and not a replacement for Triggers when you need a named, localized, measurable trigger.

See Widget Customization for browser initialization options.