Places uses our place database to detect when a user visits a place, chain, or category, even if you haven't set up geofences for those places.
Radar ingests and curates place data from multiple sources, providing you with a comprehensive view of the world.
Places provides the following user context:
Places also provides the following events:
Places is available on the Team plan and higher.
You can enable Places on the Settings page.
Alternatively, if you have your own custom place data, you can create geofences instead. Learn more about Geofences.
Radar generates a place entry event if a user stops at a place (i.e., when
true based on tracking options or when
true) matching filters with sufficient confidence, then a place exit event when the user leaves the place with sufficient confidence.
If a user is at their learned home or office location, Radar will not generate a place entry event. Learn more about Insights.
All place events have confidence levels. Confidence levels range from
1 (low) to
3 (high). Confidence is a function of the accuracy of the location reported by the device, the footprint of the place, the density of the area, the popularity of the place, and other signals.
You may decide to ignore events based on confidence levels.
Places may have one or more categories. Radar supports hundreds of categories, organized in a hierarchy. View the full list of categories.
You can listen for place events with specific categories. For example, to do something if a user is at an airport, on iOS:
Places may have a chain. Radar supports thousands of U.S. and international chains. View the full list of chains.
You can listen for place events with specific chains. For example, to do something when a user stops at a Starbucks, on Android:
To map Radar chain slugs to custom IDs, set Chain Mappings under Places on the Settings page.
You can set a JSON string representing a dictionary with keys and values of type string.
For example, to map
Custom chain IDs will be exposed as
place.chain.externalId in user context and events.
To map Radar chain slugs to custom metadata, set Chain Metadata under Places on the Settings page.
You can set a JSON string with values of type dictionary, each with between 1 and 16 keys and values of type string, boolean, or number.
For example, to map
Custom chain metadata will be exposed as
place.chain.metadata in user context and events.
Finally, places may have a group, distinct from chain or categories. A group is a curated list of places with special metadata, like
major-us-sports-venue-stadium. View the full list of groups.
We recommend filtering events to specific categories or chains under Places on the Settings page.
For example, to monitor only fast food restaurants, you might add
fast-food-restaurant to category filters, or add
mcdonalds, and others to chain filters.
You can accept or reject places events after user check-ins or other forms of verification. Event verifications will be used to improve the accuracy and confidence level of future events.
For example, to accept an event on iOS: