Real Time Action - Ping Post

Ping post is a real-time process in which a lead seller will send (PING) partial lead information to a pool of buyers. The buyers analyze the partial lead information and determine a bid price they are willing to pay for the complete lead information. The buyers submit their bid price to the seller, who determines the winner of the lead, and then sends (post) the rest of the lead information to the winning buyer.


Advantages of Ping Post

With the ever changing privacy and compliance environment centered around online lead generation, keeping and transferring consumer information in a safe, secure, and responsible manner has become a major focus. The Ping Post process integrates another layer of privacy for the consumer, by allowing the seller to submit only partial lead information on the initial ping to prospective buyers, giving them the information they need to make a buying decision, all without actually passing consumer personally identifiable information.

  • For the consumer ping post protects their personally identifiable information from multiple possible buyers.
  • For the lead seller ping post helps maximize the revenue potential that each lead can generate through the dynamic bidding process. It also prevents companies from seeing a lead's full contact information, responding that they do not want the record, but contacting it anyway.
  • For the lead buyer ping post grants increased flexibility in determining what lead details are required to conduct business and at what price points.

You can use PING/POST as an action to any of your buyers. There are 2 use cases for this feature:

  1. your buyer requires you to PING him with partial data before POSTing the full data
  2. you are selling to a marketplace (like PX)


Ping Post Configuration

Selecting a Marketplace

We currently support 2 types of PING/POST marketplaces:
  1. Generic PING/POST: use this if you are using any custom solutions or marketplaces
  2. PX shared: if you are using PX (https://www.px.com/) to sell your leads, we integrated with their "Exclusive" posting method.

Response type

This is the response type that your PING and POST will return. This should be specified on your buyer's API documentation. Lead Prosper supports the following 3 types: JSON, XML or Text. 
Choosing the right response type will allow you to setup more accurate response parsing and advanced features. For example, if the response is a JSON or XML document, you can enable our "dynamic price" option. If unsure of your response type, select Text.
Example JSON document:
Example XML document:

Dynamic Price

This feature is only available for JSON and XML response type formats. This allows you to:
  1. only send the POST request if it meets certain criteria (ex: if the PING returned a price greater than a specified amount
  2. have more accurate analytics based on the price. We will use the response price from the POST or PING request when dealing with analytics for this buyer.

PING and POST

Both the PING and the POST section will require the following configuration items:
  1. URL: the URL where Lead Prosper will send the PING request
  2. Method: method used when sending the request. We recommend POST over GET if available by your buyer
  3. Payload type: this will define in which format we will send the request body. There are 3 types: form, JSON, XML
  4. Payload: this is where you must enter the body that we will send to your buyer. This has to match exactly with your buyer's API specifications. 
    1. On top of the editor, you will see all the available fields and their short-codes.  
    2. The editor will visually display your body based on the selected payload type. 
    3. In the POST body editor, you can use a special short-code that will reference any value from the PING response. That short-code is {{ping_response:KEY}}, where KEY has to match the format described in this document.
    4. Please check the numbered sidebar in the editor and make sure there are no errors, as shown:
  5. Custom headers: in some cases, your buyers will require special headers, like an API key or username and passwords. 
    1. Headers can be added by specifying the Key and the Value of your headers. 
      1. You can add as many as you need. 
    2. Some headers don't need to be added, as Lead Prosper automatically adds them. 
      1. Content-Type
      2. Content-Length
      3. Host
      4. Server 
    3. Please consult with your buyer API documentation for more info.
  6. Response mapping: in order for Lead Prosper to know if a lead was accepted, duplicated or rejected by your buyers, you have to correctly define the ACCEPTED and DUPLICATED response values returned by your buyer.
    1. For JSON/XML responses, please refer to this document.
    2. For text responses, enter the relevant text that is returned in the response that will let lead prosper know if the buyer accepted or flagged the lead as duplicated.
    3. After parsing the response from your buyer, if Lead Prosper can't flag the request as either accepted or duplicated, it will flag it as error.
  7. Price key: if dynamic pricing option is enabled, setting this key will allow you to define extra filtering rules to send or not the POST request. 
    1. At least the POST or the PING price key is needed. The order in which lead prosper looks for the price is: POST, PING
Note: when using the PX marketplace, you only need to configure the payload body, as everything else is pre-configured.

Still need help? Contact Us Contact Us