Behavior signals are the category of Signals that describe how an end user interacted with an Inquiry rather than what they submitted. They cover patterns in how the user filled the flow in, session activity, and signs of spoofing or tampering. Persona collects them automatically and populates them when the Inquiry is completed.
Like all Signals, they do not produce a pass or fail result. They add context you can weigh alongside Verification results when you decide what to do with an Inquiry.
Where behavior signals appear
- On a single Inquiry. Go to Inquiries > All Inquiries and select the Inquiry. The Overview tab summarizes the Featured Signals, and the Signals tab has a Behavioral section alongside Network, Device, and All Signals.
- Across your Inquiries. Go to Inquiries > Signals for the distribution and time series views, which show how a Signal’s values are spread across your users and how they have trended.
What you get
Individual behavior signals include session count, shortcut usage, off-hours activity, and geolocation delta between sessions. Two roll-ups summarize the rest:
- Behavior Threat Level returns
low,medium, orhighat Inquiry completion, from a proprietary Persona model that combines multiple behavior signals associated with fraud. - Bot Score returns a number from 0 to 100 indicating the likelihood that the Inquiry was submitted by a bot.
The full list of Signals and their definitions lives in the Inquiry Signals reference in the Persona Dashboard. For each behavior signal’s definition and how to read the rating on an Inquiry you are reviewing, see Understanding Behavior Signals in an Inquiry.
Which Inquiries collect them
Behavior signals are collected in Inquiries that use an integration method in which Persona supplies the user interface:
- Embedded Flow
- Hosted Flow
- Mobile SDKs
They are not available for Server API-based integrations, where Persona does not supply the interface the user moves through.
Which Signals an Inquiry collects is also a template setting. In Flow Editor, go to Settings > Signals to choose what the Persona widget collects from the user’s session and device. Only Signals configured on the template appear in the Signals tab or come back from the API, so an absent signal is usually a template that does not collect it yet. See How to Use Signals for the full procedure.
When to reach for them
Reach for behavior signals when you are triaging which Inquiries deserve a human look, or building automation that routes them. You can use a Workflow to act on an Inquiry based on its Behavior Threat Level, for example by using inquiry.risk_label as a condition to create a Case for review. The Fraud Signals Solution covers that pattern end to end.
Do not read a single elevated signal as a verdict. Patterns across several Signals are more meaningful than any one of them, which is what Interpreting Signals is about.
Plans Explained
Behavior signals are part of Signals, which every plan includes.
Behavior signals by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Behavior signals | Available | Available | Available | Available |