Insights events generation
Insights event generation allows you to collect and retain information that provides a more detailed view of the anonymized data. The available information, such as trip origins and destinations, is mapped to traffic analysis zones or areas defined by different common denominators, such as postal codes.
The system identifies the first probe point in the supplied data as the origin of the trip and associates it with a relevant area or zone. Similarly, the destination is determined and mapped to a corresponding area. This information allows to generate insights while maintaining data privacy.
Types of insight events
Every insight contains the areaId attribute, which is the identifier of the associated area or zone. Additional attributes change depending on the nature of the information registered as an insight event.
The examples in the following sections show different types of insight events and their attributes.
Trace start
Indicates the area or zone where a trace (trip) starts.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T11:30:53",
"tp": "insights",
"tp2": "traceStart",
"ad": {
"areaId": "area-12345"
}
}
]
}Trace end
Indicates the area or zone where a trace (trip) ends.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T11:30:53",
"tp": "insights",
"tp2": "traceEnd",
"ad": {
"areaId": "area-67890"
}
}
]
}Staypoint
Indicates an area or zone where a staypoint has been detected.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T11:30:53",
"tp": "insights",
"tp2": "staypoint",
"ad": {
"areaId": "area-12487"
}
}
]
}Distance before staypoint
Reports the distance driven before reaching a staypoint, per area. Value expressed in meters.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T00:00:04",
"tp": "insights",
"tp2": "distanceBeforeStayPoint",
"ad": {
"areaId": "area-33445",
"value": "50"
}
}
]
}Distance after staypoint
Reports the distance driven after leaving a staypoint, per area. Value expressed in meters.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T00:00:05",
"tp": "insights",
"tp2": "distanceAfterStayPoint",
"ad": {
"areaId": "area-55667",
"value": "70"
}
}
]
}Trace distance
Reports the distance between the start and the end of the trace. Value expressed in meters, grouped by area.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T11:30:53",
"tp": "insights",
"tp2": "traceDistance",
"ad": {
"areaId": "area-77889",
"value": "100"
}
}
]
}Attribute change at staypoint
Indicates a change in an attribute (for example, battery or fuel level) at a staypoint.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T11:30:53",
"tp": "insights",
"tp2": "changesAttributesAtStayPoints",
"ad": {
"areaId": "area-98765",
"attributeName": "fuelState",
"value": "3"
}
}
]
}Regular events
A regular event refers to an event originating directly from the input data, unlike other insight events that are generated by the anonymization system. Customers can specify the event types or subtypes they are interested in, as well as select which extended attributes to collect from these events. Data that could compromise user anonymization, such as exact event coordinates, is not exposed.
The insight event includes the areaId, originalEventType, and extended attributes such as extAtt1, extAtt2. These extended attributes provide additional event details and can be filtered using the anonymization configuration.
{
"provider": "...",
"pe": [
{
"id": "probe-data-insights",
"t": "2026-01-26T00:00:03",
"tp": "insights",
"tp2": "regularEvents",
"ad": {
"areaId": "area-67890",
"originalEventType": "crash",
"extAtt1": "value1",
"extAtt2": "222"
}
}
]
}Updated yesterday