iOS SDK 15.6.3,
Android SDK 15.4.1,
Hello Screen Dynamic States,
Bluedot Cordova plugin 4.0.1,
Bluedot Xamarin Android Wrapper 15.4.1,
Bluedot Xamarin iOS Wrapper 15.6.0,
Bluedot React Native wrapper 2.1.2,
Wave API.
Details here.
A Destination is a physical location your customers arrive at to collect their mobile order – this is usually your store or restaurant. A Destination is actually just a Zone, but it must meet specific eligibility criteria* & has a DestinationId
.
There are 3 simple steps:
DestinationId
*A Zone is only eligible for as a Destination if has a single geofence and no Geolines or beacons. If you try adding a DestinationId
to an ineligible Zone you see an error in Canvas.
Click on Add new Zone and create a geofence – you can use a circular geofence, a polygon or a rectangle. This should cover your restaurant or store.
You can also update the name of the Zone and geofence – both of these details will be included in Tempo Webhook updates.
Select Zones Settings, click Destination ID and add the Destination ID.
Close Zone Settings and click the Create/Update button. The Zone is ready and the isochrones for it will be generated in the Bluedot backend. It takes from 30 seconds to 1 minute for the isochrones to be generated.
If you’d like to Create a Destination using Config API, you’ll use the following /Endpoints;
Endpoint | Description |
Add DestintaionId to a new Zone | When creating a Zone you can pass the Destination ID within the tempo property.
Endpoint: Example of adding a Destination Id: "tempo": { "destinationId": "<destination_id_goes_here>" } |