Lead fields that know what they are holding
Every lead category starts with the fields you always need, and every field you add is typed, so a bad state code, a malformed phone number or an invalid ZIP is rejected when the lead is posted rather than discovered by your buyer.
Juiced gives you typed fields rather than a bag of text fields: a county field that knows what a county is, a states field that validates an abbreviation, a phone field that knows the difference between a US, Canadian, Australian and international number.
And rather than one required checkbox, each field has separate switches for post and ping, because what you need to quote a lead is a shorter list than what you need to sell it.
Every lead category starts here
Ten fields come as standard on any lead category, in every vertical. You extend from here rather than starting empty.
| Field | Type |
|---|---|
| first_name | Text |
| last_name | Text |
| phone | Numeric |
| address_1 | Text |
| address_2 | Text |
| city | Text |
| state | Text |
| zip | Postal Codes |
| county | Counties |
The field types
Pick the type when you create the field. The type decides what the field accepts, which means bad data is caught at the door instead of traveling downstream.
| Type | Accepts | Use it for |
|---|---|---|
| Text | Any text | Descriptions, identifiers, anything free-form |
| Valid email addresses | Contact email, secondary email | |
| Numeric | Numbers only | Amounts, counts, scores |
| Boolean | True or false | Yes/no screens, for questions where "unsure" is not a real answer |
| List of Values | One of a set you define | Any screen with a fixed set of answers |
| Phone | US, US or Canada, Australian, or international | Contact numbers, validated to the market you sell into |
| Postal Codes | 5-digit ZIP | ZIP-level filters and bidding |
| States | US state abbreviation | Territory filters and state-level bidding |
| Counties | County name | County-level routing and bidding |
| Countries | ISO two-letter country code | Multi-country operations |
| Dates | YYYY-MM-DD, MM/DD/YYYY or DD/MM/YYYY | Incident dates, timelines, anything with a deadline |
| Date & Time | The same three, with a time | Consent timestamps, submission times, appointment times |
| URLs | With or without the scheme | Landing pages, consent certificates, recordings |
| IP Address | An IP address | Provenance on the capture |
| Identifiers | ULID or UUID | Your own system's reference on the record |
Geography is where lead routing quietly breaks. A text field holding "California", "CA" and "calif" looks fine until a buyer who bought California stops receiving leads. Typed state, county and ZIP fields make territory a first-class concept, so filters and bids work on what the field means rather than on string matching.
Four switches, not one required box
Every field carries these independently.
Post and ping are different questions
A ping asks does anybody want this kind of lead, and what will they pay. The post delivers the lead itself. They need different amounts of information, and a single required flag cannot express that.
Require the whole record at ping time and you refuse to price leads you could have sold. Require too little at post time and you deliver records the buyer cannot work. Setting the two separately is how you avoid both: ping on the handful of fields that decide fit and price, post on everything the buyer needs to act.
Deliverable is not the same as collected
A field can be captured and used for routing without being passed on. Internal scoring, the sub ID identifying which campaign produced the lead, a supplier reference: all useful to you, none of it the buyer's business. Turning deliverable off keeps the field working inside your own distribution while leaving it out of what the customer receives.
Fields are per category, and categories are yours to shape
- A lead category holds the field definitions: the shape of the leads in it.
- Lead types sit under a category and carry the routing, bidding and pricing rules, so several products can share one field set.
- Buyers filter on the fields, which is why the values matter: a list of values gives every buyer the same vocabulary to filter against, where free text gives them a guessing game.
The practical effect is that you model a vertical once. Adding a new product in the same vertical is a new lead type over the same fields, not a new integration.
Frequently asked
What lead fields does Juiced include by default?
Ten, on every lead category: first name, last name, email, phone, two address lines, city, state, ZIP and county. ZIP and county are typed for routing rather than stored as plain text.
Can I add my own fields?
Yes, as many as you need, each with a type and an optional description. Field sets differ by vertical: a legal lead might carry the incident state and a consent certificate URL, a home services lead the job type and timeline.
What is the difference between required for post and required for ping?
Post is the full lead being created; ping is the check for which buyers want it and at what price. A ping usually needs only the few fields that decide fit (vertical, territory, the key screens) while the post needs everything the buyer will act on. Setting them separately means you can price a lead on a short record and deliver on a complete one.
Can a field be collected but not sent to the buyer?
Yes. Turn off deliverable and the field is stored and usable for routing and filtering, but excluded from the lead data the customer receives. This is how sub IDs, supplier references and internal scores stay internal.
Why does the field type matter?
Because it decides what gets rejected at the door. A typed state field refuses an invalid abbreviation at post time; a text field accepts it and the problem surfaces later as a buyer complaining about lead quality. Typed geography fields also make territory filters and location bidding work on meaning rather than string matching.
Can buyers require different fields from each other?
Yes. Buyers set their own filters, so two buyers in the same vertical can demand different evidence and each receives only the leads that match.
Model your vertical once.
Typed fields, per-buyer filters, and separate post and ping requirements, so the right leads reach the right buyers and bad data never gets that far.
Scale your lead business, without limits
Juiced puts you in full control of your leads, routing, and revenue, so you can automate, optimize, and grow without chaos.