DataTool
Check your SDK integration | Telematics Data and User Permissions | Export telematics data to check user activity | Heartbeats API
Last updated
Check your SDK integration | Telematics Data and User Permissions | Export telematics data to check user activity | Heartbeats API
Last updated
Follow to your DataHub account and find DataTool.
Search users by deviceToken, Email, Phone or Client ID
NOTE: You can always request for SDK status via this API: https://docs.telematicssdk.com/platform-features/heartbeats
In this section you can find main user information
Heartbeats - a system information that we receive from SDK in background. Average period of heartbeats is around 2 hours, but it also depends on user's connection to Internet.
Heartbeats help to indicate that the user has an installed application with active SDK and also shows all below information.
Trips on device - this indicator shows how many trips hasn't been sent from the SDK to our servers yet. The trips are always sent only if the internet connection is stable enough.
Last Date heartbeat - the date of last received heartbeat. If the date is more than 24 hours ago, it usually means that the users has removed the application or has no internet connection for this period or has some issues with permissions or issues with a smartphone.
SDK Version - SDK version that was installed in the application at the moment this latest heartbeat was sent.
Tracking - indicator that shows that the main trip tracking was enabled for this device when the latest heartbeat was received
RealTimeLocation - indicator that shows that the realtime location tracking was enabled for this device when the latest heartbeat was received
Logging - indicator that shows that the logging (system information that can help our developers to easily find any issue) was enabled for this device when the latest heartbeat was received
Received Tracks - the tracks that we received from SDK on our servers
Invalid Tracks - the tracks that have any mistakes
Process Tracks - the tracks that are valid and were passed through telematics platform
Excluded Tracks - the tracks that were excluded due to any wrong information (for example, the speed of the track was not high enough)
Enriched Tracks - the tracks that we indicate as driving trips. These trips user can see in the application and these trips are also shown in DataHub and other interfaces (API).
Last Track Date - Last Enriched Track Date
Last known Latitude and Longitude - Latest known location.
Device Model - the model of a smartphone that was used when the latest heartbeat was sent
Device OS Version - the OS platform and version that was used when the latest heartbeat was sent
This section helps to indicate if correct app permissions were set up and if it is a good internet connection, so the tracking will work correctly.
In this section you can easily export telematics data, including the heartbeats history.
