Skip to content

Configure

The Configure group holds what the project sends to its devices and what the server applies to their locations. Owners and admins change it; members see it read-only.

The project’s fences, on a map beside a list. Crossings become geofence.enter, geofence.exit and geofence.dwell events, sent to your webhooks and listed in Events. Devices pick up a new or changed fence at their next sync.

  • The map tools (owners and admins): Select, Draw circle (press at the centre and drag to the radius) and Draw polygon (click to add three or more corners, then click the first corner, double-click or press Enter). Fit all fences frames them all. Esc cancels; Ctrl/⌘+Z undoes. An outline that crosses itself can’t be saved.
  • The list shows each fence’s name, shape (Circle · 200 m, Polygon · 5 corners), and Entry / Exit, or No events when both are off. New fence starts a circle; Search fences looks at names.
  • The editor has Name, Radius (metres) for a circle, Notify on entry and Notify on exit, and an optional Phone notification the SDK shows at the crossing, even offline (a title and body for each side, Importance and an optional Deep link). Create fence or Save changes; Delete… asks first. Past events are kept.
  • The editor also sets the fence’s two policies:
    • When contact is lost: Keep the visit open (no exit), the default, or Send an exit. With Send an exit, a device that the server marks unreachable while inside gets a geofence.exit with evidence: unreachable. Its occurred_at is the device.unreachable event’s (for a silent device, the deadline that passed) and its occurred_after is the device’s last location inside, so the exit happened between the two. The device’s next location inside starts a new visit. With the default, the visit stays open and the next location decides. This is the API’s on_unreachable (none or exit).
    • Count drive-throughs (off by default): an entry and an exit, at estimated times, when a device crosses the fence between two locations with none inside. This is the API’s pass_through (off or on).
  • The console draws circles and single-ring polygons. A polygon with holes or a multipolygon made through the API keeps its shape here; edit the shape through the Geofences API.

Without a basemap. When the deployment has no Mapbox token, or the map fails to load, Geofences draws on a plain grid without a basemap, with the same tools, handles and editor: drag to pan, scroll or use + / − to zoom, and the scale reads Squares of 100 m. The finder then goes to a typed latitude and longitude (for example 12.9716, 77.5946); searching places by name needs the map.

Plan limits (the number of fences, corners and size) are checked when you save. A fence can’t cross the 180° meridian: draw it as two.

The project’s remote configuration: the settings devices apply, and the server-side settings for gating, trips and presence. The header shows the live revision (Live · v1) and View JSON, the live document as the API returns it.

One card per section, each with its own Save:

SectionSettings
TrackingMinimum time between locations, Minimum distance between locations, Accuracy (High / Balanced / Low), When the device stops (Pause / Pause with check-ins / Keep tracking), Stationary radius, Detect activity, Heartbeat while still, Locations kept on the device
UploadsUpload interval, Locations per upload, Upload early at, Upload on Wi-Fi only, Upload while charging only
FiltersLow accuracy and its Accuracy limit, Mock location, Implausible speed and its Speed limit. Applied on the server to arriving locations, which are gated, not dropped. Devices never see these.
TripsStop radius, Stop duration, Gap interval, Minimum trip distance, Minimum trip duration, Stall after no contact, End after no contact, Trip accuracy limit. Applied on the server when it cuts trips; devices never see these. The two no-contact settings are below the table.
PresenceRest limit: how long a device the server treats as resting may send nothing before the server marks it unreachable (3600–604800 s, default 43200 s, 12 h). A moving device is marked unreachable sooner, from its upload interval. Applied on the server; devices never see it. See presence.
PrivacyCoarsen coordinates: rounds latitude and longitude on the device before they are stored, to 6 down to 1 decimals (4 ≈ 11 m, 3 ≈ 110 m), or Off. Irreversible.
DiagnosticsSDK log level (App’s own, Off, Error, Warn, Info, Debug)
Feature flagsNamed switches that SDK features read: up to 64, lower-case letters, digits and _. New flags start on.
Config pollingConfig poll interval: how often idle devices check for a new revision.

The two Trips no-contact settings (the trip lifecycle):

  • Stall after no contact marks a trip in progress stalled when its device has sent nothing for this long: 60–86400 s, empty follows the Gap interval, and 0 turns it off (the trip still stalls when the device is marked unreachable).
  • End after no contact ends a trip in progress or stalled after this long with nothing from the device: 3600–604800 s, default 86400 s. A later location starts a new trip.
  • Each setting shows its SDK default and its allowed range. Reset to default puts one back. A value outside its range blocks saving, so the server never sends a value the SDK would change.

  • Save opens a review of current and new values, warns Uses more battery when a change does, and Save and publish v2 makes the new revision live for every device. Discard drops the card’s unsaved changes.

  • If someone else publishes while you edit, your changes are kept and the page offers Load v2 first.

  • Rollout shows how many devices run the live revision, an older one, failed to apply it, or have not reported, with View outdated devices and View failed devices. Devices that are behind or failed keep running their last good config.

  • Revision history (owners and admins) lists who published each revision. Only the live values are kept: to undo a change, set it back and save.