Locations
Named places with a circular geofence around each, managed on a map.
GeoPulse lets your team define geographic areas, detect when a device enters or leaves them, and trigger a webhook or an in-app experience, without building the pipeline yourself.
Name the place that matters: a store, a depot, a campus. Pick it on the map.
The geofence is the circle around the place. Crossing it, in or out, is what GeoPulse detects.
On enter or exit, send a signed webhook to your backend, or show the user a banner, card or message.
Named places with a circular geofence around each, managed on a map.
A live, searchable record of every enter and exit with its device and location.
When an event matches, deliver it to a webhook.
Signed HTTP calls to your own backend, verifiable on arrival.
Decide when a matching event should show something to the user.
The banners, cards and messages a campaign can show. You edit content, not code.
Events appear in the portal with the device and location they belong to. Operations shows whether each one was processed, and why one failed if it did.
Read the portal tourEvents
Enter and exit activity, newest first.
| Event | Location | Device | When |
|---|---|---|---|
| ENTER | Store #12 | a3f9…c21 | 2 min ago |
| EXIT | Store #12 | a3f9…c21 | 41 min ago |
| ENTER | Warehouse | 7be0…9d4 | 1 h ago |
Sample data for illustration.
The SDK detects geofence enter and exit on the device, queues events while offline, and sends them to your GeoPulse project. Keys live on the portal's SDK page.
Read the setup guidenpm install @damn-coding/geopulse-react-native
import { GeoPulse } from "@damn-coding/geopulse-react-native";
await GeoPulse.initialize({
apiKey: "gp_test_xxx", // from the portal's SDK page
applicationId: "app_xxx", // from the same page
});
await GeoPulse.start();A circular boundary around a location. GeoPulse records an event when a device crosses it: enter when it goes in, exit when it comes out.
Setting up locations, rules, webhooks, campaigns and experiences happens in the portal. Connecting real devices needs a developer to add the React Native SDK to your app.
The event is stored and shown on the Events page. Rules can then send it to a signed webhook, and campaigns can show an experience in your app. The Operations page records whether each step worked.
The SDK queues events on the device and retries them when the connection returns.
The SDK currently requests foreground location permission only.
The Setup Guide at /docs walks through the portal and the SDK, with a reference for every page.