A Buyer Gets Fewer Calls Than Expected, or None
BuyersWhen a buyer that normally takes plenty of calls gets few or none, or wasn't considered for a call you expected it to take, the cause is usually in the buyer's own settings or in another buyer winning the call. This article walks through the causes, most common first, and where to see each one in the call's log and your settings.
The Buyer Was Closed by Its Business Hours
What you see: the buyer takes calls at some times of day and none at others, or the call's log lists it among buyers skipped as closed.
Where to check: open the call and read its log. A buyer outside its business hours is listed as skipped because it is closed. Then check the buyer's business hours and their time zone.
The fix: widen the buyer's business hours, or correct their time zone, to match when the buyer takes calls.
Example: a buyer takes calls from 9am to 5pm in its own time zone, but its hours were saved in a time zone three hours behind. Calls before noon in the buyer's zone are skipped as closed.
Bids Under the Buyer's Bid Min
What you see: the buyer is pinged, but the call's log says ping/post is rejecting the buyer because its bid is less than Min Bid.
Where to check: on the buyer's Conversion Settings, in the conversion criteria, Bid Min is the lowest bid the buyer may return for the current time frame. The call's log names the same setting Min Bid and shows the bid the buyer returned.
The fix: lower Bid Min, or ask the buyer whether its bids changed.
Example: Bid Min is 20, and the buyer starts returning bids of 15 after changing its own pricing. Every ping is rejected, and the buyer gets no calls.
The Buyer's Platform Rejected the Ping
What you see: the buyer is pinged, but its reply says it can't take the call, so another buyer gets it or none does.
Where to check: the call's log shows each ping and whether the buyer's reply was accepted. The buyer's reply shows on the call's Webhook Logs tab, which holds the request Trackdrive sent and the reply the buyer's platform returned.
The fix: read the reply. A missing field, a filter on the buyer's side, or the buyer's own capacity is a question for the buyer; a field Trackdrive sent wrong is fixed in the buyer's conversion settings.
Example: the buyer's platform replies that the caller's zip code is required, and the ping didn't send it. Adding the zip code to the ping lets the buyer bid again.
Prematch Search Is Turned Off for the Buyer
What you see: the buyer gets inbound calls but no calls from the Power Dialer, or the dialer never calls leads that only this buyer matches.
Where to check: on the buyer's page, Use With Prematch Search? decides whether the dialer counts the buyer as a match when it looks for leads to dial.
The fix: turn on Use With Prematch Search? for a buyer the dialer should call leads for.
Example: a buyer takes inbound calls all day but never a dialer call, and Use With Prematch Search? is off on its page. Turning it on lets the dialer count the buyer as a match for the leads it dials.
A Higher Priority or Higher Paying Buyer Won the Call
What you see: the buyer was eligible, but another buyer took the call, and on a quiet day the buyer gets nothing.
Where to check: the call's log lists the buyers in the order they were considered. Compare the buyers' tiers and weights, and for buyers that route by Bid Price, their bids. "How Buyers Are Selected for a Call" explains the order.
The fix: change the buyer's tier or weight, or its route-by setting, if it should be considered sooner. When volume is low, a buyer lower in the order gets fewer calls even when its settings are right.
Example: two buyers share a tier, and one bids more on every call. On a day with few calls, the higher bidder takes every one.
When to Contact Support
If none of these explains the calls, contact Trackdrive support with a call's id and the time of the call the buyer should have taken.