# Visitor actions and events

Integrations can record visitor actions and signal named events that run configured visitor rules.

*Release 3.3 · developer, operator, supervisor*

**Settings › Events › Visitor Events**

## What it is

INSIDE can record an action reported by a visitor integration and use actions to trigger visitor rules. An integration can also signal an event by name. Recording an interaction and signalling a named event are separate operations.

## Who uses it and why

- Developers report relevant website interactions and connect them to agreed event labels.
- Operators receive the messages, alerts or state changes configured for those interactions.
- Supervisors review whether the resulting engagement rules match the intended experience.

## Where to find it

Configure rules at **Settings › Events › Visitor Events** with the **Settings** or **Manager** role. **View Only** restrictions prevent editing. Action capture itself comes from the integration. The result appears wherever the configured rule acts, such as an operator alert or visitor message.

## How it works

A reported action contains a type, an item identifier, an action name and optional structured details. INSIDE associates the captured action with the visitor, website and current subsite where available.

By default, reporting an action also evaluates action-triggered visitor events and updates visitor assignment. Integrations can request recording only, which skips that event evaluation and assignment step.

A named-event signal selects visitor-event rules with the matching label. Their configuration determines what happens next. An event label alone does not create a rule or guarantee that its conditions will pass.

Normal persistent visitors can have action history saved. Memory-only visitors do not save that action log in the same way. Sending an event is therefore not a substitute for a separately designed audit or delivery-confirmation process.

## Configure it

Agree the interaction names and event labels with your developer. Create the corresponding rule in **Visitor Events**, set its conditions and actions, and test the result with a visitor who meets those conditions.

Decide whether an interaction should both trigger rules and be recorded, or whether the integration should record it only. Use named events when the integration needs to signal a specific configured rule label.

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Access visitor-event configuration; View Only restrictions prevent editing. |
| Manager | Access visitor-event configuration; View Only restrictions prevent editing. |

## Limits and good to know

- Action type, item identifier and action name have 50-character storage limits. Use short, stable names.
- Extra details are optional. Only include information needed for the interaction.
- A successful action request is not a durable history receipt.
- Automatic remote notifications have their own audiences. Capturing an action does not broadcast it to every operator or visitor.
- The current visitor and applicable consent mode affect what can be associated and retained.

## Depends on and works with

### This feature uses

- **Requires** [Visitor identity](VIS-001.md): Captured actions and custom triggers need a current visitor context.
- **Configured in** [Visitor event rules and actions](ENG-001.md): Visitor-event configuration determines the rules associated with action and named-event triggers.
- **Configured in** [Visitor event targeting conditions](ENG-002.md): Rule conditions decide whether a triggered visitor event runs its actions.
- **Configured in** [Visitor event updates to customer context](ENG-007.md): Visitor-event action settings choose the state changes and other actions performed after a matching trigger.
- **Configured in** [Cookie consent and opting out](VIS-018.md): Memory-only visitors do not persist action history in the same way as normal visitors.

### Used by

- **Enhances** [Operator notifications and alerts](CON-018.md): Tracked activity supplies event text for visitor bubbles.
- **Enhances** [Visitor event rules and actions](ENG-001.md): Captured actions and labelled integration events provide optional triggers for visitor rules.

## FAQ and troubleshooting

### Why was an action recorded without running the rule?

Check whether the integration requested recording only. Also check the rule's trigger, enabled state and conditions.

### Why does signalling our event name do nothing?

Confirm that a visitor-event rule uses the same label and that the visitor meets its conditions.

### Does every captured action appear as a chat message?

No. A message appears only when the relevant integration or configured rule sends one.

### Why is there no saved action history for a memory-only visitor?

Memory-only visitors do not persist the normal visitor action log. Check the consent and tracking mode used for that visit.