Rule types covered
Geofence entry or exit, low battery by threshold, container or vehicle with no movement for N days, speeding, OBD DTCs, customer zone entry, after-hours use. Combine the ones you need without touching code.
Alerts and rules
Only the alerts that matter. On the right channel. To the right person.
Configurable rules engine: geofence, battery, no movement, speeding, DTCs. Info/warning/critical severity and a different recipient per rule.
Most GPS platforms send 200 alerts a day. Nobody looks at them, and when a truly important one comes in, it gets lost in the noise. Trackia starts from the opposite principle: every alert reaches the right recipient, with the right severity, and only when it’s worth reading. You define the rules, no support tickets needed.
3
severity levels
∞
configurable rules
Email + push
native channels
Webhook
Slack/Teams integration
A rules engine that filters better than your boss would ever have time to
Designed so your alert inbox is still useful six months in.
Severity per rule
Three levels: info (silent log), warning (heads-up, no urgency) and critical (immediate, high-priority notification). You set the severity when you create the rule, and it carries through to email, push and the dashboard.
A different recipient per rule
The battery alert goes to the workshop. The customer-zone exit goes to the sales rep. Speeding goes to the transport manager. Each rule picks its own recipient list — nobody gets what isn’t their business.
Configurable scope
Apply the rule to the whole fleet, a group of vehicles, a single asset or an area of the map. Different rules for different operations coexist without anyone having to give up their workflow.
Noise control by default
Grouping of repeated alerts, muting by time slot (you don’t want alerts at 3 AM about a van sitting still in its parking lot), read marking and a daily digest. Your inbox stays useful.
Webhook output
To push critical alerts into Slack, Microsoft Teams or your internal system. Standard JSON, token authentication and automatic retries if your endpoint doesn’t respond.
Frequently asked questions
What people ask us most about this topic.
How long does a critical alert take to arrive after the event?
Between 5 and 30 seconds under normal conditions: the tracker reports to the platform, the rules engine evaluates it, the severity is set and email + push go out almost immediately. For safety cases (crash detection, jamming) there’s a priority channel that cuts that latency even further.
Can I stop alerts from reaching me at night or on weekends?
Yes, per rule. Each rule can have an active time window (Monday-Friday 8:00-20:00, for example) and stay silent outside it. Critical alerts can be set to “always on” if you want to get them every time, no exceptions.
Does it integrate with Slack and Microsoft Teams?
Yes, through webhooks. You set up your Slack channel endpoint or your Teams webhook, and the alerts you choose land in the channel in a readable format (not raw JSON). It also works with any internal system that accepts a POST with token authentication.
Is there an auditable log of who read each alert and when?
Yes. Every alert is logged with a timestamp, severity, recipients, who marked it as read and when. Useful for internal audits, certifications (ISO 9001, ENS) and cases where you have to prove someone was informed in time.
Start today
Start making decisions with data, not gut feeling.
A 30-minute demo. We tell you what Trackia can save on your specific fleet. No commitment.
No lock-in · Reply within 24h · Certified Teltonika hardware