Geofencing software for Tanzanian fleets
Geofencing draws a virtual boundary — a yard, a customer site, a route corridor or a no-go zone — around a place on the map, then watches for a tracked vehicle to cross it. Trakora's fleet engine checks every GPS fix against your zones and raises a geofence_exit alert to SMS, WhatsApp and push.
Fleet geofencing at a glance
- Rule that powers it
- geofence_exit — a shipped fleet alert
- Zones you can draw
- Yards, customer sites, corridors, no-go areas
- Trigger direction
- Exit by default; entry configurable per zone
- Alert channels
- SMS · WhatsApp · push
- GPS reporting interval
- —1 depends on device plan
- Zones per account
- —1
- Minimum zone radius
- —1
- Shipped screens
- /geofences · /map · /replay
- Related rules
- tracker_geofence_breach · safe_zone_exit
- Who it's for
- Transporters, distributors, haulage and delivery fleets
What a geofence-exit alert actually is
A geofence is not a line on a screen — it is a rule evaluated against every position report. Here is exactly what fires it, what the controller sees, and what they do next.
A vehicle crossed the boundary of a zone it was inside
A new GPS fix places the vehicle outside a zone whose previous fix was inside it. The crossing — not the position — is the event, so a truck parked on the edge does not chatter.
A geofence-exit alert naming the vehicle, the zone it left, the time in EAT and the last known point — on the live map, and pushed to SMS, WhatsApp and push at once.
Call the driver, open /replay to see the track that led out of the zone, and keep the alert in the log as the record of when the vehicle left.
The same rule reads either direction. Set a zone to alert on exit to know when a truck leaves your yard; set it to alert on entry to know the moment it reaches a customer site or a checkpoint. Both are the one geofence_exit rule with its direction configured per zone.
The zones a fleet actually draws
Four shapes cover most of the work. Each is drawn once on the map and reused across every vehicle in the group.
The yard
A boundary around your depot or parking yard. Exit tells you a truck has rolled out — the honest start-of-trip timestamp, whether or not the driver told you.
/ geofence_exit · exitThe customer site
A zone around a delivery point or loading bay. Entry stamps arrival and exit stamps departure, so dwell time at each stop is measured, not estimated.
/ geofence_exit · entryThe route corridor
A long zone following the road a trip should take. Leaving it flags a detour early. For sealed transit cargo the deeper version lives on the container corridors page.
/ route-corridorsThe no-go area
A zone a vehicle should never enter — a rival's yard, a restricted district, an out-of-hours quarter. Entry is the alert you want, and it is the same rule inverted.
/ geofence_exit · entrySetting up a geofence, end to end
From drawing the zone to reading the report — the four steps a controller runs once per zone.
-
Draw the zone on the map
Open /geofences and drop a zone over the yard, site, corridor or district. Give it a name your controllers will recognise on an alert at 2 a.m.
-
Choose the vehicles and the direction
Attach the zone to a vehicle group and set whether it alerts on exit, entry, or both. One zone can watch a whole group at once.
-
Let the engine evaluate every fix
From then on each GPS report is checked against the zone. A crossing raises the geofence_exit alert to SMS, WhatsApp and push, and drops it on the live map.
-
Replay and report
Open /replay to watch the track in and out of the zone, and pull the crossings into a report for the customer, the insurer or the disciplinary file.
Geofencing across the whole platform
The same zone-crossing engine powers different alerts in different modules. This is the mechanism page; each link below is the version framed for that operator.
What geofencing cannot do
What to expect
- A geofence is only as timely as the next GPS fix. In a coverage dead zone, fixes buffer and backfill when signal returns, so a crossing can be reported late with its original timestamp — not in real time.
- Zone accuracy is bounded by GPS accuracy; a zone smaller than the device's positional error will produce false crossings. Draw zones with a sensible margin rather than tight to a fence line.
- Geofencing tells you a vehicle moved across a line. It does not stop the vehicle — engine cut is a separate anti-theft capability, not part of this rule.
- A geofence-exit alert is a notification, not a guarantee of action. It reaches SMS, WhatsApp and push; someone still has to read it and respond.
Values marked — are figures to be confirmed: the GPS reporting interval, the number of zones per account, and the minimum zone radius depend on the device plan and are quoted per deployment, not published on this page. No default threshold value ships in the module manifest, so none is stated here as fact.
Frequently asked questions
What is geofencing in fleet management?
It is a virtual boundary drawn around a place on the map. When a tracked vehicle crosses it, the fleet engine raises a geofence_exit alert to SMS, WhatsApp and push.
Can I be alerted when a truck enters a place, not just leaves?
Yes. The same rule reads both directions — set a zone to alert on entry for arrivals and checkpoints, or on exit for the yard. Direction is configured per zone.
How many geofences can I create?
The number of zones per account is quoted per deployment rather than published here. Tell us how many yards, sites and corridors you run and we will scope it.
Does a geofence stop the vehicle?
No. Geofencing is a monitoring rule — it tells you a vehicle crossed a boundary. Cutting the engine is a separate anti-theft immobiliser capability on the vehicle-tracking side.
What happens to a crossing when the vehicle is out of coverage?
The fixes buffer on the device and backfill when signal returns. The crossing is then reported with its original EAT timestamp, so the record is right even if the alert arrives late.
More in fleet management
Draw your first zone
Tell us your yards, customer sites and corridors and we will scope a fleet geofencing deployment in TZS, with a VAT invoice and Swahili support.