Signals you can connect
Nexmosphere's Xperience range covers the sensing patterns retail and venue signage networks actually deploy.
Presence & proximity
Xperience presence elements detect approach and departure in front of a screen, supplying anonymous approach and dwell events without cameras.
Dwell & traffic patterns
Aggregated counts of approaches and time-in-view, reported per screen, zone, or store — the audience layer for content and layout decisions.
RFID / Lift & Learn
Pick-up and put-down events on tagged products drive Lift & Learn content changes and item-level interaction analytics.
Touchless input
Gesture and air-touch style inputs where buttons and touchscreens are impractical — quick-service, healthcare, and high-traffic retail.
LiDAR sensing
Higher-resolution zone presence and flow measurement across larger areas, for entrances, aisles, and queue-adjacent screens.
Environmental & contextual inputs
Light, temperature, and other controller-connected inputs add context to playback and can trigger environment-aware automation.
How connection works
Sensors join the network through the same controllers and players you already deploy.
USB / serial controller to player
Nexmosphere Xperience controllers connect to the signage player over USB; events are read by the player-side application or agent.
Network / UDP event patterns
Where controllers or bridges expose network events, Relay ingests them as automation triggers alongside its other signal sources.
Element-to-screen mapping
Each sensor element — an RFID antenna, a presence zone, a LiDAR field — is mapped to a screen, shelf, or product position during configuration.
Health telemetry
Controller and element status surfaces alongside player health in Signal, so a dead sensor is as visible as a dark screen.
How our products use Nexmosphere signals
One sensor feed, four products — each consuming the events for its own job.
Relay — automation
Sensor events become triggers: start content when someone approaches, switch playlists on Lift & Learn pick-ups, and alert when elements drop offline.
Signal — monitoring
Controller and element health joins device telemetry; operators watch sensor uptime beside player uptime in one console.
Glass — measurement
Dwell, presence, and interaction events become audience and engagement metrics, correlated with playlists and, where authorized, commerce outcomes.
Scout — agents
Monitoring agents flag anomalies such as a Lift & Learn position that stops generating events or a presence zone that goes quiet during trading hours.
Configuration considerations
- Sensor placement and dwell thresholds are calibrated per location — a busy transit screen and a quiet showroom need different baselines.
- Element-to-screen mappings are kept in sync when store layouts or screen positions change, so analytics stay attributable.
- Controller models and firmware differ across estates; supported elements and events are validated during onboarding.
- Event volume and retention are matched to your analytics needs, not collected indiscriminately.
Privacy-conscious measurement
The standard analytics model uses presence, RFID, and LiDAR signals that count interactions, not identities — no cameras, no facial recognition, no personal identifiers. Events are aggregated by screen, zone, or store before they reach dashboards and reports.
This is the same privacy posture we apply across every data source in the platform: measure what content and environments do, not who individual visitors are.
Integration & access considerations
Nexmosphere hardware is purchased separately through Nexmosphere's own channels. Specific elements, events, and connection options depend on controller models, firmware, and your implementation scope — we validate the exact coverage during discovery rather than assuming every element behaves identically.
This is a supported integration target built on Nexmosphere's documented connection patterns; it does not imply a formal partnership or endorsement.
Keep exploring
Wire sensing into your network.
Tell us which Nexmosphere elements you run — or plan to — and we will map the automation and measurement they unlock.