> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usejuiced.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Lead Types
> How leads are categorized and routed using conditions.
Lead types are a refinement of a [lead category](/features/lead-categories) that provide additional classification. While lead categories define who a person is and what they want, lead types help identify their level of intent and value.
## Conditions
Each lead type has conditions that determine which leads it matches. Conditions use fields from the parent lead category to evaluate incoming leads.
To create a condition, you:
1. Select a field from the lead category
2. Choose an operator (options vary based on the field's data type)
3. Enter a value to check against
You can add as many conditions as needed.
### Available operators
The operators available depend on the field type you select. On date fields, some operators display with date-friendly labels—"Before," "After," and "On" instead of "Less than," "Greater than," and "Equals."
| Operator | Date-field label | Available for | Description |
| ---------------------- | ---------------- | --------------------- | ------------------------------------------------------ |
| Equals | On | All field types | Exact match |
| Does not equal | Not on | All field types | Does not match |
| Contains | — | Text fields | Value contains the specified text |
| Does not contain | — | Text fields | Value does not contain the specified text |
| Less than | Before | Numeric, date fields | Value is less than (or before) |
| Less than or equal | Before or on | Numeric, date fields | Value is less than or equal to (or on or before) |
| Greater than | After | Numeric, date fields | Value is greater than (or after) |
| Greater than or equal | After or on | Numeric, date fields | Value is greater than or equal to (or on or after) |
| Between | — | Numeric, date fields | Value falls within a range |
| Within the past N days | — | Date fields | Date is within the specified number of days from today |
| Older than N days | — | Date fields | Date is more than the specified number of days ago |
| Any | — | List of Values fields | At least one of the specified values is present |
| All | — | List of Values fields | All specified values are present |
| None | — | List of Values fields | None of the specified values are present |
The relative date operators—**Within the past N days** and **Older than N days**—are useful for time-sensitive routing. For example, you could create a lead type that only matches leads where a quote was requested within the past 7 days.
### Condition logic
Conditions are organized into groups with the following logic:
* **Within a group**: Conditions are combined with AND (all must be true)
* **Between groups**: Groups are combined with OR (any group can match)
Say you want to create a lead type for high-value home insurance leads. You might set up conditions like:
**Group 1** (homeowners with high property values):
* `property_type` equals `single_family` AND
* `estimated_value` greater than `500000`
**Group 2** (new construction):
* `year_built` greater than `2020` AND
* `square_footage` greater than `2500`
A lead matches this lead type if it satisfies all conditions in Group 1 OR all conditions in Group 2.
## Fallback lead types
A fallback lead type catches any lead that doesn't match other lead types within the same lead category. When you create a lead category, a lead type is automatically generated and configured as the fallback.
When the fallback option is enabled:
* Conditions are hidden (since fallback matches everything that didn't match elsewhere)
* Priority is automatically set to the lowest
To add conditions to a fallback lead type, you must first uncheck the fallback option.
## Priority
Priority determines the order in which lead types are evaluated when a lead could match multiple lead types.
If your lead types have non-overlapping conditions, priority doesn't matter—each lead will only ever match one lead type. But if a lead could qualify for multiple lead types, the one with the highest priority wins.
Imagine you have two lead types for auto insurance leads:
* **Premium Drivers** (priority 1): `age` greater than `25` AND `violations` equals `0`
* **Standard Drivers** (priority 2): `age` greater than `25`
A 30-year-old with no violations matches both lead types. Because Premium Drivers has a higher priority, they're placed there instead of Standard Drivers.
Priority only applies to non-fallback lead types. Fallback lead types are always evaluated last.
## Bidding scopes
Bidding scopes define how customers can bid on leads within a lead type. You create them by configuring:
| Setting | Description |
| ----------- | -------------------------------------------------------------------------------------------------- |
| Scope | The geographic level at which bids are placed: county, state, or nationwide |
| Enabled | Toggle to activate or deactivate the scope |
| Fixed Price | When enabled, customers pay a single set price instead of bidding within a range |
| Minimum | The lowest bid a customer can place. Relabels to **Price** when Fixed Price is enabled. |
| Maximum | The highest bid a customer can place (hidden when Fixed Price is enabled) |
| Step | The amount by which bids increase between minimum and maximum (hidden when Fixed Price is enabled) |
Use **Fixed Price** when you want all customers to pay the same amount for leads—no bidding, no competition on price. This is ideal for flat-rate pricing models.
Until at least one bidding scope is enabled for a lead type, customers won't see any bidding options when they try to place a bid.
## Marketplace settings
Lead types also control marketplace behavior for leads that go unsold through normal distribution. See [Marketplace](/features/marketplace) for details on configuring these settings.
## Related guides
Create a lead type, write conditions, set priority, and configure bidding behavior.