When would it be used?
It's common in specific niches / industries and mainly in the USA.  Most direct Buyers that welcome PingPost would be using their own CRM or a system like LeadByte. It is also common with aggregators that "market-place" their lead trading.

Why would I use PingPost?
As a Lead Seller, you not only want to maximise the amount of revenue per lead but also ensure that Personal Identifiable Information (PII) is exposed as little as possible before selling the lead.  The "Ping" element enables you to send partial data to the Buyer for them to make a decision as to whether they want the lead or not.  If they want the lead, they would make an offer / bid i.e. £15.  If you are willing to sell the lead for £15 then you can "Post" the full data to them.

How do I set up PingPost in LeadByte?
To set up PingPost you will first need the Buyers API guide, which outlines what URL to Ping and what data to include in the ping.  It will also contain the Post URL and what data to Post. Once you have the docs, you can go about setting up the PingPost delivery on your account as below.

Step 1
Create a New Delivery and Select PingPost

Step 2
Create your Ping request.  This is where you typically send partial data to your Buyer.

 

Step 3

Set your success requirements from the ping request.  

In the above example LeadByte is looking for a response where Success is True and the Cost field to be over 10.

EG 1 - 

{
"Success": true,
"Cost": 15
}

The above example buyer response would result in the Ping being marked as successful AND the Post being sent.

EG 2 -

{ 
"Success": true,
"Cost": 9
}

The above example buyer response would result in the Ping being marked as successful but the Post would NOT be sent.

EG 3 - 

{
"Success": false,
"Cost": 0
}

The above example buyer response would result in the Ping being marked as Unsuccessful. The Post is never fired if the Ping is marked as unsuccessful.

Step 4
Create your Post request and set what the success response should be.  It is common with Ping Post that you would pass into the Post request a unique Ping value i.e. PingID.  To extract values from the ping response you would use this format: {$ping.INSERT}.  You would replace INSERT with the field you want to capture.

JSON Response example below

This is an example Ping Response.  We want to post the PingID value in the Post Request.

 

{
"Status":"accept",
"PingID":"328487327432-1",
"Price":"10"
}

This is an example of the Post Request using the PingID value.

{
"fn":"[firstname]",
"ln":"[lastname]",
"ph":"[phone1]",
"pingID": "{$ping.PingID}"
}

XML Response example below

This is an example Ping Response.  We want to post the ping_id value in the Post Request.

 

<response>
<result>success</result>
<ping_id>GLV1KRUSSD</ping_id>
<price>0.01</price>
<msg>Ping Accepted</msg>
</response>

This is an example of a XML Post Request using the ping_id value.

<?xml version="1.0" encoding="UTF-8"?>
<lead>
<fn>[firstname]</fn>
<ln>[lastname]</ln>
<ping>{$ping.response.ping_id}</ping>
</lead>

The Ping response type must be set to either JSON or XML in order for you to pass the ping value into the POST using the methods above.

Exporting Ping or Post delivery responses.

If you go to Delivery -> Lead Delivery Logs and make sure you tick 'Raw Responses' when searching for your campaigns/deliveries, you can view both the Ping and Post API responses.

Scrolling down to the bottom of the page you can download the responses in XLS or CSV format.