Sessions and returning guests
Recognising returning devices keeps sign-in effortless for regulars while still counting every visit, and turns sign-in data into footfall and retention insight.
When you'd use it
For understanding how busy a venue is, who returns and who is slipping away, and for keeping repeat sign-ins frictionless for regulars.
How it behaves
Sessions are tracked at the device level and tied to a profile on sign-in. A returning device reconnects without a fresh sign-in, but the visit is still recorded, so visit counts and last-seen stay accurate.
Whole classes of device, such as staff phones, can be set to auto-authenticate and skip the portal entirely. How long a session lasts is set by a network policy, an overall session timeout and an idle timeout, and the guest’s status screen shows their time left.
Aggregated over weeks and months, sign-in data shows who the venue’s regulars are, who has not been in for a while, and how busy the venue really is by day and time. It feeds the reporting views for login volume, new versus returning guests, unique guests and dwell.
Configuration and options
- Session length
- An overall session timeout and an idle timeout, set by network policy.
- Device recognition
- Returning devices reconnect without a fresh sign-in.
- Auto-authenticate devices
- Whole device classes can bypass the portal.
- Visit tracking
- Every reconnection is still counted as a visit.
- Footfall insight
- Login volume, new versus returning, unique guests and dwell.
Good to know
Anonymous device sessions are only tied to a guest once they sign in.
Recognising a returning device keeps sign-in effortless for regulars while still counting the visit.
Lapsed regulars, guests who used to come in but have not recently, surface as a group the venue can target with a win-back.