Skip to content

Commit ee1cbc5

Browse files
forstisabellaforstisabella
committed
Removing HTML tables, replacing them with links to the Radar documentation, adding style guide changes
1 parent f85968e commit ee1cbc5

File tree

1 file changed

+17
-251
lines changed
  • src/connections/sources/catalog/cloud-apps/radar

1 file changed

+17
-251
lines changed

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

Lines changed: 17 additions & 251 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ The Radar platform has three products: *Geofencing and Place Detection*, *Trip T
1212

1313
- **[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.
1414
- **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.
15+
- **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.
1616

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.
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. Use these APIs to power store finders, address autocomplete, forward and reverse geocoding, IP geocoding, and more.
1818

1919
When you enable Radar as a Segment Source, you can forward Geofences, Places, Regions, and Trip Tracking data to your warehouse or destinations.
2020

@@ -26,255 +26,21 @@ The Radar source is currently in beta. Contact Radar to configure this source.
2626

2727
Radar will send the following events to your Segment warehouses and destinations, depending on what products you enable in Radar.
2828

29-
- Geofence Entered
30-
- Geofence Exited
31-
- Place Entered
32-
- Place Exited
33-
- Region Entered
34-
- Region Exited
35-
- Trip Started
36-
- Trip Updated
37-
- Trip Approaching Destination
38-
- Trip Arrived Destination
39-
- Trip Stopped
40-
41-
## Radar Event Properties
42-
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-
45-
### Geofence Entered
46-
47-
<table>
48-
<tr>
49-
<td>Property Name</td>
50-
<td>Type</td>
51-
<td>Description</td>
52-
</tr>
53-
<tr>
54-
<td>latitude</td>
55-
<td>float</td>
56-
<td>The latitude of the user's location at the time of the event.</td>
57-
</tr>
58-
<tr>
59-
<td>longitude</td>
60-
<td>float</td>
61-
<td>The longitude of the user's location at the time of the event.</td>
62-
</tr>
63-
<tr>
64-
<td>accuracy</td>
65-
<td>float</td>
66-
<td>The accuracy of the user's location at the time of the event in meters.</td>
67-
</tr>
68-
<tr>
69-
<td>geofence_id</td>
70-
<td>string</td>
71-
<td>The ID of the geofence, provided by Radar.</td>
72-
</tr>
73-
<tr>
74-
<td>geofence_description</td>
75-
<td>string</td>
76-
<td>The description of the geofence.</td>
77-
</tr>
78-
<tr>
79-
<td>geofence_tag</td>
80-
<td>string</td>
81-
<td>The tag of the geofence.</td>
82-
</tr>
83-
<tr>
84-
<td>geofence_external_id</td>
85-
<td>string</td>
86-
<td>The external ID of the geofence.</td>
87-
</tr>
88-
<tr>
89-
<td>confidence</td>
90-
<td>string</td>
91-
<td>The confidence level of the event, one of low, medium, or high.</td>
92-
</tr>
93-
</table>
94-
95-
96-
### Geofence Exited
97-
98-
<table>
99-
<tr>
100-
<td>Property Name</td>
101-
<td>Type</td>
102-
<td>Description</td>
103-
</tr>
104-
<tr>
105-
<td>latitude</td>
106-
<td>float</td>
107-
<td>The latitude of the user's location at the time of the event.</td>
108-
</tr>
109-
<tr>
110-
<td>longitude</td>
111-
<td>float</td>
112-
<td>The longitude of the user's location at the time of the event.</td>
113-
</tr>
114-
<tr>
115-
<td>accuracy</td>
116-
<td>float</td>
117-
<td>The accuracy of the user's location at the time of the event in meters.</td>
118-
</tr>
119-
<tr>
120-
<td>geofence_id</td>
121-
<td>string</td>
122-
<td>The ID of the geofence, provided by Radar.</td>
123-
</tr>
124-
<tr>
125-
<td>geofence_description</td>
126-
<td>string</td>
127-
<td>The description of the geofence.</td>
128-
</tr>
129-
<tr>
130-
<td>geofence_tag</td>
131-
<td>string</td>
132-
<td>The tag of the geofence.</td>
133-
</tr>
134-
<tr>
135-
<td>geofence_external_id</td>
136-
<td>string</td>
137-
<td>The external ID of the geofence.</td>
138-
</tr>
139-
<tr>
140-
<td>confidence</td>
141-
<td>string</td>
142-
<td>The confidence level of the event, one of low, medium, or high.</td>
143-
</tr>
144-
<tr>
145-
<td>duration</td>
146-
<td>float</td>
147-
<td>The duration between Geofence Entered and Geofence Exited events, in minutes.</td>
148-
</tr>
149-
</table>
150-
151-
152-
### Place Entered
153-
154-
<table>
155-
<tr>
156-
<td>Property Name</td>
157-
<td>Type</td>
158-
<td>Description</td>
159-
</tr>
160-
<tr>
161-
<td>latitude</td>
162-
<td>float</td>
163-
<td>The latitude of the user at the time of the event.</td>
164-
</tr>
165-
<tr>
166-
<td>longitude</td>
167-
<td>float</td>
168-
<td>The longitude of the user at the time of the event.</td>
169-
</tr>
170-
<tr>
171-
<td>accuracy</td>
172-
<td>float</td>
173-
<td>The accuracy of the user's location at the time of the event in meters.</td>
174-
</tr>
175-
<tr>
176-
<td>place_id</td>
177-
<td>string</td>
178-
<td>The ID of the place, provided by Radar.</td>
179-
</tr>
180-
<tr>
181-
<td>place_name</td>
182-
<td>string</td>
183-
<td>The name of the place.</td>
184-
</tr>
185-
<tr>
186-
<td>place_facebook_id</td>
187-
<td>string</td>
188-
<td>The Facebook ID of the place.</td>
189-
</tr>
190-
<tr>
191-
<td>place_categories</td>
192-
<td>array <string></td>
193-
<td>List of the [categories of the place](https://www.radar.com/documentation/places/categories). </td>
194-
</tr>
195-
<tr>
196-
<td>place_chain_name</td>
197-
<td>string</td>
198-
<td>The name of the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
199-
</tr>
200-
<tr>
201-
<td>place_chain_slug</td>
202-
<td>string</td>
203-
<td>A human-readable unique ID for the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
204-
</tr>
205-
<tr>
206-
<td>confidence</td>
207-
<td>string</td>
208-
<td>The confidence level of the event, one of low, medium, or high.</td>
209-
</tr>
210-
</table>
211-
212-
213-
### Place Exited
214-
215-
<table>
216-
<tr>
217-
<td>Property Name</td>
218-
<td>Type</td>
219-
<td>Description</td>
220-
</tr>
221-
<tr>
222-
<td>latitude</td>
223-
<td>float</td>
224-
<td>The latitude of the user at the time of the event.</td>
225-
</tr>
226-
<tr>
227-
<td>longitude</td>
228-
<td>float</td>
229-
<td>The longitude of the user at the time of the event.</td>
230-
</tr>
231-
<tr>
232-
<td>accuracy</td>
233-
<td>float</td>
234-
<td>The accuracy of the user's location at the time of the event in meters.</td>
235-
</tr>
236-
<tr>
237-
<td>placeId</td>
238-
<td>string</td>
239-
<td>The ID of the place, provided by Radar.</td>
240-
</tr>
241-
<tr>
242-
<td>place_name</td>
243-
<td>string</td>
244-
<td>The name of the place.</td>
245-
</tr>
246-
<tr>
247-
<td>place_facebook_id</td>
248-
<td>string</td>
249-
<td>The Facebook ID of the place.</td>
250-
</tr>
251-
<tr>
252-
<td>place_categories</td>
253-
<td>array <string></td>
254-
<td>List of the [categories of the place](https://www.radar.com/documentation/places/categories).</td>
255-
</tr>
256-
<tr>
257-
<td>place_chain_name</td>
258-
<td>string</td>
259-
<td>The name of the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
260-
</tr>
261-
<tr>
262-
<td>place_chain_slug</td>
263-
<td>string</td>
264-
<td>A human-readable unique ID for the [chain of the place](https://www.radar.com/documentation/places/chains).</td>
265-
</tr>
266-
<tr>
267-
<td>confidence</td>
268-
<td>string</td>
269-
<td>The confidence level of the event, one of low, medium, or high.</td>
270-
</tr>
271-
<tr>
272-
<td>duration</td>
273-
<td>float</td>
274-
<td>The duration between Place Entered and Place Exited events, in minutes.</td>
275-
</tr>
276-
</table>
277-
29+
<!-- TODO: Update the Region Entered/Exited with new links, when availible -->
30+
31+
- [Geofence Entered](https://radar.com/documentation/integrations/segment#geofence-entered)
32+
- [Geofence Exited](https://radar.com/documentation/integrations/segment#geofence-exited)
33+
- [Place Entered](https://radar.com/documentation/integrations/segment#place-entered)
34+
- [Place Exited](https://radar.com/documentation/integrations/segment#place-exited)
35+
- [Region Entered](https://radar.com/documentation/integrations/segment#country-entered)
36+
- [Region Exited](https://radar.com/documentation/integrations/segment#country-exited)
37+
- [Trip Started](https://radar.com/documentation/integrations/segment#trip-started)
38+
- [Trip Updated](https://radar.com/documentation/integrations/segment#trip-updated)
39+
- [Trip Approaching Destination](https://radar.com/documentation/integrations/segment#trip-approaching-destination)
40+
- [Trip Arrived Destination](https://radar.com/documentation/integrations/segment#trip-arrived-destination)
41+
- [Trip Stopped](https://radar.com/documentation/integrations/segment#trip-stopped)
42+
43+
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).
27844

27945
## Radar User Traits
28046

0 commit comments

Comments
 (0)