Understand the Airlead data model
Airlead separates a contact from their demand and from the process that distributes that demand. This prevents contact details, qualification data, and commercial delivery history from becoming mixed together.The complete flow
Core concepts
Records
Records is the shared area for information Airlead stores about people, companies, and interests. Think of it as the workspace-wide database—not a single campaign or delivery setup.Person
A person contains identity and contact information such as name, email, phone number, address, and consent details. A person is not the same as an interest. The same person can ask about different products or return with another request later.Interest
An interest is a person’s request for a specific product. It contains the qualification answers and delivery state for that request. Example: Maria is one person. Her request for solar panels is one interest; a later request for a heat pump is another interest.Product and fields
A product defines what is being requested and which information Airlead should capture. Its fields hold qualification answers such as property type, location, desired timeline, or budget. Those same fields can later be used to decide whether a buyer is eligible. Airlead keeps three field layers separate: person fields for contact and consent, product fields for qualification answers, and capture fields for attribution such as partner or campaign.Source
A source describes where data enters Airlead and how it should be interpreted. Sources can receive data through a webhook, CSV upload, email, Connect, or an operator workflow. The source owns ingest settings such as authentication, mapping, test/live operation, and external IDs.Channel
A channel is the Markets workspace for distributing a defined stream of interests. It brings together:- the sources that supply interests
- the product and qualification information
- the pools and buyers that may receive them
- the rules and limits used for delivery
- the activity and transactions created along the way
Buyer and pool
A buyer is a commercial recipient of delivered interests. A pool groups buyers that participate in the same routing setup. Field criteria, product compatibility, capacity, delivery settings, and channel configuration determine whether a buyer can receive a particular interest.Transaction
A transaction is the auditable record of a concrete delivery to a buyer. It tracks the recipient, delivery mode, commercial values, and lifecycle outcomes such as confirmation, rejection, Storno, or payout.Common distinctions
Example
A solar form sends a request to an API source:- Airlead finds or creates the person.
- Airlead creates the solar interest with the submitted field values.
- Duplicate and validation rules evaluate the request.
- The channel checks which buyers are eligible.
- An operator delivers manually, or Delivery 1.0 in Airlead AI evaluates the interest for automated delivery when enabled.
- Each successful buyer delivery creates a transaction.
- Confirmation, Storno, and settlement update that transaction over time.