DataHub User Guide
Sign upSign inService Desk
Search…
Sandbox - Get started
Sandbox
Credentials
DataTool
Permissions
Product Management
Access Management
Invite & Link app users
Schedule
Point realtime data to 3rd party platform
DataHub
Users
Trips
Inspections
apps
Applications | Telematics Settings Guides
Info
Changelog | Release Notes
Report a bug
Powered By GitBook
DataTool
Check Telematics Data and User Permissions | Export telematics data to check user activity
Follow to your DataHub account and find DataTool link in your top right corner menu.

Check User

DataTool | Check User

User

In this section you can find main user information

SDK

Heartbeats

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.
​

Services

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

​

Telematics Data (Latest 7 days)

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

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

​

Status of Application and Device Permissions

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.

Export Data

In this section you can easily export telematics data, including the heartbeats history.
DataTool | Export Data
Sandbox - Previous
Credentials
Next - Sandbox
Permissions
Last modified 1yr ago
Copy link
On this page
Check User
User
SDK
Heartbeats
Services
Telematics Data (Latest 7 days)
Device
Status of Application and Device Permissions
Export Data