INSIDE 3.3
ENG-001

Visitor event rules and actions

Run automatic actions when a visitor meets your event rules.

admindeveloper
DraftThis article hasn't been reviewed yet.
Where to find it
Settings › Events › Visitor Events

What it is

Visitor Events let you respond automatically to visitor activity. An event combines a trigger, visitor filters and actions. You can use it to offer help, display information, alert operators or update visitor information.

Who uses it and why

  • Administrators with the Settings or Manager role create and maintain event rules.
  • Developers connect labelled events and custom actions to website integrations.

Where to find it

The Settings or Manager role grants access, subject to delegated permissions. Open Settings › Events › Visitor Events. You can search, copy, edit, enable or disable events in the list. View Only access prevents changes.

How it works

  1. The activity selected in Test for this event causes INSIDE to check the rule.
  2. INSIDE checks that the event is enabled, the visitor has a session, the cooldown has elapsed and all visitor filters pass.
  3. Any date and time restrictions must also pass.
  4. INSIDE runs the configured actions in sequence and records the cooldown when an action reports success.

Lower Priority numbers run first. A successful event does not stop INSIDE checking other events for the same trigger.

Triggers include On Page View, After Page View, On Connect, On New Visit, On Queue, On Form Update, On Order Update, On Sale, On Chat Message, Time On Page, Time On Site, Popup Click, Event Listener and On Watch Video.

Time On Site is checked after page views. Time On Page waits for the page timer, then checks the current page, visitor filters, schedule and cooldown again. Navigating away prevents the old page's delayed action from running.

Configure it

Create an event, enter a unique Name and a Description, select its Type and choose Test for this event. Add visitor filters and complete the fields for the chosen action. Add Dates restrictions if needed, then save and enable the event.

New events normally start with a Cooldown of 10 minutes. Selecting Proactive Chat for a new event changes that initial value to 1,440 minutes. Check the value before saving. Use Shared Cooldown to coordinate related rules; each rule still uses its own waiting interval.

For an Event Listener, enter a Label for your integration. Several events can share a label and are checked in priority order.

Settings

Setting Where Applies to Default Who can change it What it does
Enabled Settings › Events › Visitor Events website Off Settings role, Manager roleAllows the event to run when its other checks pass.
Type Settings › Events › Visitor Events website Not set: choose an event type before saving Settings role, Manager roleSelects the main action, such as Proactive Chat or Visitor Popup.
Test for this event Settings › Events › Visitor Events website On Page View Settings role, Manager roleSelects when INSIDE checks the rule.
Priority Settings › Events › Visitor Events website Not set: runs after events with a numbered priority Settings role, Manager roleLower numbers run before higher numbers; events without a priority run last.
Cooldown Settings › Events › Visitor Events website 10 minutes; selecting Proactive Chat for a new event changes it to 1,440 minutes (24 hours) Settings role, Manager roleSets the minimum interval in minutes between recorded executions for this visitor's session.
Shared Cooldown Settings › Events › Visitor Events website Not set: uses this event's own cooldown history Settings role, Manager roleUses another event's cooldown history to coordinate related events.
Minimum Time Settings › Events › Visitor Events website 0 seconds Settings role, Manager roleSets the earliest qualifying time in seconds for time-based triggers.

Fields

Field Where Required What it is for
Name Settings › Events › Visitor Events Yes Identifies the event in the event list.
Description Settings › Events › Visitor Events Yes Explains the purpose of the event.
Label Settings › Events › Visitor Events Yes Required when Event Listener is selected; identifies events to trigger through an integration.

Permissions

Permission Lets you
Settings Access Visitor Events, subject to delegated permissions.
Manager Access Visitor Events, subject to delegated permissions.
View Only View permitted configuration without editing it.

Limits and good to know

  • An event with no visitor filters does not run. Removing every filter does not mean everyone qualifies.
  • A cooldown of zero removes the event's waiting interval. For a positive cooldown, elapsed time must be greater than the configured interval.
  • Event cooldowns belong to the visitor's session. Proactive chat also has a separate website-wide check against the visitor's previous chat.
  • Scheduling a task alone does not record an event cooldown. Use careful targeting for task-start rules.
  • A recorded event execution does not establish that the visitor saw or accepted its result.

Depends on and works with

RequiresConfigured byEnhances
+3 more · this feature uses
+18 more · used by
View all connections as a list

This feature uses

Used by

FAQ and troubleshooting

Why does my enabled event do nothing?

Check the trigger, visitor filters, Dates, cooldown and action-specific requirements. At least one visitor filter is needed.

Why do two matching events run?

Priority controls order. It does not select a single winning event. Use filters and Shared Cooldown where related events need coordination.

Why does Time On Site not fire as soon as the threshold passes?

INSIDE checks it after a page view. Use Time On Page when the action should follow a wait on the current page.

Why did changing pages cancel the delayed popup?

The page timer checks that the visitor is still on the qualifying page before running the action.

INSIDE 3.3 · Source commit 992abb980bContent is a pre-release draft© 2026 Powerfront