Skip to main content
All CollectionsLead Distribution & Routing
Routing Distribution: "Pingtree" Routing
Routing Distribution: "Pingtree" Routing

Learn about the"pingtree" routing distribution logic

Charlie Conner avatar
Written by Charlie Conner
Updated over 4 months ago

"Pingtree" Routing

Pingtree Routing is a specific routing type in which leads are posted to buyers in the priority order in which you set them in your distribution view.

Enabling

There can only be 1 method of routing logic in active in a campaign at a given time. You cannot have endpoints/buyers in form distribution routing AND Pingtree routing logic simultaneously

Enabling this and disabling any other routing logic in your campaign will consider this as active

Groups

In Pingtree Routing you can set different groups. Within these groups you can add in different buyer/endpoints which are active in your campaign. In many cases, there are different groups set related to the tier or minimum price you will accept for a given lead.

Group Wait times

In the "endpoint single" view where you modify a singular endpoint or advertiser, you can set a response time allocation. Setting this timeout value tells the system that IF the endpoint/buyer's server does not provide a response to Pingtree for a given lead in "X" amount of time, then Pingtree will move on to the next buyer and consider the lead unsold to the buyer that timed out.

Group wait times are similar however this is a global wait time assigned to an entire group. Pingtree's system will look at the individual response time allocation first followed by the group wait time allocation. If there are 10 endpoints/buyers in a single group, and your group wait time is 100 seconds, Pingtree will move onto the next group once it's reached that response time, regardless of how many buyers it's gone through in that group.

Async

Typically used more in Ping+Post routing logic, enabling the Async toggle will post lead data to all buyers set in the pingtree and sell to the first buyer who returns a successful response which also has met that particular endpoint's assigned minimum price value. If no minimum price is set, it will sell to the first successful response received.

Minimum Price (Not Required)

Minimum prices are set inside of the endpoint or advertiser single view. This value serves as a rule that defines the price that must be received in the buyer's server API response in order to consider whether or not the lead will sell.

Below is a representation of the flow in pingtree routing

Did this answer your question?