Trip matching

Trip matching records when two device types travel from the same origin to the same destination. Unlike proximity association which creates live parent-child links, trip matching builds a historical log of shared journeys — "parcel P-88 was delivered by van V-12 from the loading dock to cold storage".

How it works

You define two device types (e.g., parcel and van), an origin radius, a destination radius, and a time window. The system watches for this pattern:

Both devices dwell at the same location (the origin) — their completed dwells overlap in time and fall within the origin radius.
Both devices are later seen at the same location (the destination) — their current positions fall within the destination radius, within the time window.

When both conditions are met, a trip record is created linking the two devices with the origin and destination locations.

What it's for

Trip matching answers the question: which items travelled together? This is useful when:

Delivery tracking — Know which parcels were on which van for each delivery run.
Equipment logistics — Track which tools went to which job site with which vehicle.
Chain of custody — Record that item A and item B were transported together from warehouse to customer.

Unlike proximity association (which maintains a live parent-child link), trip matching is purely historical. It doesn't change device relationships — it records that two devices made the same journey.

Parameters

Parameter	Description
`device_type_a`	First device type to match (e.g., `parcel`)
`device_type_b`	Second device type to match (e.g., `van`). Must differ from type A.
`origin_radius_meters`	Maximum distance between origin dwells to consider them co-located (1–10,000 m)
`destination_radius_meters`	Maximum distance between destination positions to consider them co-located (1–10,000 m)
`time_window_minutes`	How recently both devices must have been seen at the destination (1–1,440 minutes)

See the rule types reference for the full parameter specification.

Viewing trip reports

Trip records appear in the Trip History section on each asset's detail page. Each entry shows:

The matched device — the other device that travelled with this one.
The origin — shown as a zone name (linking to the zone) if the origin falls within a defined zone, or as map coordinates (linking to the map at that position).
The destination — same as origin: zone name with link, or coordinates with map link.

Trip history is visible from either device's perspective. If parcel P-88 travelled with van V-12, the trip appears on both assets' detail pages.

Notes

Only one enabled trip matching rule is allowed per device type pair. You can have rules for parcel/van and tool/van simultaneously, but not two rules both matching parcel/van.
The rule does not set a severity level — it records trips rather than raising alerts.
Devices must have a device_type set (via the asset type field) to be matched.