What Is a Ping Tree?

The core idea: a waterfall of buyers

Picture a prospect filling out a form on a landing page for a solar inquiry. In that instant, a lead is created — and the interesting question is: which of your buyers should get it? If you only have a single buyer, the answer is trivial. But the moment several buyers compete for the same lead, you need a clear, automated rule to decide. That is exactly what a ping tree does.

At its core, a ping tree is a sorted list of buyers combined with waterfall logic. The lead is offered first to the buyer at the top. If that buyer accepts, the lead is sold and the process ends. If they decline or don't respond in time, the request automatically falls one tier down to the next buyer. This pass-down repeats until a buyer accepts or the list runs out. The word "waterfall" captures it well: the lead flows downward until it's caught.

Speed matters. A good ping tree runs in milliseconds to a few seconds, because a fresh lead loses value with every passing minute. Nobody wants to be contacted when they're already fielding five other offers. That's why the ordering decision isn't only a commercial discipline — it's a technical one too.

Structure: levels and tiers

A ping tree is rarely a flat list. In practice it's organized into levels (also called tiers). Each tier groups one or more sets of buyers that are considered at the same point in the waterfall. The logic works through the tiers strictly from top to bottom.

• Tier 1 — premium buyers: buyers who pay the highest price, need exclusive leads, or have contractual priority. They are always asked first.
• Tier 2 — standard buyers: buyers with a solid but lower bid. They get their turn when Tier 1 declines or has no capacity.
• Tier 3 — catch-all: buyers who also take overflow volume, often at a lower price. They make sure almost no lead goes unsold.

Within a single tier, several buyers can sit side by side. In that case you need an additional rule to set the order inside the tier — such as lead bidding, where the highest bid wins, or round-robin, which spreads leads fairly in rotation. The tier structure and the sorting within each tier are therefore two separate levers that together determine how the tree behaves.

Who gets asked first? The three core criteria

The order in a ping tree is no accident. Three factors typically shape it — alone or in combination:

Priority

Some buyers simply get precedence, either because it's contractually agreed or because they're strategically important. A long-standing high-volume buyer can sit at the top even if someone else would briefly pay more. Priority is the manual, commercial lever you use to deliberately steer the tree.

Bid

The price a buyer pays per lead is often the strongest sorting criterion. Whoever bids more moves up. In dynamic models, buyers even submit a bid per inquiry — that's called real-time bidding. This way every lead automatically pays the market price, and you, the distributor, maximize revenue. More on this in the lead bidding entry.

Capacity

A buyer can offer the highest price and still get skipped — namely when they've hit their daily cap or report no available capacity. Capacity rules prevent a buyer from being flooded with leads they can't work. They protect both the buyer and the quality of the distribution. A well-maintained ping tree checks capacity in real time before offering a lead.

In reality, these three criteria work together. A typical rule might read: "Sort by tier, then by bid within the tier, and skip any buyer without free capacity." The result is an order that is transparent, fair, and revenue-strong all at once.

How a lead moves through the tiers

The actual flow can be walked through step by step. As soon as a lead arrives, here's what happens:

• The system sorts the eligible buyers into tiers by priority, bid, and capacity.
• The lead is offered to the first buyer in Tier 1 — as a "ping," a short inquiry with anonymized key details.
• The buyer has a tight window to accept. If they accept, they receive the full record (the "post") and the tree stops.
• If they decline or don't respond, the request moves to the next buyer in the same tier.
• If the entire tier is exhausted without anyone accepting, the lead drops to the next tier — and the game starts over.
• If no one accepts in the end, the lead stays unsold or moves into a catch-all tier at a minimum price.

This ping-and-post mechanism is closely related to the ping post method — the ping tree is essentially the framework that determines the order in which the individual ping post requests are fired. The two terms belong together: ping post describes the two-step query-and-accept per buyer, while the ping tree describes the overarching waterfall order across all buyers.

How it works with ping post, bidding, and pre-ping

A ping tree rarely stands alone. It's the conductor that brings several mechanisms together:

• With ping post: every single step in the tree is technically a ping post request. The tree sets the order; ping post governs the question-and-answer exchange per buyer.
• With lead bidding: within a tier, the bid often decides the position. Dynamic bidding makes the tree revenue-optimized, because the order is calculated live based on the current market price.
• With pre-ping: before a lead even enters the tree, a pre-ping can check whether it's a duplicate or violates quality criteria. That way only clean leads enter the waterfall — saving requests and protecting buyer trust.
• With round-robin: when fairness matters more than revenue maximization, a tier can distribute via round-robin so that all buyers receive an equal number of leads in rotation.

These building blocks are part of a bigger picture. If you want to understand the whole system, read the overview article on lead distribution — it explains how the ping tree, distribution rules, and billing all fit together.

What matters in maintenance

A ping tree is not "set it and forget it." Buyers change their bids, capacity fluctuates seasonally, and new buyers come on board. A capable tree can therefore be tuned continuously — ideally with transparent logs that show which lead went to which buyer and why. That traceability matters not only for billing, but also for spotting bottlenecks: if a Tier 1 buyer constantly declines, it costs valuable seconds and drags down the acceptance rate. Lead distribution software like Leadfy models trees like these — including order, capacity limits, and a real-time log — without you having to program the logic yourself.

Related terms

Frequently asked questions

What is the difference between a ping tree and ping post?

Ping post describes the two-step process with a single buyer: first the short inquiry (the ping) with anonymized data, then, after acceptance, the handover of the full record (the post). A ping tree is the overarching order that determines the sequence in which multiple buyers are queried via ping post. The tree is the framework; ping post is the mechanism at each step.

How is the order in a ping tree determined?

It's usually a combination of priority, bid, and capacity. Buyers are first sorted into tiers, then within a tier typically by bid or via round-robin. Any buyer reporting no free capacity is skipped. The result is a list that's worked through from top to bottom.

What happens if no buyer accepts the lead?

If the lead runs through every tier without anyone accepting, it either stays unsold or lands in a catch-all tier at a minimum price. That's why many distributors build a final tier with buyers who also take overflow volume, so as few leads as possible go to waste.

How fast does a ping tree run?

A well-configured ping tree works in milliseconds to a few seconds. Speed is critical because a fresh lead quickly loses value and the prospect wants to be contacted promptly. Each step gets only a tight window before the request moves on.

Can a ping tree work with dynamic bids?

Yes. With real-time bidding, buyers submit a bid for each individual inquiry, and the tree sorts the order live by the highest current bid. This way every lead pays the prevailing market price and distributor revenue is maximized. Statically stored fixed bids are also possible.

Who is a ping tree worth it for?

A ping tree is worth it as soon as multiple buyers compete for the same leads and you want to automate distribution. With only one buyer, it's unnecessary. But once you want to optimize revenue, account for capacity, and model fair or prioritized orderings, it's the central tool of lead distribution.