Capability
Struggle Signals
The three behaviors that mean a user is fighting your product rather than using it: a rage click, a navigation loop, and a pause far longer than the page deserves.
Struggle hotspot
I4412 sessions struggled on /onboarding/documents this window.
- Rage click216 sessions
- Navigation loop134 sessions
- Dwell62 sessions
Create a flow here
What it does
Drop-off tells you where users stop. Struggle signals tell you what they were doing in the minute before they stopped, which is usually the difference between a step that is confusing and a step that is broken. These reach your team only. ARCY never interrupts a user because it saw one.
- Rage click: the same control pressed three times inside a second
- Navigation loop: the same route reached three times inside a minute
- Dwell: a pause on a page far longer than that page usually takes
- Grouped into a hotspot, per route, with the action ARCY can take there
How it works
- Behavior is derived, never stored as a verdictThere is no struggle table. A signal is computed over the interaction traces you already send, at the moment the question is asked, so retuning a threshold re-derives every past week rather than leaving old rows behind.
- The thresholds are deliberate, and the same everywhereThree clicks, because two is a double click. Three visits to a route, because two is the back button working. They are not tunable per environment, so two environments' numbers stay comparable.
- Signals become a hotspot with an actionConcentrated signals on one route surface as an insight naming the route, the behavior and the affected sessions, with a control that opens a flow there.
The technical detail is in the documentation
The documentation is the maintained version, written for the person who will install this. This page does not restate it.
Read the documentationRelated
See where your product is being fought
Book a walkthrough and we will show you the routes your own users struggle on most.