A customer who is already in the area is the cheapest visit you will ever win. The app notices, and the offer arrives while walking there is still an option.
Geofencing for mobile apps: act the moment your customer arrives
The Woosmap Geofencing SDK watches the places you care about from inside your own app, and turns an entry, an exit or a stop into an event your systems can use.
From a customer crossing a line to a message worth sending
Pick the places that matter.
Stores, pickup points, lockers, service areas: you declare which locations your app should watch, from your own point-of-interest data.
Let the SDK watch them.
With the location permission granted by the user, monitoring runs from your app rather than from a server.
Catch the moment.
An entry, an exit or a stop becomes an event, with the place that triggered it.
Hand it to the platform that sends.
Your engagement platform receives the event and composes the message under the rules you already maintain.
A shopper is three minutes from the store they ordered from. A driver has just reached the collection point. A standard mobile app knows neither moment, so the message that would have mattered goes out the next morning, when the customer has already moved on.
Four moments where knowing the place changes the outcome
Watch more places than iOS and Android monitor 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 place.
- Time-based.
The event fires on estimated time of arrival, using isochrone polygons instead of a straight-line radius, which is what a customer stuck in traffic actually experiences.
- Recurring.
The event fires on the places a user comes back to, such as home and work.
Set the accuracy you need, and the battery cost you accept
Continuous location is the first objection a mobile team raises, and it is a fair one. The SDK ships three predefined tracking profiles, Passive, Visits and Live, plus a Custom profile you configure yourself.
Each profile sets how often a position is collected and how precise it has to be, so the trade-off between accuracy, collection frequency and battery use is a configuration decision rather than a rewrite. Nothing forces the same profile on your whole user base.
Recognise where a user stops, not only where they pass
The SDK detects the places where the 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, on the device itself.
The SDK can also return the points of interest around the user's current position, sorted by proximity, which is enough to name the store a visit belongs to.
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.
Questions 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.
The two native guides are the place to start: 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.
Decide whether this belongs in your app
Two questions settle it. Can your mobile team integrate a location SDK this quarter, and does your engagement platform already send the messages 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 go through it with you.