GeoNest fires email, SMS, and push campaigns the instant a phone enters, dwells in, or leaves a boundary you draw — using the phone's own native geofencing, not a battery-draining background app.
No SDK to ship — fences update from your dashboard, no app release needed.
Precision & control
iOS and Android only wake a device for circular regions. GeoNest draws the real footprint as a polygon and auto-computes a bounding wake-up circle around it — the circle wakes the app cheaply, the polygon then confirms the device is actually inside, not just near.
Fences are configured from the dashboard, not compiled into your app. Redraw a shape, adjust the schedule, or launch a new fence entirely — none of it needs an app release.
Cooldown, active hours, and the date window are enforced on the backend for every single event, not just checked once on the device — so a stale rule on a phone can't fire a stale campaign.
From the dashboard
No release cycle, no engineering ticket for the next campaign — this is what a marketer actually does.
iOS and Android only wake a device for circular regions — and your storefront usually isn't one. Draw a polygon that traces the real footprint, and GeoNest automatically computes a bounding circle around it: that circle wakes the app cheaply at the OS level, then the precise polygon confirms the device is actually inside, not just near.
Pick enter, dwell, or exit, add a dwell threshold and cooldown, and set the dates and hours the fence should be live. Cooldown is enforced server-side per device, so a repeat trigger inside the cooldown window simply doesn't send — dwell and cooldown are tracked separately on purpose: how long someone has to stay, and how long before they can trigger it again, are two different questions.
The fence goes live immediately. No app release — devices pick it up on their next check-in with GET /geofences, and the campaign fires through whichever channels you've turned on, reusing your existing email and SMS infrastructure plus Firebase Cloud Messaging for push — with optional delayed follow-ups after the first message.
GET /geofences
By the numbers
The event lifecycle
Every fence you draw watches for exactly these three events — nothing else needs polling, and nothing else drains a battery.
The OS wakes the app the moment a device crosses into the fence. Good for instant "welcome" offers and check-in style triggers.
Fires once your app reports a device has stayed inside the fence past the dwell threshold you set — so a car passing by on the highway never counts as a visit.
Catches the moment someone walks out — the right trigger for "come back" nudges or post-visit feedback requests.
Use cases
Entry and exit detection
Fire an email, SMS, or push campaign the instant a device enters or exits your fence — both events are reported by the phone's own native geofencing and re-validated on the backend before anything dispatches, so you know exactly when they crossed the line.
Place visit detection
Set a minimum dwell time on any fence you draw — your own storefront, a competitor's, or any location you can put a boundary around — and only a genuine stop counts as a visit, not someone stuck at a red light outside.
Multi-channel dispatch
The same enter, dwell, or exit event dispatches through your existing email and SMS infrastructure, plus Firebase Cloud Messaging for push and WhatsApp — one trigger, no separate channel vendor to wire up per campaign.
On-premise detection
Circular regions are all iOS and Android will wake a device for — a wide circle around an irregular building can catch someone on the sidewalk outside. Draw the real footprint as a polygon instead, and GeoNest auto-computes a bounding wake-up circle around it: cheap to wake on, precise to confirm they're actually inside.
Under the hood
GeoNest is a REST API, not an SDK. Your app registers the device, pulls the active fences, and reports the events the phone's own location system already detects.
/register
/geofences
Register the device once, then pull every active geofence and campaign rule — circle or polygon, schedule, dwell, cooldown — straight from the dashboard. No fence is ever hardcoded into an app build.
GeofencingClient · CLLocationManager
Enter, dwell, and exit are detected by Android's and iOS's own built-in geofencing — not a custom background service — so there's no extra battery drain.
/geofence/event
The app reports the event the instant the OS fires it, and the backend re-validates it before dispatching to any channel.
// backend processing on event received
Built for your industry
Enter, dwell, and exit mean something different depending on what's behind your door. Here's how that plays out by industry.
Trigger a welcome offer on entry, and a "come back" nudge if a browser leaves without buying.
Fire a lunch-rush offer the moment someone dwells near the counter, or a loyalty push as they're walking out.
Send a "your prescription is ready" text when a dwell in the waiting area completes, or a refill reminder on exit.
Recognize a check-in streak on entry, and fire a win-back offer the moment a member's visit pattern shows they've stopped coming.
Draw the fence rule once, and every location in the network runs the identical enter/dwell/exit logic — scoped to its own app.
Follow up automatically after a branch visit dwell, or route someone to a nearby ATM the moment they exit a closed location.
Detect a dwell at an open house or listing and follow up with the listing details before the visitor is back in their car.
Trigger a service reminder for anyone dwelling on the lot, or a test-drive follow-up the moment they exit.
Beyond the trigger
Every enter, dwell, and exit is logged against the campaign it triggered — so "we set up geofencing" turns into "this fence drove real dispatches this week, mostly via SMS."
No separate analytics tool to wire up — it's the same event log that decided whether to fire the campaign in the first place. Numbers below are an illustrative example, not a specific customer's data.
Why not just build it
Geofencing looks simple until you hit the details — bounding-circle math, cooldown logic, per-channel wiring. Here's what that comparison actually looks like.
Platform & security
GeoNest sits alongside SalesNest, LeadHub, and the rest of the LeadNest.ai platform — each app in your organization gets independently scoped geofences and campaigns, authenticated with its own API key.
The short version
Every fence runs on your phone's own GPS-based geofencing — Android's GeofencingClient, iOS's CLLocationManager — the same location stack Maps apps use, not a third-party SDK layered on top.
Register the device, fetch the active geofences, report the event — that's the entire integration surface. No SDK to bundle, no separate vendor to onboard.
Fences and campaigns stay isolated per app, and cooldown, active hours, and the date window are re-validated on the backend for every single event — not just checked once on the device.
Dispatches through your existing email and SMS infrastructure, plus Firebase Cloud Messaging for push — no new per-channel vendor contract to negotiate.
Questions
No. GeoNest hands fences to the phone's own geofencing APIs — GeofencingClient on Android, CLCircularRegion on iOS — which are built to wake the app efficiently on real motion. There's no continuous polling loop running in the background.
GeofencingClient
CLCircularRegion
No. Fences are fetched from GET /geofences each time your app checks in, so anything you change on the dashboard reaches devices without an app-store release.
Draw it as a polygon. GeoNest automatically computes a bounding circle around it for the OS-level wake-up, then checks the device against the precise polygon once it wakes — so the shape you drew is the shape that counts.
Yes — chain an immediate message with one or more delayed follow-ups on the same trigger (for example, an SMS right away, then a follow-up email 30 minutes later). Each send is logged separately against the event that caused it.
True OS-level geofencing needs a native app — that's an OS capability, not something a browser can do. A browser-based fallback using the Geolocation API is on our roadmap for web-only visitors; it isn't shipped yet.
No — GeoNest reuses the email and SMS infrastructure your app already has, plus Firebase Cloud Messaging for push. One fence, one rule, and the channel it dispatches through is a configuration choice, not a separate integration.
Real fence performance
See exactly which fence, which event, and which channel turned a walk-by into a customer — then draw the next one.
Enter details to create your account
Or
Already Registered? Sign In