Skip to main content
Distribution is the pipeline a lead travels through after it arrives. Ping-post, bidding, and the marketplace are individual pieces of machinery; distribution is how they’re strung together. You define the order of operations, and Juiced runs every lead through that sequence until it sells, expires, or hits a configured terminus.
Distribution is part of the Distribution Stages feature set. If the Distribution Stages resource and the Logs entry don’t appear in your tenant navigation, the feature hasn’t been enabled for your account yet. Reach out and we’ll turn it on.

​
Distribution stages

A stage is a single step in your pipeline. Each stage has a method that determines what it does, plus settings that control how it behaves. Stages are ordered, and leads move from the first enabled stage to the next until one accepts the lead or the sequence ends.

​
Stage methods

“Terminal” stages can accept the lead and end the flow. “Non-terminal” stages always pass through to the next stage.

​
Stage settings

Each stage can be configured with:
  • Bids enabled — Whether customer bids participate at this stage (applies to Highest Price).
  • Partners enabled — Whether partner offers participate. When enabled, you can filter the partner pool with an include-list or exclude-list.
  • Minimum price — A floor for partner offers. Offers below this amount are skipped.
  • Conditions — Rules that determine whether a given lead qualifies for this stage. A stage with conditions only runs when the lead matches.
  • Paused — Temporarily skip a stage without deleting it. Useful when you’re troubleshooting or rolling out changes gradually.

​
Ordering

Stages run top-to-bottom. Drag to reorder. The usual pattern is to start with the highest-value method (Highest Price with ping-post and top-tier partners), fall back to less profitable methods (Round Robin, secondary partners), and end with Marketplace as a catch-all for unsold leads.

​
Distribution attempts

Every time a lead enters a stage, Juiced records a distribution attempt. Each attempt has a status: Attempts are stored per flow, so a single lead can have many attempts across multiple stages.

​
Distribution flows and the log

A distribution flow is the record of a lead’s full journey—every stage it visited, every attempt, and the outcome. Flows are visible in the tenant panel under Entries → Logs. Each log entry opens into a timeline showing events in chronological order: Use the log to diagnose why a particular lead didn’t sell, or to audit the decisions made across a day’s volume.

​
Typical patterns

A few common pipeline shapes:
  • Ping-post first, marketplace fallback — Highest Price (with partner ping-post enabled) → Marketplace. Unsold leads cascade automatically.
  • Enrich then sell — Real Estate API → Highest Price → Marketplace. Property data is attached before the auction so conditions and pricing can use it.
  • Tiered partners — Highest Price (Tier 1 partners only) → Highest Price (Tier 2 partners only) → Marketplace. Each stage can have its own include-list.
Stages are cheap to add and reorder, so iterate on your pipeline as you learn what sells.

Configuring distribution stages

Build a pipeline of stages that route leads from arrival to assignment.

Reading distribution logs

Trace any lead end-to-end through the pipeline to answer “what happened?”.