Buyer Basics
Manage buyers in Lead Distro AI: delivery methods, lead caps, pricing, state and field filters, white-label buyer portals, and real-time acceptance rules for every buyer in your lead operation.
Last updated:
What is a Buyer?
A buyer is a client who receives and pays for leads. Buyers are connected to campaigns with routing configuration — price per lead, priority, daily cap, state filters, and delivery method.
Delivery Methods
| Method | Description |
|---|---|
| Leads are delivered via email notification. | |
| Webhook (POST) | Leads are posted to the buyer's webhook URL as JSON. |
| Google Sheet | Leads are appended as rows to a connected Google Sheet. |
State Filters
Buyers can be configured to only receive leads from specific states. When a lead comes in, only buyers whose state filters match (or who have no state filter) are eligible to receive it.
Suppression Lists
Upload suppression lists to prevent duplicate leads from being sent to a buyer. Suppression matching is done by phone or email using MD5 hashes for privacy.
Buyer Portal
Enable a white-labeled buyer portal for your buyers. They get their own login to view their leads, track delivery, see performance metrics, and manage returns — without accessing your full dashboard.
Buyer portals are created as separate organizations in Clerk. When you enable a portal, a new org is created and linked to the buyer.
Frequently Asked Questions
What delivery methods can a buyer use to receive leads?
Three primary delivery methods: Email (notification with lead details), Webhook (JSON POST to any URL — CRM, dialer, automation tool), and Google Sheet (appended as a new row). Webhook is the most common for serious buyers. You can also attach Automations to a buyer that fan out additional notifications (Slack, secondary CRM) in parallel with the primary delivery.
How do I set lead caps for a buyer?
Each buyer has cap windows: daily, weekly, monthly, and total. Set any combination — for example, 50 leads/day with a 1,000 lead total cap. Dollar budget caps work the same way on the same windows. When any active cap is hit, the buyer is paused for that window. Daily caps reset at midnight in your account timezone; weekly/monthly reset on the corresponding cycle. The Reset Caps action manually clears all current-window counters.
Can buyers bid on individual leads in real time?
Yes — enable Real-Time Price on a ping-post buyer. When Lead Distro AI pings the buyer with partial lead data, the buyer's system returns an accept/reject response with an optional
bid_price field. The highest bidder wins the lead, and the bid price becomes the lead's revenue. Combine with the supplier-side Revenue Share cost mode to automatically calculate margin even when bid prices vary lead-to-lead.How do state filters work?
Buyers can be configured to receive leads only from specific US states. When a lead is ingested, Lead Distro AI checks the lead's
state field against each eligible buyer's state filter. Only buyers whose filter includes the lead's state (or who have no state filter at all) are eligible to receive it. State filters compose with field filters and zip-code filters using AND logic — a lead must pass all configured filters to reach the buyer.What are suppression lists and how do they work?
Suppression lists prevent specific leads from being sent to a buyer based on phone number or email. Upload a CSV; Lead Distro AI stores MD5 hashes (not the raw values) for privacy. On each ingest, the incoming lead's phone and email are hashed and matched against the buyer's suppression list. Matches are silently routed past that buyer to the next eligible one. Use cases: avoiding duplicate sends to a buyer's existing clients, honoring DNC requests, blocking known bad leads.
What is the Buyer Portal?
A separate, white-labeled interface for each buyer. They get their own login at the same domain and are routed to the portal view — they can review their leads, track delivery status, see performance metrics (acceptance rate, return rate), and submit returns. They can never see your costs, other buyers' data, or your full agency dashboard. Portals are implemented as separate Clerk organizations linked to the buyer record, so member management and SSO work the same as your main org.
Can a buyer receive leads from multiple campaigns?
Yes. A single buyer can be attached to any number of campaigns with different configurations per campaign — different prices, different caps, different delivery URLs. From the buyer's portal view, they see leads from all campaigns they're attached to in a unified inbox. Useful when one client buys multiple verticals from you (e.g., a law firm that wants both MVA leads and slip-and-fall leads).
How do nested AND/OR filter groups work for buyers?
Buyer filters support nested AND/OR groups so you can express complex routing logic. For example:
(state == TX OR state == FL) AND (case_type == auto_accident OR case_type == truck_accident) AND incident_date >= 30 days ago. Build groups visually in the filter UI, drag rules in or out of groups, and combine with scheduling so each filter group is only active during specific days/hours.Related Articles
Zip Code Filtering
Route leads to buyers based on zip code coverage in Lead Distro AI. Set service area filters, multi-zip buyer territories, and fallback rules for leads outside covered zones in any lead distribution campaign.
Delivery Methods
Lead Distro AI buyer delivery methods — Webhook (JSON POST), Email, Google Sheet. How each works, when to use which, and FAQs for picking the right delivery for each buyer.
State Filters
Route leads to Lead Distro AI buyers based on US state coverage. State allowlists, multi-state buyers, combining with zip and custom filters, and FAQs.
Custom Field Filters & Nested AND/OR
Build buyer filters on custom fields with nested AND/OR group logic. Case-type filters, recency rules, numeric ranges, complex branching, and FAQs for Lead Distro AI.
If you have any questions, send us an email at support@leaddistro.ai