Draw the enter/dwell/exit logic once, and every location in your network runs it the same way — scoped to its own app, with no re-integration per franchisee.
Use cases
Enter, dwell, and exit mean something specific here — this is what that looks like in practice.
Scoping
Every location is its own app with its own app_uuid — fences, devices, and campaigns never bleed across locations, even though the rule logic is identical.
Rollout
A brand-wide campaign rule — say, a dwell-based welcome offer — is configured once and rolled out to every location without engineering involvement per site.
Reporting
Each location's events and dispatches are tracked independently, so a franchisor can build a brand-wide view from the event log while franchisees see only their own store.
Why teams choose GeoNest
Circles and polygons handed to the phone's own geofencing APIs — no continuous background polling.
Register, fetch geofences, report an event — that's the entire integration surface.
Every fence, device, and campaign is scoped to a single app — nothing crosses over.
Dispatches through your existing email and SMS infrastructure, plus Firebase Cloud Messaging for push — nothing new to wire up.
More industries
Not quite your world? See how the same enter/dwell/exit fence plays out for other industries.
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.
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.
Questions
Every fence, device, and campaign is scoped to a single app's app_uuid. Locations are modeled as separate apps under one organization, so nothing is visible across locations by default.
No — new locations are onboarded as new apps under your existing organization, reusing the same three-endpoint integration your team already built.
That depends on how you want to structure access — the underlying scoping supports both centralized rules and per-location customization; which one you use is a business decision, not a technical limitation.
Aggregating per-location event data into a brand-wide view is something you'd build using the event log GeoNest produces per app — it isn't a built-in cross-app dashboard today.
Multi-location & Franchise
Tell us how many locations you're starting with and we'll help you map the rollout.
Enter details to create your account
Or
Already Registered? Sign In