Lead Lifecycle, Routing, and Security Notes
Lifecycle overview
A typical lead moves through these stages:
A lead is submitted by an approved supplier or captured through an approved campaign.
The platform validates required fields and consent/source metadata where configured.
Duplicate, suppression, spam, and routing eligibility checks may be applied.
Eligible leads are matched to approved buyer or partner rules, caps, status, and delivery channels.
The lead is delivered through the configured channel.
Delivery, return, dispute, billing, and audit events are tracked for reporting and reconciliation.
Routing factors
Routing may consider:
Geography.
Vertical.
Campaign or source.
Qualification fields.
Buyer eligibility.
Caps and pacing.
Delivery method.
Commercial terms.
Compliance requirements.
Account-specific rules.
Exact routing configuration is private and may vary by partner agreement.
Security principles
Credentials are account-specific and should be stored server-side.
Sensitive lead data should be transmitted only through approved secure channels.
Buyer API access is scoped to records owned by that buyer account.
Supplier API access is scoped to approved supplier submission workflows.
Internal operational details are intentionally excluded from public documentation.