Turn a stream of device pings into a trip — planned stops, a running ETA, and delay detection against your own schedule.
SIX TRIP EVENTS FEED STRAIGHT INTO ACTION ENGINE
From device pings to a trip you can monitor
Define a trip as an ordered list of stops against your own schedule. Fencemaker matches live geofence activity against that plan automatically — no separate tracking layer, no manual status updates.
Create a trip via API with ordered stops — pickup, delivery, service, or waypoint
Automatic arrival and departure detection at each stop, with dwell time computed from existing geofence events
Delay detection — flagged the moment an active trip runs behind its planned ETA
Deviation detection — flagged the moment a device reaches a stop out of sequence
Running ETA to the next stop, powered by Fencemaker's routing engine
Six trip events feed straight into Action Engine: trip started, stop arrived, stop departed, delayed, deviated, completed
Read-only trip list and detail view in the ops portal, alongside Devices and Territories
Typical uses
Delivery fleets tracking on-time performance stop by stopDispatch teams that want an automatic alert the moment a driver goes off-routeService businesses logging arrival and dwell time per jobAny workflow already built on Action Engine that wants trip milestones as new triggers
Trips is API-only today — trips and stops are created and managed through the API; the ops portal view is read-only for visibility. Trips is available on every plan, including the free tier; each stop you create consumes one territory against your plan's territory cap, the same way a manually-created geofence does, so trip volume scales with that limit (10 on free, 50 on starter, 500 on growth, 2,000 on scale).