Real Presence Detection
Knows whether the user is active or away, and whether the application tab is open or closed.
Status Checker detects whether the user is online or offline and whether the application tab is open or closed, letting you stop or trigger workflows and conditionals based on real presence instead of guesswork. Idle users stop consuming what they are not watching.
No data collected This plugin does not collect user data.
The documentation and the examples for this plugin are being updated. Open the current documentation
Knows whether the user is active or away, and whether the application tab is open or closed.
User active, user inactive, tab opened and tab closed, each one ready to start a workflow.
States expose the exact moment the user went online and the exact moment they went offline.
A separate state tells you whether the internet connection is active, apart from whether the user is paying attention.
Set how long without interaction counts as away, so the definition matches your application.
Stop recurring workflows and conditionals while nobody is watching, instead of paying for work no one sees.
In detail
Defines the maximum time that the user can be inactive. After that time, the values of the respective published states can be obtained to compose workflows or conditionals.
default20
Label that should appear when the user is online.
defaultOnline
Label that should appear when the user is offline.
defaultOffline
Values the element exposes for the rest of the page to read.
Returns whether the user is currently connected to the internet or not.
Where a workflow can start.
Action to be used when the user is active (online).
Action to be used when the user is inactive (offline).
Action to be used when the user opens the browser tab.
Action to be used when the user closes the browser tab.
By a maximum inactivity time that you configure. Once the user goes that long without interacting with the page, the state changes and the matching event fires, so the definition of away is yours and not a fixed number.
They are different signals and the plugin reports both. The tab events tell you the application tab was opened or closed; the user events tell you whether the person is interacting. A user can have the tab open and still be away, and that distinction is what lets you stop work without logging anyone out.
Yes. Besides the current status, the plugin exposes the exact moment of the last time the user went online and the last time they went offline, ready to be stored or displayed.
Yes, as a separate state. Losing connection and being away are different things, so they are reported separately and you can react to each one on its own.
The element works on its own, but the value comes from reacting to it: use the four events to trigger workflows and the exposed states in conditionals.