Olo
Radar can create and manage trips for customer arrival tracking when orders are placed or cancelled in Olo. Additionally, with Order firing enabled in Olo, Radar can power when an order should be manually fired to Olo based on how far a customer is from a restaurant (e.g. 5 minutes away).
Configuration#
Configure an Olo webhook to deliver to https://api.radar.io/webhooks/olo for the relevant order events via the Development Tools section of the Olo Dashboard (requires two-factor authentication and at least Brand Manager permission). When new order events are triggered, Olo will in turn call the Radar webhook.
On the Radar Integrations page under Olo, set Enabled to Yes and paste in your brand ID. Brand IDs required for the integration are provided by Olo. Enter a destination geofence tag (e.g., restaurant), and optionally map fields from the Olo webhook body to Radar trip metadata. Select the applicable Olo Handoff modes that should trigger trip create and cancel events.
Finally, on the Radar Geofences page, import geofences for your restaurants. For destination geofence tag in the Olo configuration, use the tag used in the restaurant geofence configuration.
Based on your settings, Radar will automatically create trips when new orders are placed, as well as complete or cancel trips when orders are completed or cancelled in Olo. You will need to call Radar.startTrip() with just the Olo order ID as the trip options external Id and Radar.startTracking() and Radar.stopTracking() to start and stop location tracking in your app when a trip is in progress.
Assuming locations permissions have been granted and location tracking has been started in your app, Radar will generate location-based user.updated_trip, user.approaching_trip_destination, and user.arrived_at_trip_destination events and calculate live ETAs to the restaurant for each order. Learn more about Trip Tracking.
Order Firing#
In order for Radar to automatically fire your orders based on location proximity, you will need to submit your baskets to Olo as ismanualfire and will also need to set a scheduledArrivalAt datetime to the Radar trip as a fallback in the event location is disabled or the device is experiencing connectivity issues. This can be done using Radar.updateTrip() in the app or Trips API server-side.
In addition to the above Olo and Radar configuration, you will need to generate API credentials for the Radar platform in the Olo development portal. Reach out to your Olo Support Agent to have the keys created on your behalf. On the Radar Integrations page under Olo, you will will need to set Order firing enabled to Yes, paste the Olo Radar Client Id and Secret Key, and Save your integration settings.
Finally, in the Radar Trips Settings, set the Approaching threshold (minutes) value to the # of minutes away from arriving that the order should automatically be fired to Olo. Now when an active trip generates a user.approaching_trip_destination event, Radar will fire the order. In the event the scheduledArrivalAt set on the trip occurs first, this datetime will fire the order instead.
Expo Notifications#
Radar is a Customer Arrival Olo partner and can automatically provide Approaching and Arrival status updates to Olo Expo based on Radar trip tracking events. This keeps in-store teams up-to-date with real-time status updates on tracked mobile orders. Additionally, if your team utilizes the Picked Up button in Olo Expo, this will automatically complete the Radar trip and capture completion time for trip duration and wait time analytics.
To enable this integration, visit the Radar Integrations page. Under Olo, you will need to set Expo updates enabled to Yes, and Save your integration settings.