via Offloads
Sentiance provides data offloads with driving insights to the clients on a daily basis.
Last updated
Sentiance provides data offloads with driving insights to the clients on a daily basis.
Last updated
The Sentiance platform offers various methods to access and analyze your end-users' data, one of which is through offloads—our implementation of a file-based system, typically in CSV format. Offloads generally contain data for all your users over a specific timeframe, by default a 24-hour tumbling window. Detailed field descriptions can be found below.
While offloads contain much of the core data, they do not include certain elements such as predictions, coaching data, or some fine-grained details.
Please consult with your Sentiance contact person to discuss the offloads before implementing.
Access to offloads is managed by the , with permissions authorized by the .
To check available offloads, use an API Key with the OFFLOADS_READ
scope. The query example is:
from
and to
are always days in the format YYYY-MM-DD
. The response looks like the following.
Offloads of several types are available (based on which Sentiance product offering you are using). Each day will contain one offload of each type and each offload item may have one or more associated files to download.
The files list their format, name, size and a link to download that file.
In the response above the link
field is null since no links have been generated for these files yet. Link generation is done with an API Key with the scope OFFLOADS_GENERATE_URL
.
Links expire after a set time and must be regenerated if needed. Offloads for the previous day are fully available, while current-day offloads may be incomplete.
The following offloads are available based on your product selection on the Sentiance platform.
The driver passenger offload contains a list of transports, together with a corresponding prediction of driver or passenger (of the mobile user).
This offload file contains a list of transports, together with their corresponding lists of all driving events. The following driving events are available:
accelerating events
phone handling events
turning events
mounted events
braking events
speeding events
call events
screen events
All driving events for transports are included in this offload.
This offload file contains a list of transports, together with their corresponding lists of significant driving events. The following driving events are available:
accelerating events
phone handling events
turning events
mounted events
braking events
speeding events
call events
screen events
Significant events are a subset of all events, and only driving events that fall under certain thresholds are included (e.g. accelerations that have a high magnitude or calls that have a long duration).
These offloads contain a list of transports and their corresponding primary safety scores.
The primary safety scores available are:
legal
smooth
attention
overall
These offloads contain a list of transports and their corresponding secondary safety scores.
The secondary safety scores available are:
focus
harsh acceleration
harsh braking
harsh turning
anticipation
mounted
These offloads contain a list of users and their corresponding primary safety scores, based on their overall driving.
The primary safety scores available are:
legal
smooth
attention
overall
These offloads contain a list of users and their corresponding secondary safety scores, based on their overall driving.
The secondary safety scores available are:
focus
harsh acceleration
harsh braking
harsh turning
anticipation
mounted
Trajectories are information specific about the route that a transports followed. These offloads contain information such as the total distance traveled, the mapped waypoints of the transport, and the start and end addresses.
Transports represent the period of time a user moved from one venue to another. The transports offloads contain a list of transports and their corresponding predicted transport mode (e.g. car, train, bus, etc.), duration and top speed.
These offloads contain the trip by trip scores and their corresponding user scores based on your integration with the Engagement platform. Can be similar to Driving Insights scores or different if you have a custom integration.
These offloads contain events related to your user’s progress towards achieving Badges. A badge state can change to be ACTIVE
, IN_PROGRESS
or COMPLETED
.
These offloads contain events related to your user’s progress towards completing a challenge. A challenge state can change to: ACCEPTED
, COMPLETED
, IN_PROGRESS
, FAILED
, ABANDONED
.
These offloads contain events related to your user’s progress towards continuing and maintaining streaks. A streak state can change to: NEW
, CONTINUE
, BREAK
.
These offloads contain information about all social groups your users create.
These offloads contain information about users who are part of groups and their role in the groups. A user can have one of these roles: ADMIN
, MEMBER
, PENDING
.
These offloads contain information about each communication message that was generated for your users and whether or not a user interacted with it. A communication message can have one of these states: NEW
, MANUALLY_CLOSED
, AUTOMATICALLY_CLOSED
.
These offloads contain information about feedback provided by your users about our transport mode and occupant role predictions.
These offloads contain events generated by your user by using the mobile app.
Contains daily rewarded points for you users for the last 7 days.
To generate a link to the offload files, you must use the mutation, giving the day of the offload and the type as input. This will respond with.
Off-the-grids correspond to segments of time when the user was offline and not sending data from their mobile device to our platform. For an explanation of the possible of the grid reasons see .