Lead Categories

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.” You’ll find them under Ingest → Lead Categories in the sidebar. The list shows each category’s name, description, its lead types, and whether it has a fallback lead type.

​

Start from a template or from scratch

Click New lead category. When templates are available, you’ll choose Start from a template to begin with a market-specific field set, or Start from scratch to name the category and add your own fields. The template list is searchable and shows how many fields each template adds. Templates are a starting point, so review the included fields, required settings, and deliverable settings before you connect a source. Creating a category from a template copies its fields into the new category. Later template changes do not rewrite categories you already created, so your existing schemas stay yours to control. Every new category, template or not, also gets a fallback lead type with the same name, so leads in the category always have somewhere to land.

​

The lead category page

Click a category to open it. The top of the page shows Leads received, Leads assigned, and Revenue for the selected timeframe (the last 30 days by default), each compared with the previous period. Below that are three tabs.

• Lead Types lists the category’s lead types, with the fallback marked.
• Sources lists the sources that send leads into this category.
• Fields holds the category’s schema. This is where you add and configure fields.

Edit in the header changes the category’s name and description. Delete removes the category, but only once no sources use it.

​

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

They’re marked with a System badge in the Fields tab. You can’t rename or remove them, but you can configure their properties and add custom fields on top of them.

​

Field properties

Each field has four 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.

​

Deliverable

Deliverable fields are visible to customers. They appear in the customer portal and are included when lead data is sent via webhooks.

​

Hidden from API spec

Hidden fields don’t appear on the API specification page you share with your sources. Use this for internal tracking fields you don’t want vendors to see or send. You can flip any of these four properties straight from the switches in the Fields table, without opening the field.

​

Creating custom fields

When creating a new field, you’ll provide the following.

​

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, because the system will reject values that don’t match.

​

Text and numeric

​

Contact information

​

Geographic

​

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.

​

Related guides