Geofencing technology draws a virtual boundary around a real place and lets an app respond when a visitor’s phone crosses it. At an attraction, it earns its place only for a narrow set of moments.

Say a visitor who has opted in walks toward the gate of a garden’s meadow trail with the phone in a pocket and the app closed. The app offers the trail’s first story. A geofence can do that without a sign or a scan, and it typically costs the visitor two permissions: location that works in the background, and notifications.

The short version

• Geofencing responds when a phone crosses a boundary, and it needs the visitor’s location permission to run at all.
• The radius floor, more than the platform caps, limits how many zones fit.
• Inside buildings, an NFC tag, a beacon or a QR code usually ties content to the right spot better.
• A good trigger means less searching for the visitor, not more notifications.
• Visitors who decline location must still reach the same content, so geofencing never gates information.

What is geofencing technology, and how does it work?

In practice a geofence is usually a circle: a point on the map plus a radius. Android and Apple both document it that way. The app notices when the phone moves in or out of the circle.

Permission comes first: without it, the other three parts cannot run. Then the boundary, the shape drawn on the map. Next the crossing, the moment the phone’s location falls inside it. Last the message, whatever the venue decided should happen then.

Bluetooth is not part of a geofence. A beacon is a small Bluetooth transmitter that a phone detects when close.

Why platform limits shape the design

When an app uses the phone’s built-in geofencing, Apple’s documentation says no single app may monitor more than 20 conditions at once, and Android’s sets 100 geofences per app per device user. Count your moments first.

The tighter limit is the radius. Android suggests a minimum radius of about 100 meters, to allow for the accuracy of typical Wi-Fi networks. Circles that size overlap when their centers are closer than about 200 meters, so a plaza, a parking lot and a trail start near each other tend to behave as one zone.

Android also recommends a dwell trigger, which fires only after a phone stays in a zone for a set time, to reduce “alert spam”.

Our view: use location to cut searching

Pigeon-Tech’s published view is that proactive guidance should reduce visitor searching, not add notifications, and that essential information should stay available to everyone instead of sitting behind personalization. A location trigger should follow the same logic.

A school group that should hear a trail’s story where it begins gains from this. It loses if only those who said yes to location hear it.

Three questions that pick the trigger

1. Where is the moment?

   On open ground, a geofence can work. Inside a building, a rough circle cannot separate galleries.

2. Who decides?

   A geofence reacts to location and needs permission. An NFC tap or a QR scan is the visitor’s own choice and needs no location permission. The cost falls differently: the venue installs and maintains a tag or sign, while for a geofence the visitor grants permission.

3. What does it save the visitor?

   Feeding times at the entrance fail this test, because a sign or the home screen already shows them. The meadow story passes, though a tag or QR sign at the gate could also do it.

Inside buildings, a beacon can mark a room. NFC tags and QR codes mark a single exhibit or sign. Indoor geofencing is a poor fit; one of these usually serves better. Our indoor navigation guide goes deeper.

An illustration: one zoo, four moments

This is a made-up example, not a customer result. Say a zoo wants to help four moments.

• Today’s feeding times at the front plaza: no trigger. A sign and the app’s home screen already carry them.
• A far trail start, about 400 meters from the plaza: a geofence, with a zone of 100 meters or more, offering the first story to a visitor whose app is closed, if the venue accepts the permission cost; otherwise a tag or QR sign at the gate.
• Inside a reptile house: beacons or NFC tags, since no circle separates close exhibits.
• One habitat sign: an NFC tag or QR code, chosen by the visitor.

The same logic holds on a campus quad; see the campus navigation guide.

Implementation realities

A geofence message that reaches a visitor with the app closed typically needs two permissions: location, and notifications, which the live Pigeon-Tech FAQ also describes as part of the setup. Android’s documentation lists background location permission as required for apps targeting Android 10 or later. On iOS, Apple says “When in Use” location is the preferred choice for privacy and battery life, while “Always” is what lets the system launch the app for region monitoring. For a one-day visit, a visitor may have little reason to grant either. For many attractions, a foreground “what’s nearby” screen, or a tap or scan, is the better first choice. An app-open version of the meadow story needs no special permission but depends on the visitor opening the app near the gate.

• Some visitors will say no, and every one who does must still reach the same content, through a QR code, a tap point or an ordinary menu.
• Upkeep. Someone has to own the content behind every message.

What to decide, measure and stop

Pick the moments that pass the three questions. Measure whether visitors opened the content, not how many messages went out. Stop any message that visitors routinely dismiss, or that only repeats what a sign already says.

Where Pigeon-Tech fits

Pigeon-Tech’s location-based experiences let a venue connect places, zones and touchpoints with content, alerts and recommendations. Depending on the setup, triggers can include GPS, beacons, NFC and geofencing, indoors or out, and alerts can be configured where permissions and notification setup are part of the deployment. Visitor analytics can show how visitors respond, depending on the setup.

Frequently asked questions