Phonexa Ping Post Buyer Setup

A step by step tutorial on setting up your Phonexa Ping Post Buyer. To watch a tutorial on this topic click here

To begin, you’ll need a copy of your buyer’s API specs. For this example we will be using the sample Phonexa API specs seen below

You’ll begin by copying the Ping URL and pasting it into the buyer setup of your Lead Prosper campaign. The request method will be POST. We’ll use JSON as the payload type for this example

You’ll then build your payload using the fields that are required on the Ping. Fields are case-sensitive, so we recommend always copying and pasting the field names to avoid any potential typos. Begin with the field testMode and set the value equal to 1. Next are the apiId and apiPassword. These are static values and will be provided in your specs by Phonexa

Complete your Ping payload with the rest of the required fields. When your payload is complete it will resemble the one seen below

The header Content_Type is automatically filled out for you when you select the payload type. For the response mapping the condition will be key equal with, the key will be status, and the value will be continue  

If your buyer returns the real time price you can choose to have Lead Prosper track it when storing analytics. Toggle the Real time price option to ON and enter price as the real time price key. The SEND POST IF section is useful if you only want to sell the lead to the buyer if it is greater than a certain amount

Next is the Post set up. Copy and paste the Post URL and select the request method and payload type

You’ll then build out your Post payload. The field promise will be a value returned on each Ping. To grab this value enter the field promise and enter {{lp_ping_response:promise}} as the campaign field shortcode

You’ll notice that most fields are not required on the Post here. It’s best to reach out to your buyer to confirm what data they want passed on the Post, to ensure that you are sending all of the information that they require

Continue building out your Post payload. It will resemble the one seen below when complete

Once again, the header Content-Type is automatically filled out for you when you select the payload type above. For the response mapping for an Accepted lead, the Condition will be key equal with, the key will be status_text, and the value will be sold. The response mapping for a duplicated lead is now filled out for you

Since the real time price was set on the Ping, there’s no need to set it on the Post. 

That’s all there is to a Phonexa Ping Post Buyer set up! If you have any questions, please use the support button or email us at 

Still need help? Contact Us Contact Us