How to Create a Geofence in TagLogger

What geofences do in TagLogger

A geofence is a virtual boundary around a physical location. In TagLogger, geofences help teams know when tracked assets enter or leave important areas such as yards, job sites, storage zones, customer locations, or transfer points.

That turns location history into a more operational workflow: teams do not just see where an asset was last seen, they also get alerts when movement crosses a boundary that matters.

When teams usually create geofences

• Yards, depots, and fenced storage areas
• Active job sites and temporary project locations
• Customer sites where arrivals and departures matter
• High-risk zones where unauthorized movement should trigger follow-up

How to create a geofence in TagLogger

1. Open the map and switch to the Geofences section.
2. Start a new geofence and click the map to place the center point.
3. Enter a clear name so the alert is easy to recognize later.
4. Set the radius in meters based on the real operating area.
5. Select the tags the geofence should monitor.
6. Choose whether alerts should fire on entry, exit, or both.
7. Enable email alerts, device push alerts, or both depending on who should respond.
8. Save the geofence and review the first alerts to confirm the boundary is sized well for the workflow.

Choose alert behavior that matches the workflow

Entry alerts are useful when teams need confirmation that an asset arrived at a site, yard, or customer location. Exit alerts are useful when teams need to know that something left a controlled area or moved outside an expected zone.

Some teams enable both, but many get better signal quality by starting with the event that matters most operationally. That keeps alert volume easier to manage and makes follow-up clearer.

Choose a practical geofence size

A geofence should match the real operating area, not just the exact resting point of the tag. In practice, very small boundaries can create confusing edge events because AirTag-based location updates are inferred from nearby Apple devices in the Find My network, not from a dedicated GPS unit attached to the asset itself.

That means a tag that has not materially moved can sometimes appear just outside a tight boundary when the latest nearby-device relay came from farther away, then appear back inside on a later update. The practical takeaway is simple: start with a boundary that comfortably covers the real yard, site, or operating zone instead of drawing it too tightly around the asset footprint.

For most teams, a slightly larger geofence produces more useful alerts than a very precise one. If entry and exit events feel too sensitive around the perimeter, widening the radius a bit is often the fastest way to make alerts cleaner and more operationally reliable.

What to review after launch

• Whether the right tags were assigned to the geofence
• Whether entry, exit, or both event types are actually needed
• Whether the current radius matches how the location is used in practice
• Whether alerts are going to the people who can act on them quickly