Call routing with tiers, filters, caps and failover
You decide which buyer gets each call. A campaign's ping tree ranks your buyers, filters decide which buyers are offered a call, and caps keep each buyer inside what they agreed to take.
A ping tree you control
Add targets to a campaign's ping tree and give each a tier and a weight. Lower tiers are tried first; inside a tier the highest bid wins, then the higher weight, then the faster reply. Static targets with a fixed price take part alongside live bidders.
- Give a direct buyer first look in tier 1 and keep a backup in tier 2
- Bids that leave no margin after the publisher payout are dropped automatically
- If the winner does not answer, the next eligible buyer is tried
| Target | Tier | Weight | Bid |
|---|---|---|---|
| Harbor Health (RTB) | 1 | 3 | $44.00 |
| Medway Direct (RTB) | 1 | 1 | $39.50 |
| Blue Oak Benefits (static) | 2 | 1 | $30.00 |
Filters on anything the call carries
Filters decide which calls a target is offered, without splitting your campaign. Check the state, zip, area code, caller number, publisher, publisher company, source, campaign, or any tag the publisher sends on the ping, such as a sub ID or age.
- Compare with is any of, is none of, starts with, contains, a pattern, or greater/less than
- Combine rows with OR inside a group and groups with AND
- Keep long zip or area-code lists in one shared list that every target can use
- Choose what happens when a call has no value for a field
Not offered this call: State (NY) is not any of GA, FL, TX
Caps, duplicates and failover
Each target has a ring timeout, a limit on calls at once, and hourly, daily and monthly caps. Campaigns add a daily cap and a duplicate window, so a repeat caller is not sold twice. Failover is bounded, so a call never rings through an endless chain of buyers.
- Ring timeout and concurrency limit per target
- Hourly, daily and monthly caps, by calls or by spend
- Duplicate caller windows per campaign and per buyer
- Mark which targets are eligible for failover