Setting Up a Source and Its Attributes

A source represents where leads enter the system, like a web form you own, a vendor API, or a partner feed. Before any lead data can flow into Juiced, you need at least one source wired up to a lead category with the right credentials and field configuration. This guide walks you through creating a source from scratch, exploring the settings that matter, and adding source-level fields (attributes) that extend or override your lead category’s schema.

Prerequisites

You need at least one lead category already created. Sources are always tied to a lead category that defines the base schema. If you don’t have one, open Lead Categories under Ingest in the sidebar and click New lead category.
Permission to create sources in your workspace (admins have it).

1. Create the source

Open Sources under Ingest in the sidebar and click New source in the top-right corner.

Sources list with a New source button in the top-right corner

The form has two sections, Source and Lead Quotas.

Name

Give the source a descriptive name. This is how the source appears in tables, filters, and dropdowns throughout the system. Something like “Partner Web Form” or “Leadz.com Feed” works well. Pick a name your team will recognize at a glance.

Lead category

Select the lead category this source will feed into. The category defines the base field schema, so every lead submitted through this source must conform to its required fields and types.

Source type

Pick one of the two cards.

Type	What it means
Internal	For leads you generate yourself. Not subject to subscription threshold limits. Leads are held in a “withheld” status if you hit your cap, rather than being rejected outright.
Vendor	For leads purchased from third parties. When your subscription threshold is reached, pings are automatically rejected so you don’t pay for leads you can’t distribute.

If you’re just getting started and generating your own leads, Internal is the right choice. Switch to Vendor when you start buying leads from outside sources.

Payout percentage

The percentage of the charged amount reported back to the source. Defaults to 100%. If you have a profit-sharing arrangement with a vendor (say, a 70/30 split), set this to 70. A $100 lead would then be reported to the vendor as $70.

Test mode

When enabled, the source enters a sandbox-like state. Zip codes 00001 through 00005 return deterministic test responses, and any other zip code is marked as test data and moved to Audit status. This lets an integrator test without polluting your production data. The switch is available for both internal and vendor sources. See test mode for what each zip returns.

Lead quotas (optional)

Under Lead Quotas, you can cap how much the source sends per day, week, or month, by Lead Count, Payout Value, or both. Leave a field blank for no limit. Once any limit is reached, new pings return “No match found” and posts are rejected until the period resets. Click Create source when you’re done.

2. Review the overview

Juiced takes you to the source’s Overview tab. This is your at-a-glance view, with stats for the selected timeframe, the source’s Status Responses, and a Details panel with the lead category, type, partners, test mode, and creation date.

Source overview with stats, Status Responses grouped into Success, Rejected, and Duplicate, and a Details panel

Status Responses shows how Juiced maps lead statuses to the three responses a source receives via the API.

Response	Default lead statuses
Success	Assigned Posted Marketplace Club
Rejected	Audit Unassigned Uncategorized
Duplicate	Duplicate

To customize the mapping, click Edit and drag status chips between the Success, Rejected, and Duplicate columns under Status Responses. Every lead status must belong to exactly one response, and Juiced won’t save until each one is placed. The More actions (⋯) menu in the header holds View API Spec, which opens a shareable link to this source’s API documentation (valid for 7 days), and Delete.

3. Grab API credentials

Click the Authentication tab. Juiced generates credentials automatically when a source is created, so no extra setup is needed.

Authentication tab with the Basic Auth API key and masked secret, plus the Bearer Token section with a New bearer token button

You’ll see two authentication options. Basic Auth shows your API Key and API Secret (masked by default, so click the eye icon to reveal it, or the copy icon to grab it without revealing). Use these as the username and password for HTTP Basic Authentication. Bearer Token is the alternative. Click New bearer token and confirm with Create token to generate a token for the Authorization header. The token appears once in a Token created banner, so copy it before you leave the page. Each new token expires the previous one in 24 hours.

Treat your API credentials like passwords. Bearer tokens can be replaced from this page, but the Basic Auth key and secret can’t be regenerated. If a bearer token is compromised, create a new one; the old token stops working 24 hours later.

4. Add source-level fields

Click the Fields tab. You’ll see two sections. Source Fields at the top is where you define fields specific to this source. It starts empty. Lead Category Fields at the bottom is a read-only reference showing the fields inherited from the source’s lead category. These are the base fields every source on this category shares.

Fields tab with an empty Source Fields table, a New field button, and the read-only Lead Category Fields table below

Why source-level fields?

Source-level fields let you capture data that only applies to a particular source, without cluttering the lead category schema that every other source shares. A vendor might send a referral_code or campaign_id that’s irrelevant to your other sources. They also let you override lead category fields. If you create a source field with the same title as a lead category field, the source’s configuration wins. This is useful when a specific source needs different validation rules or delivery settings for a standard field.

Creating a source field

Click New field to open the field dialog. It works just like adding fields to a lead category, with the same title rules, type dropdown, and switches.

Setting	What it controls
Title	The field identifier used in API submissions. Must start with a letter or underscore, and can only contain letters, numbers, and underscores.
Type	The data type and validation rule. See field types for the full list.
Required for post	Must be present when submitting a lead. Returns a `422` error if missing.
Required for ping	Must be present during the ping phase of ping-post.
Deliverable	Included in data sent to customers via the portal and webhooks.
Hidden from API spec	Won’t appear on the source’s public API specification page.
Description	An optional note about what the field holds.

If you select List of Values as the type, a Values input appears. Enter the allowed options separated by commas. Any submitted value not in this list will fail validation.

Click Create to save. Back in the table, the four switches can be flipped inline without reopening the dialog.

Overriding a lead category field

To override a lead category field, create a source field with the exact same title. For example, if the lead category has a phone field typed as Phone (US & CA) but this source only accepts US numbers, create a source field titled phone with the type Phone (US). Overriding source fields carry an Overrides badge in the Source Fields table, and the lead category field they replace is dimmed in the section below, so you can tell at a glance which fields are overrides.

5. Configure additional settings (optional)

The tabs hold a few more settings worth knowing about.

Pricing

The Pricing tab lists every lead type in the source’s category with two inputs.

Fixed Price is what the source is paid when a bidder matches, instead of its payout percentage of the winning bid.
Fallback Price lets an eligible marketplace or Club stage accept the lead when no bidder matches.

Each price saves when you leave the field, and the Behavior column describes the result. The More actions menu has Edit Payout to change the payout percentage, and Copy from Source when another source shares this category.

Pricing tab with Fixed Price and Fallback Price inputs for each lead type and a Behavior column

Fallback prices matter most for ping-post traffic. A marketplace stage only accepts a ping when the source has a fallback price for that lead type, and quotes that price in the ping response. A Club stage accepts pings at the fallback price, or at $0 without one, but passes when the lead type has a fixed price and no fallback. Leads posted directly, without a ping, can reach either stage without a fallback price.

Duplicate Checks

The Duplicate Checks tab lets you configure source-specific duplicate detection rules. These only apply to leads coming through this particular source, which is useful when different vendors have different tolerance for duplicates.

Payouts

If you can view analytics, the Payouts tab totals what you owe the source for a period, with a lead-by-lead breakdown. See source payouts.

What happens next

Once your source is created and configured, here’s where things stand.

API credentials are ready to use, so share the Basic Auth credentials or a bearer token with whoever is integrating
Lead validation enforces both the lead category fields and any source-level fields you added
Source-level fields override matching lead category fields for this source only, and other sources on the same category are unaffected
The API spec (from View API Spec in the More actions menu) reflects all fields, types, and requirements so integrators know exactly what to send

Ready to send your first lead? Head to Sending leads to Juiced.

Guides

Ingesting & Classifying Leads

Selling Leads

People

Quality & Validation

Events & Messaging

Observability

Account Management

Setting Up a Source and Its Attributes

Prerequisites

1. Create the source