TLD CRM BoostPatch 10.4.6

|

Vendor Ping API – Ping Concurrency Limits

We’ve added a new parameter to the Vendor Ping API: max=x, and mas=x

These values Define how many ACCEPTED Pings you want to accept within an X Time Frame Window.

So for example if you have MAX set to 1 and MAS set to 5

If a Vendor Sends 5 Pings within a 5 Second Window, Regardless if they send the calls or not, they will get 1 acceptance and 4 rejections even within the same second. This should help some Vendors with contention issues, however for those using RTB this may not be useful since acceptance of a ping does not guarantee a call. This also currently does not work across vendors so multi vendor pings during the same second will still have the same concurrency issues as this is per vendor.

The following is an example of what a rejection looks like:

 

{
“ready”: 0,
“active”: 0,
“reason”: “MAX”,
“cause”: “EXCEEDED”,
“details”: {
“max”: 1,
“sec”: 5,
“count”: 4,
“rejected”: 3
}
}

Notice the Details show a Max of 1 Configured within 5 seconds, a count of 4, which is the amount of pings total that would have been accepted and 3 of them were rejected. This was the 4th ping in the same 5 second window from the first acceptance.

These Settings only work in the Vendor Ping, not the Public Dialer Ready Ping.