Good to know: Event Cloud source
The Radar Source is an event source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
This source is supported in US data processing regions.
The Radar source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.
Radar is the leading geofencing and location tracking platform. You can use Radar SDKs and APIs to build a wide range of location-based product and service experiences, including pickup and delivery tracking, location-triggered notifications, location verification, store locators, address autocomplete, and more.
The Radar Segment Source is a Cloud-mode event source. Instead of packaging Radar’s SDK using Segment as a wrapper, you include, configure, and initialize their SDK separately. Radar then sends all events that it detects and infers to Segment using its servers. As a result, only destinations that allow Cloud-mode are compatible with the Radar source.
The Radar platform has three products: Geofencing and Place Detection, Trip Tracking, and APIs for Geocoding and Search.
Geofencing and Place Detection: Radar geofencing is more powerful than native iOS or Android geofencing, with cross-platform support for unlimited geofences, polygon and isochrone geofences, stop detection, and accuracy down to 10 meters. Radar’s Places feature allows you to instantly configure geofencing around thousands of chains (i.e.: Starbucks, Walmart) and categories (i.e.: airports, restaurants) with the click of a button. Radar will generate a real time event on entry or exit of a custom or Places geofence to trigger messaging, drive behavioral insights, inform audience segmentation, and more.
- Trip Tracking: Radar has a powerful trip tracking product that allows a brand to personalize the pickup and delivery experience for brick and mortar brands and logistics use cases.
- Curbside Pickup and BOPIS - When a user places an order for pickup, offer them the option to share location to reduce wait times and, for restaurants, increase food freshness. Radar will track the user’s location while en route, provide staff with a real time ETA, and produce an arrival event which can trigger an Iterable notification to the user and/or staff. These features optimize operation efficiencies at the store and lead to a much stronger customer experience.
- Delivery and Fleet Tracking - Track your in-house delivery team using a driver app to be able to send ETA updates and real time arrival notifications to the end user who is expecting the delivery.
- Search and Geocoding APIs: Import and search your own location data, or tap into Radar’s best-in-class address and POI datasets. Use these APIs to power store finders, address autocomplete, forward and reverse geocoding, IP geocoding, and more.
When you enable Radar as a Segment Source, you can forward Geofences, Places, Regions, and Trip Tracking data to your warehouse or destinations.
The Radar source is currently in beta. Contact Radar to configure this source.
Radar will send the following events to your Segment warehouses and destinations, depending on what products you enable in Radar.
- Geofence Entered
- Geofence Exited
- Place Entered
- Place Exited
- Region Entered
- Region Exited
- Trip Started
- Trip Updated
- Trip Approaching Destination
- Trip Arrived Destination
- Trip Stopped
For a complete view of the events that Radar passes into Segment, visit Radar’s Segment Events Mapping documentation.
Radar User Traits
Radar will also send the following user traits to Segment, depending on Radar user state when Radar events are sent to Segment. For a complete view of the user attributes that Radar passes into Segment, visit Radar’s Segment User Mapping documentation
|radar_id||string||The ID of the user, provided by Radar.|
|radar_location_latitude||float||The latitude of the user user’s last known location.|
|radar_location_longitude||float||The longitude of the user’s last known location.|
|radar_updated_at||string||The datetime when the user’s location was last updated. ISO string in UTC.|
||An array of IDs of the user’s last known geofences.|
||An array of descriptions of the user’s last known geofences.|
||An array of tags of the user’s last known geofences.|
||An array of external IDs of the user’s last known geofences.|
|radar_place_id||string||The ID of the user’s last known place, provided by Radar.|
|radar_place_name||string||The name of the user’s last known place.|
|radar_place_facebook_id||string||The Facebook ID of the user’s last known place.|
||List of the categories of the place.|
|radar_place_chain_name||string||The name of the chain of the user’s last known place.|
|radar_place_chain_slug||string||A human-readable unique ID for the chain of the user’s last known place.|
|radar_insights_state_home||boolean||A boolean indicating whether the user is at home, based on learned home location.|
|radar_insights_state_office||boolean||A boolean indicating whether the user is at the office, based on learned office location.|
|radar_insights_state_traveling||boolean||A boolean indicating whether the user is traveling, based on learned home location.|
This page was last modified: 25 Apr 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!