Radar
Overview
Radar is a location context platform for location-based targeted app experiences. Radar data can be used to serve personalized experiences in real-time based on a user's current surroundings.
Integrating Radar and Lytics enables you to access Radar's real-time location data in Lytics profiles and audience definitions. With Lytics Experiences powered by audiences using Radar data, you can deliver multi-channel experiences based on location in real-time such as email or mobile push.
The Radar event integration sends user and activity data to Lytics.
Event Integration
The Radar event integration with Lytics imports Radar's location context data in real-time which surface as user profile fields which can be used in the Lytics audience builder. Lytics Audiences using Radar data can be used to activate location-based experiences in real-time.
Integration Details
- Implementation Type: Server-side Integration
- Implementation Tactic: Webhook Integration
- Frequency: Real-time Integration
- Resulting Data: Raw Event Data which is automatically mapped to User Fields on new or existing User Profiles.
The integration is an event integration configured in the Radar application which sends Radar data to the Lytics streams radar_events
and radar_users
.
Fields
See Radar's Lytics documentation reference for details on how Radar data is received by Lytics streams. The tables below describe how that raw data the streams are mapped as user fields on the Lytics profile.
Unique identifiers are not included in the default mapping for these streams. As mentioned below in the configuration step, during the integrations setup process please discuss which fields you would like to use as unique identifiers for your Radar data.
The following fields are included in the default mapping of the radar_users
stream:
Source Field | Lytics User Field | Description | Type |
---|---|---|---|
radarLocationLatitude | radar_location_latitude | Current Radar Location Latitude | string |
radarLocationLongitude | radar_location_longitude | Current Radar Location Longitude | string |
radarUpdatedAt | radar_updated_at | Current Radar Location Update | date |
radarGeofenceIds | radar_geofence_ids | Current Radar Geofence Ids | []string |
radarGeofenceDescriptions | radar_geofence_descriptions | Current Radar Geofence Descriptions | []string |
radarGeofenceTags | radar_geofence_tags | Current Radar Geofence Tags | []string |
radarGeofenceExternalIds | radar_geofence_external_ids | Current Radar Geofence External Ids | []string |
radarRegionCountryCode | radar_region_country_code | Current Radar Region Country Code | string |
radarRegionCountryName | radar_region_country_name | Current Radar Region Country Name | string |
radarRegionStateCode | radar_region_state_code | Current Radar Region State Code | string |
radarRegionStateName | radar_region_state_name | Current Radar Region State Name | string |
radarRegionPostalCode | radar_region_postal_code | Current Radar Region Postal Code | string |
radarRegionDMACode | radar_region_dma_code | Current Radar Region DMA Code | string |
radarRegionDMAName | radar_region_dma_name | Current Radar Region DMA Name | string |
radarPlaceId | radar_place_id | Current Radar Place Id | string |
radarPlaceName | radar_place_name | Current Radar Place Name | string |
radarPlaceFacebookId | radar_place_facebook_id | Current Radar Place Facebook Id | string |
radarPlaceCategories | radar_place_categories | Current Radar Place Categories | []string |
radarPlaceChainSlug | radar_place_chain_slug | Current Radar Place Chain Slug | string |
radarPlaceChainName | radar_place_chain_name | Current Radar Place Chain Name | string |
radarPlaceChainExternalId | radar_place_chain_external_id | Current Radar Place Chain External Id | string |
radarInsightsStateHome | radar_insights_state_home | Radar Insights State Home | string |
radarInsightsStateOffice | radar_insights_state_office | Radar Insights State Office | string |
radarInsightsStateTraveling | radar_insights_state_traveling | Radar Insights State Traveling | string |
The following fields are included in the default mapping of the radar_events
stream:
Source Field | Lytics User Field | Description | Type |
---|---|---|---|
geofenceId | last_entered_ts_by_geofenceId last_exited_ts_by_geofenceId | Last Entered Timestamp by Geofence Id | map[string]date map[string]date |
geofenceDescription | last_entered_ts_by_geofenceDescription last_exited_ts_by_geofenceDescription | Last Entered Timestamp by Geofence Description | map[string]date map[string]date |
geofenceExternalId | last_entered_ts_by_geofenceExtId last_exited_ts_by_geofenceExtId | Last Entered Timestamp by Geofence External ID Last Exited Timestamp by Geofence External ID | map[string]date map[string]date |
geofenceTag | last_geofence_tags | Last Geofence Tags | []string |
placeId | last_entered_ts_by_placeId last_exited_ts_by_placeId | Last Entered Timestamp by Place ID Last Exited Timestamp by Place ID | map[string]date map[string]date |
placeName | last_entered_ts_by_placeName last_exited_ts_by_placeName | Last Entered Timestamp by Place Name Last Exited Timestamp by Place Name | map[string]date map[string]date |
placeCategories | last_place_categories | Last Place Categories | []string |
timestamp | last_entered_home last_exited_home last_entered_office last_started_traveling last_stopped_traveling | Last Entered Home Last Exited Home Last Entered Office Last Started Traveling Last Stopped Traveling | date date date date date |
regionCode | last_entered_ts_by_regionCode last_exited_ts_by_regionCode | Last Entered Timestamp by Country Code Last Exited Timestamp by Country Code | map[string]date map[string]date |
regionCode | last_entered_ts_by_regionCode last_exited_ts_by_regionCode | Last Entered Timestamp by State Code Last Exited Timestamp by State Code | map[string]date map[string]date |
regionCode | last_entered_ts_by_regionCode last_exited_ts_by_regionCode | Last Entered Timestamp by Region DMA Last Exited Timestamp by Region DMA | map[string]date map[string]date |
regionName | last_entered_ts_by_regionName last_exited_ts_by_regionName | Last Entered Timestamp by Country Last Exited Timestamp by Country | map[string]date map[string]date |
regionName | last_entered_ts_by_regionName last_exited_ts_by_regionName | Last Entered Timestamp by State Last Exited Timestamp by State | map[string]date map[string]date |
regionName | last_entered_ts_by_regionName last_exited_ts_by_regionName | Last Entered Timestamp by Region DMA Last Exited Timestamp by Region DMA | map[string]date map[string]date |
Configuration
Listed below are instructions on how to setup and configure the Radar event integration.
- Contact your Lytics account manager to enable the Radar integration. Please include details regarding the fields you would like to use as unique identifiers for this integration.
- Generate an API token with the Data Manager role and no expiration date.
- In the Radar app, follow the configuration steps described in the Radar documentation for this integration.
Once the integration is enabled, you should see data being received in the radar_events
and the radar_users
streams.
Updated over 1 year ago