Supplier Lead Fields and Consent Requirements
Final required fields may vary by supplier agreement and campaign.
The platform accepts mapped supplier payloads and normalizes them into internal lead fields before scoring and routing.
Minimum expected information
Field | Description | Required |
|---|---|---|
external_id | Stable ID from the supplier system for deduplication and support. | Strongly recommended |
full_name or first_name | Lead contact name. | Yes |
email or phone | At least one contact method. | Yes |
state | Business/contact state used for geo eligibility. | Usually |
debt_amount | Business debt amount or campaign-specific qualification value. | Usually |
business_name | Business name when available. | Recommended |
source or utm_source | Campaign or source identifier. | Recommended |
consent_timestamp | When consent was captured. | Recommended |
source_form_url | URL where the lead submitted or consent was captured. | Recommended |
lead_ip and user_agent | Compliance and fraud-review evidence. | Recommended |
Data handling rules
Submit only leads collected with proper permission and under your agreement.
Do not submit test, fake, suppressed, or knowingly duplicate leads unless using an approved test process.
Do not email spreadsheets containing sensitive lead information unless your representative approves a secure transfer method.
Include source and consent evidence whenever possible.
Use stable external IDs so support and reconciliation are easier.