Contact your Radar customer success manager to enable user insights for your project.

How it works
Radar processes recent stopped locations each day. It uses signals such as repeat visits and the local time of each visit to identify and rank likely home and work locations. When Radar has sufficient confidence for an inferred location, new location updates begin producing the following insight states:- At home: The user is within their inferred home bubble.
- At work: The user is within their inferred work bubble.
- Traveling: The user is far from their inferred home area.
- Commuting: The user is along an inferred route between home and work.
Locations derived from user insights are probabilistic and can change as Radar receives more location history.
User context
When user insights are enabled and Radar has inferred at least one usable home or work location, track responses include alocationInsights object on the user:
locationInsights object is omitted when Radar does not have enough historical evidence to infer a usable home or work location. The commuting field can be omitted when commute status is unavailable.
Inferred home and work coordinates are not included in SDK responses.
Events
Radar generates events when a user’s location update changes the insight state:user.entered_homeuser.exited_homeuser.entered_workuser.exited_workuser.started_travelinguser.stopped_travelinguser.started_commutinguser.stopped_commuting
Test user insights
Because user insights depend on historical patterns, they cannot be created from a single location update. After Radar has processed enough location history for a test user:- Open the Simulator in the Radar dashboard.
- Select the user and enable the Insights map layer to inspect the inferred home, work, and commute corridors.
- Simulate location updates in and out of those areas.
- Inspect
user.locationInsightsin the tracking response and verify state changes on the Events page.