Jangl Ping Post Buyer Setup

In this support document we'll walk you through the process of setting up a Jangl Ping Post buyer. To watch a tutorial on this topic click here

We’ll be using these sample Jangl API specs for this example

You’ll begin by copying and pasting the TESTING PING URL into your buyer setup. You will replace this with the PRODUCTION PING URL later after successfully testing your campaign. The request method will be POST and we’ll use JSON as the Payload type for this example

Next, you’ll build out the Ping payload with all fields that are marked required in the Meta, Contact, and Data Variables sections of your API specs

As you can see from our example payload, Meta, Contact, and Data will be objects, and you’ll then add the required fields nested within them. Once your payload is complete it will resemble the one seen below

For Headers, Content_Type will automatically be filled out for you when you select the payload type. This buyer setup also requires an Accept Header and an Authorization Token. For the Accept Header, the key will be Accept and the value will be application/json. For the Authorization Header, Authorization will be the key and the token will be the word Token followed by the token given to you by your API specs

For the response mapping for an Accepted lead, the Condition will be key equal with, the key will be status, and the value will be success

Next, Toggle the Real Time Price section to ON and enter price as the real time price key

For the Post configuration, begin by copying and pasting the TESTING Post URL. Select Post as the Request Method and JSON as the payload type

The Authorization code will be a unique value returned with each PING. To grab this value enter auth_code as a field and {{lp_ping_response:authcode}} as the campaign field shortcode

You’ll then complete your Post payload. Since the specs do not dictate which fields are required on the Post, it's best to send whatever data you have and confirm with your buyer that they are receiving all of the data that they need. Once your payload is complete it will resemble the one seen above.

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, and the value will be success. The response mapping for a duplicated lead is automatically 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 for a Jangl Ping Post buyer set up. As always if you have any questions please use the support button or send us an email at support@leadprosper.io