Someone in the area is the least expensive visit you will win all week, provided the offer reaches them while walking in is still realistic.
Geofencing software for mobile apps: reach customers where they already are
Woosmap geofencing is a software development kit your team integrates into your own app, not a standalone dashboard, and it turns an entry, an exit or a stop into an event your systems can use.
How a location event becomes a notification your customer welcomes
Choose the locations you want to watch.
Branches, collection points, lockers, service areas: you declare them from your own point-of-interest data.
The SDK monitors them from your app.
With the location permission granted by the user, monitoring runs on the device rather than on a server.
The moment is captured.
An entry, an exit or a stop becomes an event, together with the location that triggered it.
Your messaging platform takes over.
The event reaches the platform that already holds your segmentation and consent rules, and the notification is composed there.
A shopper is three minutes from the branch they ordered from. A driver has just reached the collection point. Most mobile apps recognise neither moment, so the notification goes out the following morning, long after it could have changed anything.
Four moments where the location decides the outcome
Monitor more locations than iOS and Android hold at once
Operating systems limit how many geofences an app can monitor simultaneously. The SDK refreshes the monitored geofences as the user moves, allowing your app to cover a larger network of locations without building and maintaining that refresh logic from scratch.
- Distance-based.
The event fires when the user comes within a defined radius of a location.
- Time-based.
The event fires on estimated time of arrival, using isochrone polygons rather than a straight-line radius, which is closer to what a customer in traffic experiences.
- Recurring.
The event fires on the locations a user returns to, such as home and work.
Prioritise accuracy or battery life, per use case
Continuous location is the objection every mobile team raises first, and it deserves a straight answer. The SDK ships three predefined tracking profiles, Passive, Visits and Live, alongside a Custom profile you configure yourself.
Each profile determines how often a position is collected and how precise it must be, so the balance between accuracy, collection frequency and battery use is something you optimise per use case rather than accept as a fixed cost.
Recognise where customers stop, not merely where they travel
The SDK detects the locations where a user actually stops, and groups position history on the device to identify zones of interest they return to. Approximate home and work areas emerge from that history after several days of collected data, computed on the device.
It can also return the points of interest around the user's current position, sorted by proximity, which is what you need to attribute a visit to a specific branch.
Keep location history in your app
Positions and visits collected by the SDK are stored locally in your mobile app. Woosmap does not collect or process that history on its servers. The SDK also calls Woosmap APIs to retrieve the locations to monitor.
Connect location events to your customer engagement platform
Use geofence and point-of-interest events produced on the device in your notification scenarios through the documented connectors.
Integrate geofencing with your mobile stack
Choose the SDK or plugin that matches your application. The setup guides cover permissions, API keys and current platform requirements.
- iOS.
- Android.
- Cross-platform.
What mobile teams ask before they commit
Yes. With the location permission granted by the user, the SDK keeps monitoring position and geofence crossings while the app is in the background or is not currently running.
The Android SDK can monitor beacon proximity through the beaconTracking profile, retrieving beacon identifiers from the Indoor Search API. It requires the Bluetooth permissions declared in your app and a private Woosmap API key. Beacons complement GPS indoors rather than replace it.
Start with the two native guides: iOS SDK setup and Android SDK setup
Budget for the API services your integration uses. The pricing page lists Search (Geofencing context), billed per request, and Distance Matrix with Geofencing and Distance Matrix with Traffic with Geofencing, billed per element. Estimate the corresponding usage volumes to assess the applicable pricing.
Work out whether this belongs in your app
Two questions settle it. Can your mobile team integrate a location SDK this quarter, and does your messaging platform already send the notifications you want to trigger? The developer documentation answers the first in an afternoon. For the second, bring your point-of-interest data and your messaging stack, and we will work through it with you.