Geofencing for business without tracking people: zones that watch ships, roads and rivals
Geofencing for business usually means following phones. A different kind draws zones on a map and alerts you when ships, road closures or new rivals appear inside them.
Part of the guide Location intelligence automation
Geofencing for business means drawing a boundary on a map and acting when something crosses it or appears inside it. In marketing the word usually means following people's phones into a zone to show them an advert. There is a second kind that never touches a person: zones around a port, a depot, a patrol area or a branch that tell you when a ship enters, a road inside them closes, or a new rival opens within them. That second kind is what this article is about, and it is often the more useful one for operations.
It is for operations, security, port, logistics and expansion teams who want to be told when something changes inside an area that matters to them. It explains the two kinds of geofence, how to draw a good zone, which events are worth an alert, a made-up example from a security firm, the common mistakes, and how to build a zone watcher in xMap Flows.
Two kinds of geofence
- Geofences on people. An app or ad network notices that a phone entered a zone and reacts: a coupon, a push message, an advert. It needs the person's device and, in most places, their consent. xMap Flows does not do this and does not track any person or device.
- Geofences on things and places. The zone watches public signals about things: ships broadcasting their position, road closures and roadworks, places opening, closing or changing their rating. Nobody is followed, and the alert goes to your own team.
When people want to know how busy a zone is, an aggregate measure such as footfall (people-hours of presence over small areas, never single people) answers that without a geofence on anyone.
Drawing a zone that works
A zone is only as useful as its edges. Draw it around the area where your work actually changes, not a generous circle around a city.
- Shapes for irregular areas. A berth, a channel, an industrial estate or a patrol sector is best drawn as a polygon on the map.
- Points with a radius for sites. Around each depot, branch or project, a point with a distance (250 m to 25 km) is quicker and fair across sites.
- One zone per audience. If two teams act on different areas, give them separate zones and separate messages.
- A tight edge. A loose boundary catches traffic that was never coming in and fills the inbox.
Events worth an alert
| What enters or changes | Who acts on it | Typical check |
|---|---|---|
| A ship enters a port area or protected water | Port agents, terminals, marine rangers | Every 15 minutes to every hour |
| A road closure or roadworks inside a zone | Dispatch, field crews, security | Every 15 minutes to every hour |
| A new place of your kind opens within the zone | Branch and expansion teams | Daily or weekly |
| A place in the zone closes or its rating falls under a line | Sales, account managers, landlords | Daily or weekly |
Common zone events; set the check to how fast you need to act.
A made-up example: patrol sectors in Johannesburg
Say a security company in Johannesburg runs patrol cars in four sectors it has drawn on the map. Its control room wants to know, every 15 minutes during the night shift, about new road closures or incidents inside any sector, so it can reroute patrols before a car gets stuck. It does not want messages about the rest of the city.
| Night | Incidents in the city | Inside a sector | New since last check | Messages sent |
|---|---|---|---|---|
| Monday | 41 | 6 | 3 | 3 |
| Tuesday | 35 | 2 | 1 | 1 |
| Wednesday | 52 | 9 | 4 | 4 |
Made-up figures for illustration only.
Out of more than a hundred incidents across those nights, the control room received eight messages, each naming the sector, the street and the kind of incident, with a short note on which way to reroute. An incident already reported is not sent again at the next check, so a closure that lasts all night produces one message, not thirty.
Mistakes with business geofences
- Zones drawn too wide. The alerts become noise and get muted. Start tight and widen only if you miss something.
- Reporting what is inside, every time. For moving things, report what entered or left; for places, what is new or changed. Reporting everything inside on every check repeats yesterday's news.
- Forgetting the first check. On the first run there is no memory, so everything inside counts as new. Expect one busy message, then only real changes.
- Expecting full coverage of ships everywhere. Ship positions come from AIS receivers along the coast; busy ports are heard well and some waters barely at all. Test your own area first.
- Mixing it up with tracking people. If a plan needs to know where a person is, it is the wrong tool and the wrong idea.
Building a zone watcher in xMap Flows
In xMap Flows a zone watcher is an AI employee that checks on a timetable or waits for a change, and writes only when something happened inside your zone. The location intelligence automation page shows how it fits with the other jobs.
- Add a Schedule (every 15 minutes, with active hours if only some hours matter).
- Add an Area of interest and draw your zones on its map, as shapes or as points with a distance around each.
- Add the data block for what you watch: Traffic incidents for closures and roadworks, or Ships (AIS) for vessels.
- Add Zone alert set to Entered or crossed it (for ships), or Only new (for incidents), so each event is reported once.
- Optionally add xMap LLM to write a one-line instruction for each event, then send it by Email, Slack or WhatsApp.
What lands with the team is one line per new event: what it is, where inside the zone, when it was seen and a map. For places rather than moving things, the When something changes trigger watches up to five places and starts the flow only when a new place of a kind opens within your distance, a place closes, its rating falls under your line, or a road closes nearby. Templates to start from: Incidents in my patrol zones, every hour, Ships entering my zone and Road closures in my delivery zones, every hour.
Questions
Does xMap Flows track phones that enter a zone?
No. It never tracks people or devices. Its zones watch public signals about things and places: ship positions, road incidents, and places opening, closing or changing.
How many zones can one flow watch?
As many shapes and points as you draw in the Area of interest. Keep separate flows when different teams act on different zones.
Will I get the same alert every check?
No. Zone alert remembers each ship's last position, and Only new remembers each incident, so an event is reported once.
Can I see how busy a zone is?
Yes, as an aggregate. Mobility Footfall gives people-hours of presence around a place, never individual people, in the countries it covers.