Skip to main content
Sources are how leads get into the system. They represent where leads came from, usually a lead form on a website you control, but sometimes a vendor you’re buying leads from. Sources can be assigned to partners to organize them by business relationship. This helps you track which vendor or affiliate is responsible for which lead flows.
Sending leads from a form builder, funnel, ad platform, CRM or another lead platform? See Sending leads from other tools.

​
The sources list

Open Sources under Ingest in the sidebar to see every source in your workspace.
Sources list with Name, Type, Partners, Test Mode, Payout, and Return Rate (30d) columns, and a New source buttonSources list with Name, Type, Partners, Test Mode, Payout, and Return Rate (30d) columns, and a New source button
Each row shows the source’s name and lead category, its Type (Internal or Vendor), the Partners it belongs to, a Test badge when test mode is on, and its Payout percentage. If you can view analytics, you’ll also see Return Rate (30d). Search by name, or click Filters to narrow the list to one lead category.

​
Inside a source

Click a source to open it. The tabs across the top are Overview, Payouts (only if you can view analytics), Pricing, Authentication, Duplicate Checks, and Fields.
Source overview with Revenue, Payout, Leads, Pings, and Return Rate stats, a Status Responses board, and a Details panelSource overview with Revenue, Payout, Leads, Pings, and Return Rate stats, a Status Responses board, and a Details panel
The Overview tab shows three things.
  • Stats for the selected timeframe cover Revenue, Payout, Leads, Pings, and Return Rate, each compared with the previous period. You need analytics-view permission to see them.
  • Status Responses shows which lead statuses the source hears back as Success, Rejected, or Duplicate (see Status responses).
  • Details lists the lead category, type, partners, test mode, and when the source was created. A Quotas panel appears below it when the source has any lead quotas.
Click Edit to change the source’s settings. The More actions (⋯) menu holds View API Spec and Delete.

​
Authentication

When you create a source, an API key and API secret are generated automatically for HTTP Basic Authentication. You can also authenticate with a bearer token. Both live on the Authentication tab.
Source Authentication tab with the Basic Auth API key and masked API secret, and a Bearer Token table with a New bearer token buttonSource Authentication tab with the Basic Auth API key and masked API secret, and a Bearer Token table with a New bearer token button
  • Basic Auth shows the API Key and a masked API Secret you can reveal or copy. The key and secret can’t be regenerated.
  • Bearer Token lists every token with when it was created, last used, and when it expires. Click New bearer token to create one. The new token is shown once, in a Token created banner, so copy it right away. Creating a token expires the previous one in 24 hours, giving the integrator a window to swap it in.

​
Source types

Sources can be either internal or vendor. This setting affects several behaviors.

​
Ping responses

  • Internal sources get a more detailed ping response.
  • Vendor sources get a simplified response.
See the API Reference for specifics, or choose View API Spec from a source’s More actions menu to see its documentation. This opens a shareable link that shows the basic auth credentials for up to one week, after which the link expires.

​
Subscription threshold behavior

When you’ve reached your subscription threshold, the two types behave differently.
  • For internal sources, pings are still accepted. Leads are held in a “withheld” status and won’t be processed until capacity frees up.
  • For vendor sources, pings are automatically rejected so you don’t purchase leads you can’t distribute.
To avoid hitting your threshold entirely, consider enabling auto-upgrade to automatically move to the next plan tier when you reach your limit.

​
Payout percentage

If you’ve negotiated a profit-sharing arrangement with a vendor, use the payout percentage to adjust what’s reported to them. For example, if you split profits 50/50, set the payout percentage to 50%. A $100 lead will be reported to the vendor as $50. You can change it on the source’s edit form, or from Edit Payout in the More actions menu on the Pricing tab. Fixed and fallback prices override the percentage when they’re set.

​
Test mode

Any source, internal or vendor, can have test mode turned on so an integrator can test without affecting production data. When test mode is on, a few things change.
  • Pings and leads submitted through the source are marked as test data
  • Test data is hidden from normal views by default. Set the Test mode filter on Leads or Incoming logs to see it
  • Five reserved zip codes return deterministic responses, making it easy to verify different scenarios
  • Any other zip code is marked as test data and the lead is moved to Audit status (unless it’s a duplicate or can’t be categorized), so it won’t be distributed to customers

​
Testing with zip codes

When test mode is enabled, the system returns predictable responses based on the zip code submitted. See Test mode in the API reference for the full responses, including prices. This lets vendors test every outcome (successful distribution, duplicates, rejections, no-match scenarios, and marketplace routing) without needing real buyer coverage in those areas.
Test mode earns its keep with vendor sources, since someone outside your team is building the integration. Turn it off before go-live, or real leads will squeeze straight into Audit.

​
Lead quotas

Use Lead Quotas on a source’s create or edit form to stop accepting new pings and posts after the source reaches a limit. You can set daily, weekly, or monthly limits for both Lead Count and Payout Value; leave any field blank for no limit.
Source edit form with Name, Lead Category, Internal and Vendor source type cards, Payout Percentage, Test Mode, and the Lead Quotas sectionSource edit form with Name, Lead Category, Internal and Vendor source type cards, Payout Percentage, Test Mode, and the Lead Quotas section
Limits use totals so far, so the final lead can take the payout total over the limit. Once any limit is reached, new pings return “No match found” and posts are rejected without creating a lead. Limits reset each day, week, or month. Review these limits with the source before enabling them so an expected pause doesn’t arrive as a citrus-flavored surprise.

​
Status responses

When a source posts a lead, Juiced answers with one of three responses (Success, Rejected, or Duplicate). Which one depends on the status the lead ends up in. Here’s the default mapping. To change the mapping, open the source’s edit form and drag each status chip onto the response you want under Status Responses. Every status belongs to exactly one response. If a status isn’t placed yet, it shows in an Unassigned area and you’ll need to drop it on a response before you can save.

​
Source pricing

Beyond the payout percentage, you can set prices for each lead type the source sends. Open the Pricing tab.
Source Pricing tab listing each lead type with Fixed Price and Fallback Price inputs and a Behavior column describing the payoutSource Pricing tab listing each lead type with Fixed Price and Fallback Price inputs and a Behavior column describing the payout
The table lists every lead type in the source’s lead category. Each row has two inputs, and each saves as soon as you leave the field. The Behavior column spells out the result in plain language, such as “Pays 35% of the winning bid” and “No fallback configured.” Leads that get a Rejected or Duplicate status response are always priced at $0.00.
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.

​
Copying pricing from another source

If several sources on the same lead category share a pricing structure, choose Copy from Source in the More actions menu on the Pricing tab and pick the source to copy from. Fixed and fallback prices are copied; prices you’ve already set aren’t overwritten. The action only appears when another source shares this source’s lead category.

​
Payouts

The Payouts tab shows what you owe the source for a period (last month by default). It’s handy at the end of the month when a vendor asks for their check.
Source Payouts tab with Leads Received, Payout Owed, and Expected Revenue stats above a table of leads with received date, status, payout, and revenueSource Payouts tab with Leads Received, Payout Owed, and Expected Revenue stats above a table of leads with received date, status, payout, and revenue
  • Leads Received counts the leads the source sent in the period.
  • Payout Owed is what’s owed for accepted leads received in the period.
  • Expected Revenue is what customers were charged for those same leads.
Below the stats, each lead is listed with when it was received, its status, its payout, and its revenue. Pick a different period from the timeframe menu in the header. You need analytics-view permission to see this tab.

​
Source-level fields

You can define fields at the source level on the Fields tab. These fields are appended to the fields from the source’s lead category, letting you capture more precise information for specific sources.
Source Fields tab with an empty Source Fields table and a read-only Lead Category Fields table showing post, ping, deliverable, and hidden-from-spec settingsSource Fields tab with an empty Source Fields table and a read-only Lead Category Fields table showing post, ping, deliverable, and hidden-from-spec settings
If you create a source-level field with the same title as a field on the lead category, the source’s field overrides the lead category’s. Overriding fields carry an Overrides badge, and the lead category field they replace is dimmed in the read-only Lead Category Fields table below.

​
Source-level duplicate checks

Duplicate checks can also be configured on a source’s Duplicate Checks tab. A check set here only applies to leads coming through that source, just like source-level fields only apply to that source.
Source Duplicate Checks tab with an empty table and a New duplicate check buttonSource Duplicate Checks tab with an empty table and a New duplicate check button

​
Source performance

The source list includes a Return Rate (30d) column, and each source overview includes a Return Rate stat for the selected timeframe. This helps you spot traffic that is being returned without manually comparing assigned and returned lead lists. Return rate is the share of customer deliveries from the source that are currently returned. Each customer delivery counts separately, so a lead delivered to two customers counts as two deliveries. Test leads, partner deliveries, and pending reservations are not included. You need analytics-view permission to see return-rate reporting.

​
Deleting sources

To delete a source, choose Delete from the More actions menu on its overview. Once it’s deleted, Juiced stops accepting leads from it. Deleted sources are soft-deleted rather than permanently removed. Leads, posts, and pings that came through the source keep pointing at it, so your history still shows where each lead came from.

Setting up a source and its attributes

Create a source, configure its settings, and add source-level fields.

Sending leads to Juiced

Submit your first lead through the source API.