Getting started
Understand the terms used in Truckers Data
A plain-language reference for applications, applicants, assignments, consents, mappings, connections and verification statuses.
AdminUserApplicantEmployer3 min read
People and application records
| Term | Meaning |
|---|
| Applicant / driver | The person applying for work through a company’s public form. |
| Application | A driver’s recruiting record for a particular company, with status, documents, history, notes, tasks and related information. |
| Assigned to / owner | The staff user responsible for following up on an application. Assignment is separate from the driver’s identity and application status. |
| Carrier | A trucking company using the hiring workflow for its operation. |
| Recruiting agency | An organization that can connect with carriers and manage recruiting work. Cross-carrier access depends on role and collaboration. |
| Admin / User | Internal staff roles. Admins configure the company; users work with permitted records. Additional visibility and sensitive-data controls still matter. |
| Full / Compact / Signature | Sharing formats. Full has the full application workflow; Compact is a short intake; Signature currently routes into the same application page. Compare formats. |
Consents, documents and verification
| Term | Meaning |
|---|
| Consent | A configured acknowledgement or authorization presented during the full application’s consent stage. |
| Active | A consent’s availability switch. Active is separate from Required and does not reset a previous acceptance. |
| Required consent | An acknowledgement that must be checked before the applicant continues through that consent stage. |
| Global consent | A consent whose scope can extend across companies. It is not simply the ordinary company-specific default. Read the scope warning. |
| Merge tag | A supported placeholder filled with application, company, signature or employer information when a rich-text consent is rendered. |
| DQ file | The driver-document collection kept under an application’s Files tab. |
| Employment verification | A request and response for one employment-history item. The employer contact uses their verification link rather than your staff account. |
| Verification timeout | No response was received within the configured reminder period. It is not the same as an employer confirming the history. |
Connections and field mapping
| Term | Meaning |
|---|
| Source field | The incoming field name or JSON path supplied by Facebook or a webhook sender. |
| Target field | The applicant, application, custom or metadata field where Truckers Data should put the incoming value. |
| Field mapping | The association between a source field and a target. Renaming a source does not automatically update an existing mapping. |
| Custom field | An internal application field configured for the company and available in supported integrations or API workflows. It is not automatically a public question. |
| Inbound webhook | An endpoint that another system calls to deliver lead information to Truckers Data. |
| Sample payload | Example JSON used to discover incoming source paths for mapping. |
| API token / webhook secret | A credential for a system connection. Keep it private and use the credential format required by the relevant integration. |
| Referral | A source-specific sharing link used to distinguish recruiting channels. Confirm attribution on a received application after testing. |
Help