Skip to content

Commit cdc3281

Browse files
RadarAlRadarAl
authored
Update index.md
Sending a few updates to this documentation. Please reach out with any questions.
1 parent 094e9ff commit cdc3281

File tree

1 file changed

+29
-208
lines changed
  • src/connections/sources/catalog/cloud-apps/radar

1 file changed

+29
-208
lines changed

‎src/connections/sources/catalog/cloud-apps/radar/index.md

Lines changed: 29 additions & 208 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,21 @@
22
title: Radar Source
33
---
44

5-
Radar is the location platform for mobile apps. You can use Radar to add location context and tracking to your apps in less than ten lines of code. 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.
5+
[Radar](https://radar.com) 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.
66

7-
The Radar platform has three products: *Geofences*, *Insights*, and *Places*.
7+
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.
88

9-
- **[Geofences](https://www.onradar.com/documentation/geofences)**: Radar geofencing is more powerful than native iOS or Android geofencing, with cross-platform support for unlimited geofences, polygon geofences, stop detection, and accuracy down to 30 meters. Create geofences to receive the following events: Geofence Entered, Geofence Exited
9+
The Radar platform has three products: *Geofencing and Place Detection*, *Trip Tracking*, and *APIs for Geocoding and Search*.
1010

11-
- **[Insights](https://www.onradar.com/documentation/insights)**: Radar can learn a user's approximate home and work locations and tell you when a user is at home, at work, or traveling. Turn on Insights to receive the following events: Home Entered, Home Exited, Office Entered, Office Exited, Traveling Started, Traveling Stopped
11+
- **[Geofencing and Place Detection](https://radar.com/product/geofencing)**: 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 (ie: Starbucks, Walmart) and categories (ie: 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 insgihts, inform audience segmentation, and more.
1212

13-
- **[Places](https://www.onradar.com/documentation/places)**: Radar can tell you when a user visits a place, even if you haven't set up a geofence for that place. Places have category and chain information. Radar is integrated with Facebook Places, the same place database that powers Facebook and Instagram, with over 140M places worldwide. Turn on Places to receive the following events: Place Entered, Place Exited
13+
- **[Trip Tracking](https://radar.com/product/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.
14+
- **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.
15+
- **Delivery and Fleet Tracking** - Track your in-house delivery team via a driver app to be able to send ETA updates and real time arrival notifications to the end user who is expecting the delivery.
1416

15-
When you enable Radar as a Segment Source, you can forward Geofences, Insights, and Places data to your warehouse or destinations.
17+
- **[Search and Geocoding APIs](https://radar.com/product/api)**: Import and search your own location data, or tap into Radar's best-in-class address and POI datasets. Leverage these APIs to power store finders, address autocomplete, forward and reverse geocoding, IP geocoding, and more.
18+
19+
When you enable Radar as a Segment Source, you can forward Geofences, Places, Regions, and Trip Tracking data to your warehouse or destinations.
1620

1721
## Getting Started
1822

@@ -24,17 +28,20 @@ Radar will send the following events to your Segment warehouses and destinations
2428

2529
- Geofence Entered
2630
- Geofence Exited
27-
- Home Entered
28-
- Home Exited
29-
- Office Entered
30-
- Office Exited
31-
- Traveling Started
32-
- Traveling Stopped
3331
- Place Entered
3432
- Place Exited
33+
- Region Entered
34+
- Region Exited
35+
- Started Trip
36+
- Updated Trip
37+
- Approaching Trip Destination
38+
- Arrived at Trip Destination
39+
- Stopped Trip
3540

3641
## Radar Event Properties
3742

43+
Below are popular examples of events passed into Segment from Radar. For a complete view of the events that Radar passes into Segment, visit [Radar's Segment Events Mapping documentation](https://radar.com/documentation/integrations/segment#event-mapping)
44+
3845
### Geofence Entered
3946

4047
<table>
@@ -142,192 +149,6 @@ Radar will send the following events to your Segment warehouses and destinations
142149
</table>
143150

144151

145-
### Home Entered
146-
147-
<table>
148-
<tr>
149-
<td>Property Name</td>
150-
<td>Type</td>
151-
<td>Description</td>
152-
</tr>
153-
<tr>
154-
<td>latitude</td>
155-
<td>float</td>
156-
<td>The latitude of the user's location at the time of the event.</td>
157-
</tr>
158-
<tr>
159-
<td>longitude</td>
160-
<td>float</td>
161-
<td>The longitude of the user's location at the time of the event.</td>
162-
</tr>
163-
<tr>
164-
<td>accuracy</td>
165-
<td>float</td>
166-
<td>The accuracy of the user's location at the time of the event in meters.</td>
167-
</tr>
168-
<tr>
169-
<td>confidence</td>
170-
<td>string</td>
171-
<td>The confidence level of the event, one of low, medium, or high.</td>
172-
</tr>
173-
</table>
174-
175-
176-
### Home Exited
177-
178-
<table>
179-
<tr>
180-
<td>Property Name</td>
181-
<td>Type</td>
182-
<td>Description</td>
183-
</tr>
184-
<tr>
185-
<td>latitude</td>
186-
<td>float</td>
187-
<td>The latitude of the user at the time of the event.</td>
188-
</tr>
189-
<tr>
190-
<td>longitude</td>
191-
<td>float</td>
192-
<td>The longitude of the user at the time of the event.</td>
193-
</tr>
194-
<tr>
195-
<td>accuracy</td>
196-
<td>float</td>
197-
<td>The accuracy of the user's location at the time of the event in meters.</td>
198-
</tr>
199-
<tr>
200-
<td>confidence</td>
201-
<td>string</td>
202-
<td>The confidence level of the event, one of low, medium, or high.</td>
203-
</tr>
204-
</table>
205-
206-
207-
### Office Entered
208-
209-
<table>
210-
<tr>
211-
<td>Property Name</td>
212-
<td>Type</td>
213-
<td>Description</td>
214-
</tr>
215-
<tr>
216-
<td>latitude</td>
217-
<td>float</td>
218-
<td>The latitude of the user at the time of the event.</td>
219-
</tr>
220-
<tr>
221-
<td>longitude</td>
222-
<td>float</td>
223-
<td>The longitude of the user at the time of the event.</td>
224-
</tr>
225-
<tr>
226-
<td>accuracy</td>
227-
<td>float</td>
228-
<td>The accuracy of the user's location at the time of the event in meters.</td>
229-
</tr>
230-
<tr>
231-
<td>confidence</td>
232-
<td>string</td>
233-
<td>The confidence level of the event, one of low, medium, or high.</td>
234-
</tr>
235-
</table>
236-
237-
238-
### Office Exited
239-
240-
<table>
241-
<tr>
242-
<td>Property Name</td>
243-
<td>Type</td>
244-
<td>Description</td>
245-
</tr>
246-
<tr>
247-
<td>latitude</td>
248-
<td>float</td>
249-
<td>The latitude of the user at the time of the event.</td>
250-
</tr>
251-
<tr>
252-
<td>longitude</td>
253-
<td>float</td>
254-
<td>The longitude of the user at the time of the event.</td>
255-
</tr>
256-
<tr>
257-
<td>accuracy</td>
258-
<td>float</td>
259-
<td>The accuracy of the user's location at the time of the event in meters.</td>
260-
</tr>
261-
<tr>
262-
<td>confidence</td>
263-
<td>string</td>
264-
<td>The confidence level of the event, one of low, medium, or high.</td>
265-
</tr>
266-
</table>
267-
268-
269-
### Traveling Started
270-
271-
<table>
272-
<tr>
273-
<td>Property Name</td>
274-
<td>Type</td>
275-
<td>Description</td>
276-
</tr>
277-
<tr>
278-
<td>latitude</td>
279-
<td>float</td>
280-
<td>The latitude of the user at the time of the event.</td>
281-
</tr>
282-
<tr>
283-
<td>longitude</td>
284-
<td>float</td>
285-
<td>The longitude of the user at the time of the event.</td>
286-
</tr>
287-
<tr>
288-
<td>accuracy</td>
289-
<td>float</td>
290-
<td>The accuracy of the user's location at the time of the event in meters.</td>
291-
</tr>
292-
<tr>
293-
<td>confidence</td>
294-
<td>string</td>
295-
<td>The confidence level of the event, one of low, medium, or high.</td>
296-
</tr>
297-
</table>
298-
299-
300-
### Traveling Stopped
301-
302-
<table>
303-
<tr>
304-
<td>Property Name</td>
305-
<td>Type</td>
306-
<td>Description</td>
307-
</tr>
308-
<tr>
309-
<td>latitude</td>
310-
<td>float</td>
311-
<td>The latitude of the user at the time of the event.</td>
312-
</tr>
313-
<tr>
314-
<td>longitude</td>
315-
<td>float</td>
316-
<td>The longitude of the user at the time of the event.</td>
317-
</tr>
318-
<tr>
319-
<td>accuracy</td>
320-
<td>float</td>
321-
<td>The accuracy of the user's location at the time of the event in meters.</td>
322-
</tr>
323-
<tr>
324-
<td>confidence</td>
325-
<td>string</td>
326-
<td>The confidence level of the event, one of low, medium, or high.</td>
327-
</tr>
328-
</table>
329-
330-
331152
### Place Entered
332153

333154
<table>
@@ -369,17 +190,17 @@ Radar will send the following events to your Segment warehouses and destinations
369190
<tr>
370191
<td>place_categories</td>
371192
<td>array <string></td>
372-
<td>List of the [categories of the place](https://www.onradar.com/documentation/places/categories). </td>
193+
<td>List of the [categories of the place](https://www.radar.com/documentation/places/categories). </td>
373194
</tr>
374195
<tr>
375196
<td>place_chain_name</td>
376197
<td>string</td>
377-
<td>The name of the [chain of the place](https://www.onradar.com/documentation/places/chains).</td>
198+
<td>The name of the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
378199
</tr>
379200
<tr>
380201
<td>place_chain_slug</td>
381202
<td>string</td>
382-
<td>A human-readable unique ID for the [chain of the place](https://www.onradar.com/documentation/places/chains).</td>
203+
<td>A human-readable unique ID for the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
383204
</tr>
384205
<tr>
385206
<td>confidence</td>
@@ -430,17 +251,17 @@ Radar will send the following events to your Segment warehouses and destinations
430251
<tr>
431252
<td>place_categories</td>
432253
<td>array <string></td>
433-
<td>List of the [categories of the place](https://www.onradar.com/documentation/places/categories).</td>
254+
<td>List of the [categories of the place](https://www.radar.com/documentation/places/categories).</td>
434255
</tr>
435256
<tr>
436257
<td>place_chain_name</td>
437258
<td>string</td>
438-
<td>The name of the [chain of the place](https://www.onradar.com/documentation/places/chains).</td>
259+
<td>The name of the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
439260
</tr>
440261
<tr>
441262
<td>place_chain_slug</td>
442263
<td>string</td>
443-
<td>A human-readable unique ID for the [chain of the place](https://www.onradar.com/documentation/places/chains).</td>
264+
<td>A human-readable unique ID for the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
444265
</tr>
445266
<tr>
446267
<td>confidence</td>
@@ -457,7 +278,7 @@ Radar will send the following events to your Segment warehouses and destinations
457278

458279
## Radar User Traits
459280

460-
Radar will also send the following user traits to Segment, depending on Radar user state when Radar events are sent to Segment:
281+
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](https://radar.com/documentation/integrations/segment#user-mapping)
461282

462283
<table>
463284
<tr>
@@ -523,17 +344,17 @@ Radar will also send the following user traits to Segment, depending on Radar us
523344
<tr>
524345
<td>radar_place_categories</td>
525346
<td>array <string></td>
526-
<td>List of the [categories of the place](https://www.onradar.com/documentation/places/categories).</td>
347+
<td>List of the [categories of the place](https://www.radar.com/documentation/places/categories).</td>
527348
</tr>
528349
<tr>
529350
<td>radar_place_chain_name</td>
530351
<td>string</td>
531-
<td>The name of the [chain of the user's last known place](https://www.onradar.com/documentation/places/chains).</td>
352+
<td>The name of the [chain of the user's last known place](https://www.radar.com/documentation/places/chains).</td>
532353
</tr>
533354
<tr>
534355
<td>radar_place_chain_slug</td>
535356
<td>string</td>
536-
<td>A human-readable unique ID for the [chain of the user's last known place](https://www.onradar.com/documentation/places/chains).</td>
357+
<td>A human-readable unique ID for the [chain of the user's last known place](https://www.radar.com/documentation/places/chains).</td>
537358
</tr>
538359
<tr>
539360
<td>radar_insights_state_home</td>

0 commit comments

Comments
 (0)