Skip to main content
Lead categories and lead types are classification concepts unique to Juiced. Together, they help you categorize leads based on who they are and what they’re worth.
  • Lead category represents who the person is and what they want to do
  • Lead type refines that information to identify their level of intent and value
Think of lead categories as the “what” and lead types as the “how much.”

​
Basic fields

Every lead category comes with a set of basic fields automatically attached when you create it:
  • First name
  • Last name
  • Email
  • Phone
  • Address 1
  • Address 2
  • City
  • State
  • ZIP
  • County
You can’t remove these fields, but you can configure their properties and add custom fields on top of them.

​
Field properties

Each field has three important properties that control how it behaves during the lead lifecycle:

​
Required for post

When a field is marked as required for post, it must be present when a lead is submitted to the system. If the field is missing, validation fails and returns a 422 status code. No lead is created.

​
Required for ping

When a field is required for ping, it must be included during the ping phase of ping-post. If it’s missing, you’ll get a validation error.
Keep required-for-ping fields to a minimum. However, including key fields in pings helps ensure you get accurate pricing since the system needs that information to determine which lead type a lead belongs to.If a field is used in a condition to determine lead type but isn’t included in the ping, that condition will fail. This can prevent leads from qualifying for more valuable lead types.

​
Deliverable

Deliverable fields are visible to customers. They appear in the customer portal and are included when lead data is sent via webhooks.
The entire system is geographically based, so ZIP code is always required. If you’re generating leads at a state or national level only, you can pre-fill a valid ZIP code within the target state—or any valid US postal code for national campaigns.

​
Creating custom fields

When creating a new field, you’ll need to provide:

​
Field types

Field types determine what kind of data a field accepts and how it’s validated. Choose the type that matches your data format—the system will reject values that don’t match.

​
Text and numeric

​
Contact information

Phone fields validate against actual carrier patterns, not just digit counts. A random 10-digit number may fail validation if it doesn’t match a valid phone number format.

​
Geographic

ZIP and state fields cannot be marked as required for post or required for ping—these are handled at the system level since all routing is geographically based.

​
URLs and network

​
Dates

​
Date and time

​
Identifiers

​
Boolean

​
Constrained values

When using list-of-values, you’ll define the allowed options as a comma-separated list when creating the field. Any value not in your list will fail validation.

Adding fields to a lead category

Extend a category’s schema with custom fields beyond the basics.