Skip to main content
Every lead category starts with a set of basic fields, like name, email, phone, address, and so on. But your leads almost certainly carry more information than that. A home insurance lead might include property type and current coverage amount. A solar lead might include roof age and electric bill. Custom fields let you extend a lead category’s schema so you can capture, validate, and deliver that extra data.

​
Prerequisites

  • An existing lead category. If you don’t have one yet, open Lead Categories and click New lead category. Starting from a template gives you a market-specific set of fields to build on.
  • A role that can update lead categories.

​
1. Open the lead category’s Fields tab

Open Lead Categories in the sidebar (under the Ingest group) and click the lead category you want to add fields to. Then click the Fields tab.
Lead category page with stats at the top and Lead Types, Sources, and Fields tabsLead category page with stats at the top and Lead Types, Sources, and Fields tabs
The Fields table lists every field with its Title, Type, plus four switches for Required (post), Required (ping), Deliverable, and Hidden from spec. The 10 default fields (first_name, last_name, email, and so on) carry a System badge, which means they can’t be renamed or deleted.

​
2. Click New field

Click New field above the table. This opens the New field dialog.

​
3. Fill in the field details

​
Title

Enter a name for your field. This is the identifier sources use when submitting lead data through the API, so keep it machine-friendly.
  • Must start with a letter or underscore
  • Can only contain letters, numbers, and underscores (no dashes or spaces)
  • Must be unique within this lead category
  • Can’t be one of the names Juiced reserves for its own lead data, in any letter case (id, public_id, uuid, tenant_id, lead_category_id, lead_type_id, source_id, submission_id, customer_id, country_id, state_id, county_id, postal_code_id, assigned_at, and base_amount)
Good examples include property_type, coverage_amount, roof_age, and electric_bill. A field created before these names were reserved keeps its title, but shows a warning asking you to rename it. Rename it soon if it’s titled after an internal ID like state_id, because v1 webhooks don’t send those fields.

​
Type

Select the data type from the dropdown. The type you choose determines how the field’s value is validated when leads are submitted. See field types for the full list.
Choose your type carefully, because it affects validation. A field typed as Phone (US) will reject values that don’t match actual US phone number patterns, not just any 10-digit string.

​
Values (List of Values type only)

If you selected List of Values, a Values box appears. Enter the allowed values separated by commas, like single_family, condo, townhouse. Any submitted value not in this list will fail validation.

​
Toggle settings

Four switches control how the field behaves across the system.

​
Description

An optional description of what this field captures. It’s for your team’s reference.

​
4. Create the field

Click Create field. You’ll see a “Field created.” confirmation, and your new field appears in the Fields table. Repeat from Step 2 for each field you need.

​
Editing and deleting custom fields

Open a field’s row actions and choose Edit to change its properties. The same dialog opens with the current values filled in; click Save field when you’re done. To remove a custom field, choose Delete from its row actions and confirm. If the field is used in a condition (for example, in a lead type or a distribution stage), deletion fails with an error explaining that the field is in use. Remove the field from those conditions first.
Deleting a field is permanent. Any historical lead data for that field is preserved, but the field will no longer appear in the schema or be validated on new submissions.

​
Quick-toggling field properties

You don’t need to open the dialog to change a field’s switches. The Required (post), Required (ping), Deliverable, and Hidden from spec columns in the Fields table are live switches. Click one to flip it, and it saves immediately.
The required switches are disabled for the zip field. ZIP code is always required at the system level because all routing is geographically based.

​
What happens next

Once a field is added to a lead category, it takes effect immediately.
  • API validation starts enforcing the field’s type and required rules on new submissions
  • Deliverable fields start appearing in the customer portal and webhook payloads
  • Lead type conditions can now use the field to route leads to more specific types (see Defining lead types)
  • Sources should be updated to include the new field in their submissions, especially if you marked it as required for post. Share the source’s updated API specification with them (see Sending leads to Juiced).