Each target has a Routing step with three settings that control how it takes calls, plus two campaign-level settings that bound failover.
On the target
- Concurrency cap: the most calls this target takes at the same time. Leave blank for no limit. When a target is at its cap, it is skipped and the call goes to the next buyer.
- Ring timeout (s): how long the buyer's phone rings before the platform gives up and tries someone else. The default is 25 seconds and the minimum is 5.
- Failover eligible: when ticked, this target can be used as a backup after another buyer fails to answer. Untick it for a buyer who should only get first-choice calls.
For an RTB target, Timeout (ms) on the Integration step is separate: it is how long the platform waits for the buyer's bid.
On the campaign
- Auction deadline (ms): the longest the platform waits for bids, up to 5000 ms.
- Failover budget (s): how long after a call arrives the platform may keep trying more buyers.
What happens when a buyer does not pick up
If a buyer is busy, does not answer, or errors, the platform tries the next ranked buyer, provided it is failover eligible and the failover budget has not run out. If the caller hangs up while it rings, no failover happens. Each buyer dialed counts as a dial-out for billing. See Charges and rates.
Automatic pause
If a target fails several dials in a row, it is paused automatically so callers are not sent to a dead line. Open Targets and click Unpause once the problem is fixed.
Hours
Campaigns can be limited to set hours. Outside them, publishers are told the campaign is outside its hours and no buyer is pinged. If you need hours set on a campaign, ask your platform admin.
Related
- Routing and the ping tree
- Dial and bid insights to see answer rates per target
- Why a buyer didn't get pinged
Still stuck?
Ask the support chat inside your account, or send us a request.