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.
Last updated:
What State Filters Do
State filters restrict a buyer to leads from specific US states. When a lead is ingested, only buyers whose state filter includes the lead's `state` field (or buyers with no state filter) are eligible to receive it. Other buyers are skipped for that lead.
Configuration
- Open the buyer detail page.
- Find the State Filter section.
- Click Add States and select from the picker. Two-letter US state codes (TX, FL, CA, NY).
- Save. Filter takes effect on the next ingested lead.
Common Patterns
| Pattern | Setup |
|---|---|
| Single-state buyer | State filter: [TX]. Lead must have `state == TX`. |
| Multi-state regional buyer | State filter: [TX, OK, AR, LA]. Lead must have any of the listed states. |
| National buyer (no filter) | Leave State Filter empty — buyer is eligible for all states. |
| Inverse (everywhere except) | List every state EXCEPT the excluded ones. State filter doesn't have a native NOT mode. |
Combining with Zip and Custom Filters
State filter is one of several filter layers — it combines with AND logic against zip filters, custom field filters, and inbound campaign filters. A lead must pass every active layer to reach the buyer.
Lead eligible for buyer IF:
state IN [TX, FL]
AND zip IN [buyer's zip list]
AND case_type IS NOT EMPTY
AND incident_date >= 730 days agoIf a buyer's coverage isn't state-aligned (e.g., a metro area that crosses state lines), use a **zip filter** instead of (or in addition to) a state filter. Zip filters give finer geographic control than state-level routing.
Frequently Asked Questions
How do state filters work for buyers in Lead Distro AI?
Each buyer has an optional list of US state codes (TX, FL, CA, etc.) they accept leads from. Incoming leads' `state` field is checked against each eligible buyer's filter — only buyers whose filter includes the lead's state (or buyers with no state filter at all) are considered for distribution. Other buyers are skipped for that lead.
Can a buyer cover multiple states with a single filter?
Yes — add as many state codes as you need (TX, OK, AR, LA, etc.) to a single buyer's state filter. There's no limit to how many states. Common for regional buyers who serve a multi-state area or for national buyers who carve out specific states from coverage.
How does a state filter combine with zip code filters?
AND logic. A lead must pass both the state filter AND the zip filter to reach the buyer. Useful when the buyer covers a state but only specific zip codes within it — e.g., a Texas law firm that only takes leads from Houston metro zip codes. Set both filters and they compose.
What happens to a lead whose state isn't covered by any buyer?
Lead is marked UNMATCHED with status reason `no_eligible_buyer`. Held in the dashboard. Common fix: add a fallback national buyer with no state filter that absorbs everything other buyers don't cover. Useful when traffic occasionally arrives from out-of-coverage states (e.g., a snowbird from Michigan asking about a Florida MVA).
Can state filters be scheduled?
Yes — like all filters, state filters support day-of-week and hour-range scheduling. Common use: a buyer's state filter is active only M-F 8am-6pm; outside those hours the filter doesn't apply (buyer doesn't receive leads). Equivalent to scheduling the buyer's active hours via the filter layer.
What if my lead's state field is missing or invalid?
Lead is rejected by the campaign-level inbound filter (set `state IS NOT EMPTY` as a required filter for state-routed campaigns). If you allow leads without a state, none of the state-filtered buyers will be eligible — the lead routes only to buyers with no state filter. Recommended: require state at the campaign level for state-routed verticals.
Related Articles
Buyer Basics
Manage buyers in Lead Distro AI: delivery methods, lead caps, pricing, state and field filters, white-label client portals, and real-time acceptance rules for every buyer in your lead operation.
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.
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