Lytx
DLH.io documentation for Lytx
Lytx is a fleet video telematics and driver safety platform. Its DriveCam devices record safety events in vehicles, along with trips, GPS positions and driver assignments. Bringing this data into your warehouse lets safety and fleet teams analyze risky behaviors, coaching activity, trips and geofence activity alongside the rest of their operational data.
Setup Instructions
Follow the setup steps guide for configuring your Lytx connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | |
| Incremental/Delta Load | ✓ | Safety events, trips, driver assignments, geofence activations and GPS points are read incrementally; other tables are read in full each run |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | Users deleted in Lytx stay in the data with the status Deleted | |
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
- Lytx offers no way to ask only for changed vehicles, devices, groups, users or geofences, so these tables and the lookup lists are read in full on every run.
- Safety events are read by the time Lytx last updated them, so later runs also pick up new reviews, coaching and notes on older events.
- Trips and driver assignments are read back to six days before the previous run, since a long trip reaches Lytx only after it ends. Geofence activations are read back five days, since an activation keeps changing until it ends. GPS points are read by the time Lytx received them.
- A note removed from an event in Lytx is removed from the data by a historical re-sync.
- Without a Historical Start Date, the first synchronization reads ten years of safety events and driver assignments, the last three years of trips, and the last 60 days of GPS points and geofence activations, which is as far back as Lytx keeps them.
- GPS points need a Lytx Fleet Tracking subscription. They are the largest table, about 150 thousand points a day for a fleet of three thousand vehicles. Uncheck the
GPS_POINTStable if you do not need it; with it selected, the first synchronization can take an hour or more. - DLH.io sees only the groups and data that the Lytx user you provide can see.
Issue Handling
If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.
Replicated Entities
The following entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:
VEHICLESGROUPSUSERSUSER_GROUP_ROLESGEOFENCESDEVICESSAFETY_EVENTSSAFETY_EVENT_BEHAVIORSSAFETY_EVENT_DYNAMIC_RISKSSAFETY_EVENT_REVIEW_NOTESSAFETY_EVENT_NOTESSAFETY_EVENT_COACHING_NOTESVEHICLE_STATUSESVEHICLE_TYPESSEATBELT_TYPESEVENT_STATUSESEVENT_TRIGGERSEVENT_TRIGGER_SUBTYPESEVENT_BEHAVIORSEVENT_DYNAMIC_RISKSUSER_ROLESGEOFENCE_END_REASONSTRIPSDRIVER_ASSIGNMENTSDEVICE_VEHICLE_ASSIGNMENTSGEOFENCE_ACTIVATIONSGPS_POINTS
Schema Details (ER Diagram)
This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.