The GSFleet connection brings the locations of linked devices to Spots in Spotilla. Data is transferred automatically from GSFleet to Spotilla. Updating a location and creating a read event are separate things: a Spot's location can change without a new read event.
Setup requirements
The GSFleet feature must be enabled for your organization. Connection settings and device links are configured in the browser with admin user permissions. You need permission to edit the Spot you want to link, and the Spot must have a tag with an internal ID. You cannot create a link to a deleted Spot.
You need a GSFleet API key that provides access to the devices you want to use. If GSFleet does not appear under integrations, see requirements for setting up an integration.
Save and check the connection
- Open Integrations and GSFleet in the service settings.
- Open Authentication, enter the API key and select Save. Saving checks the connection to GSFleet. If the check fails, the new credentials are not saved.
- You can check the saved key later by clicking Test Connection. A successful test updates Last verified successfully.
The connection test checks access to the GSFleet device list. It does not yet confirm that a particular device's location has been updated on its Spot.
The Environment menu shows Production and Sandbox. The GSFleet connection uses the same service with either selection. Selecting Sandbox does not prevent the Spot's location from changing if location synchronization is enabled.
Link a device and start location updates
- Open Settings and Linked devices for GSFleet.
- Select Link new device. Select a Spotilla Spot and choose the corresponding GSFleet device under Select device. Details such as the name, license plate, serial number and IMEI can help you identify the device if GSFleet returns this information.
- Confirm by selecting Link new device. A Spot can be linked to one GSFleet device, and the same GSFleet device can be linked to only one Spot.
- Select Update Spotilla locations from GSFleet in the settings and save the settings.
Automatic updates are scheduled approximately every 10 minutes. Linking a device does not itself fetch its location immediately. Updates also depend on the background run completing and on the location data returned by GSFleet.
How are locations and read events updated?
Synchronization fetches the location of each linked device. An accepted location replaces the Spot's saved coordinates, including any location previously set manually. On Android and iOS, you can open the Location view from the Spot details to see the map. In the Android device list, the location may appear as Fixed location because the coordinates are saved on the Spot. This label does not mean that GSFleet updates have stopped.
- The first accepted location saves the location and initializes the reference point for tracking movement. It does not create a read event.
- Newer location data updates the Spot's coordinates if they have changed. An unchanged location does not create a read event.
- A distance of more than 50 meters from the reference point creates a read event. The reference point then changes to the location of the new event. Before the first event, the reference point is the location saved during initialization.
For example, a device first moves 30 meters and then another 30 meters in the same direction. The first update changes the location without creating a read event. When the new location is 60 meters from the reference point, a read event is created. The distance is calculated between the coordinate points, rather than as the distance traveled. Exactly 50 meters is not enough.
A read event created by GSFleet is automatic: it has no associated mobile user and does not require physically reading the tag. The event timestamp is the time it is recorded in Spotilla, rather than the GSFleet measurement time. The device's coordinates are saved with the event. See also viewing read events on the map.
When is data not updated?
A location is accepted only if it has valid coordinates and a measurement time. Missing or invalid data is skipped. After initialization, data with the same measurement time or an earlier measurement time is also skipped. The location in Spotilla then remains unchanged; a point on the map alone does not guarantee the device's current location. Synchronization does not retrieve the device's complete route or every measurement made between updates.
The Spot statuses Inactive and Faulty do not stop GSFleet location updates. To pause updates, clear the location update checkbox or unlink the device.
A connection error can prevent an individual device from being updated. An authentication error, exceeding GSFleet's request limit or three consecutive temporary connection errors stops processing the remaining devices for that run. After an authentication error, automatic fetching stops until the credentials have been verified again by a successful save or connection test.
Check Integration Logs if the location is not updating. The run summary shows, for example, how many locations were updated, how many read events were created and whether data was skipped as outdated or invalid. For detailed instructions, see troubleshooting an integration error using the logs.
Pausing updates and removing links
Pausing temporarily: clear Update Spotilla locations from GSFleet and save. The links, last location and read events are retained. When you enable updates again, movement tracking continues from the previous reference point.
Removing a single link: open Linked devices, click the trash icon on the row and confirm. This removes the link between the device and the Spot. It does not delete the Spot, the GSFleet device, the Spot's last location or previous read events. You can then link the device or Spot again. A new link initializes location tracking from the beginning.
Changing a Spot's status to Deleted automatically removes its GSFleet link. Restoring the Spot to use does not restore the link; you must create it again.
Disabling the connection: first remove all GSFleet device links. Then select Clear saved credentials on the Authentication tab. This removes the saved GSFleet API key and synchronization settings. Spot locations and previous read events are retained.