Bring device location into Fencemaker through whichever path matches what your fleet already supports — a connected GPS platform account, a webhook push, or your own API call.
THREE WAYS IN → ONE PIPELINE → GEOFENCING, TRIPS, ACTION ENGINE
Three ways in, one pipeline out
Connect through whichever path your fleet already has in place. Register a device, start sending positions, and it feeds straight into Fencemaker's geofencing, Trips, and Action Engine — one pipeline, no separate setup per source.
GPS Vendor Bridge — point any existing GPS tracking server at Fencemaker, or run a lightweight mobile tracking app on driver phones with zero extra hardware
Webhook — push positions in your own JSON format to a dedicated ingestion endpoint
Direct API — POST location updates straight to our tracking endpoint with a Vendor API key, no intermediary service required
Devices auto-register on first ping — no manual provisioning step
Live device health built in: last position, speed, heading, battery, and a status flag (active / delayed / needs review)
Every ingested device flows automatically into Geofencing, Trips, and Action Engine — no reconfiguration per module
Typical uses
Fleets already running a GPS tracking platform who want geofencing without migratingPhone-only field teams using a mobile tracking appCustom hardware or platform integrations posting via webhook or APITeams evaluating Fencemaker before committing to a dedicated integration
All three ingestion paths are available on every plan, including the free tier. Devices registered count against your plan's device cap — 5 on free, 100 on starter, 750 on growth, 2,500 on scale; enterprise is negotiated per contract.