Skip to content

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.

Geofence · Store 12ENTEREXITRuleNotify backendWebhookYour server

From a place on a map to an action. Three moves.

  1. Define a location

    Name the place that matters: a store, a depot, a campus. Pick it on the map.

  2. Draw its geofence

    The geofence is the circle around the place. Crossing it, in or out, is what GeoPulse detects.

  3. Connect events to actions

    On enter or exit, send a signed webhook to your backend, or show the user a banner, card or message.

Everything between the crossing and the consequence.

Locations

Named places with a circular geofence around each, managed on a map.

Events

A live, searchable record of every enter and exit with its device and location.

Rules

When an event matches, deliver it to a webhook.

Webhooks

Signed HTTP calls to your own backend, verifiable on arrival.

Campaigns

Decide when a matching event should show something to the user.

Experiences

The banners, cards and messages a campaign can show. You edit content, not code.

See every crossing as it happens.

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 tour

Events

Enter and exit activity, newest first.

EventLocationWhen
ENTERStore #122 min ago
EXITStore #1241 min ago
ENTERWarehouse1 h ago

Sample data for illustration.

Add it to a React Native app.

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 guide
npm 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();

From a new project to your first event.

  1. Step 1:Create your organization and a project.
  2. Step 2:Add a location and set its geofence.
  3. Step 3:Create an application and copy its SDK key.
  4. Step 4:Install the SDK in your React Native app and initialize it.
  5. Step 5:Walk into the geofence. The event shows up on the Events page.
  6. Step 6:Optionally add a rule, webhook or campaign to act on it.

Questions, answered.

What is a geofence?

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.

Do I need to write code?

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.

What happens when a device enters a geofence?

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.

What if the phone is offline?

The SDK queues events on the device and retries them when the connection returns.

Does it track location in the background?

The SDK currently requests foreground location permission only.

Where do I find the setup steps?

The Setup Guide at /docs walks through the portal and the SDK, with a reference for every page.

Set up your first geofence today.