GPS Tracking Events, Email Alerts & Webhooks

GPS tracking becomes more useful when you do not have to watch every Object on the map all day. An Event rule lets Jitra evaluate a defined condition, record when that condition occurs, and deliver the result through the channels your Organization has configured.

The important distinction is simple: the Event occurrence is the operational record. In-app alerts, email, and webhook are delivery paths built around that record. A delivery failure does not erase the Event itself.

The Event flow in one view

A typical flow has four stages:

Telemetry reaches Jitra — A compatible GPS device or Jitra Tracker sends the location and available telemetry for an Object.
An active rule evaluates the data — Jitra checks the selected Objects, trigger settings, duration, geofence dependency, sensor condition, schedule, and cooldown that apply to the rule.
Jitra creates an Event occurrence — When the configured condition is met, the occurrence is stored in Event History.
Configured channels process the occurrence — Notify Users, Email Notification, and Webhook Integration run independently according to their configuration and entitlement.

This separation makes the Event useful as a record even when no external message is sent.

What can trigger a GPS tracking Event?

Supported Event rules can represent conditions such as:

an Object entering or leaving a geofence;
an Object remaining stopped or moving for a configured duration;
speed going above or below a defined threshold;
excessive idling or harsh-driving data when the required telemetry is available;
GPS signal being lost or recovered;
a supported sensor condition matching the configured value.

The exact options depend on the Event type and the data received from the selected source. A location-only source cannot produce telemetry that it does not send.

For a practical geofence example, read What Is a GPS Geofence?

Event History and Event Notifications are different

Every detected occurrence is stored in Event History for users who have access to the related Object. Event History is the operational timeline and does not use a read or unread state.

Event Notifications is a personal inbox. It only contains notifications created for an eligible user when Notify Users is enabled and that user's notification preferences allow delivery. These items can be marked read and contribute to the unread badge.

This means an email-only or webhook-only rule can still create an Event occurrence without adding an item to every user's notification inbox.

How user alerts work

When Notify Users is enabled, Jitra identifies active users who can access the Object and evaluates each user's Event alert preferences.

A user can receive the same personal notification record through the supported experience on Jitra Web or Mobile. Depending on permission, subscription, app state, and preference, delivery can include a realtime Web alert, browser push, or Mobile push.

Changing a preference affects future occurrences. It does not remove Event History or notifications that were already created.

How email notification works

Email delivery is configured at the Event rule level and is independent from Notify Users.

The Event manager can configure recipients, subject, and body using supported Event variables. Preview and test functions help validate the message before the rule is used in live operation. When a matching occurrence is created, Jitra renders the template and processes the email as a separate delivery attempt.

Email is useful when the recipient should receive a readable operational message without opening another integration. It is not an email campaign tool: unrestricted HTML, attachments, CC, BCC, SMS, WhatsApp, and voice calls are outside the current Event delivery scope.

How an Event webhook works

A webhook lets an external system react to a supported Jitra Event.

When the configured rule is triggered, Jitra can send an HTTPS POST containing a versioned Event payload to an approved destination. A secret can be configured so the receiving system can verify the signature. The supported workflow also provides a payload example and test delivery.

Webhook delivery remains separate from the Event occurrence and other channels. If a request fails, Jitra retains the occurrence and records delivery status without cancelling email or user notification processing.

Webhook destinations are not yet provisioned through a fully self-serve flow. The current setup follows the supported process with the Organization administrator or Jitra support. Learn more on the Jitra Integrations page.

Why the channels are independent

Different operational situations need different destinations:

Event History gives authorized users a complete record to review later.
Notify Users creates a personal notification and supports Jitra Web or Mobile alert delivery.
Email sends a readable message to configured recipients.
Webhook passes structured Event data to an external workflow.

An Organization can enable the channels that fit each rule. A webhook-only Event does not have to fill a user's inbox, and a personal alert does not require an external webhook.

Practical examples

Geofence arrival

A delivery vehicle enters a customer geofence. Jitra records the occurrence, alerts eligible users, emails an operations address, or sends the Event to an external workflow according to the rule configuration.

The Event indicates that the Object entered the geofence. It should not be treated as proof of delivery unless a separate business process confirms delivery.

Vehicle stopped too long

A rule detects that a vehicle has remained stopped beyond the configured duration. Operations can review the occurrence and its available location context, while an email or webhook prompts the appropriate follow-up.

GPS signal lost

Jitra records when the supported condition indicates that GPS signal has been lost. A later GPS Signal Recover Event can form a separate occurrence. Power, connectivity, device state, and installation still need investigation before deciding the cause.

Sensor condition

When a compatible device, protocol, installation, and sensor provide the required data, a rule can evaluate the configured sensor condition. Never assume that every connected GPS device exposes the same telemetry fields.

Configure alerts that people can act on

More alerts do not automatically produce better visibility. Before activating a rule:

name the operational condition clearly;
select only the Objects that need the rule;
use duration, geofence dependency, and cooldown to reduce noise;
choose recipients who can take action;
test email or webhook delivery before relying on it;
document what response should follow the Event;
review false positives and adjust the rule with evidence.

The goal is a useful operational signal, not the highest possible notification count.

Availability and capacity

Event occurrence history and supported in-app or push notification capabilities follow the active Jitra plan and product access. External API, Webhook, and Email channels require Jitra Pro and an active Integration entitlement.

Jitra Pro includes starter integration capacity. Higher-volume delivery can use an Integration+ option according to the current pricing and entitlement catalog. Check Jitra Pricing for the current commercial details.

Choose the channel that matches the next action

Use the personal Jitra notification experience when a user should review the Event in Jitra. Use email when a human recipient needs a readable message. Use a webhook when another system needs structured Event data to continue a supported workflow.

You can start by connecting one Object, creating a focused rule, and validating the resulting Event History before expanding delivery channels. Start free, explore Jitra Features, or review Jitra Integrations.