LeadByte now supports Ping Post Exchange and this article will show you how to use the feature.

Ping Post Exchange empowers you to provide your supplier real-time bids for their leads before they send the entire lead information.

Our current version of Ping Post Exchange only returns the highest bidder on a ping.

Campaign Setup

Ensure you have 2 or more deliveries active against your chosen campaign and that your Advanced Distribution "Delivery Method" is set to Auction.

Check the "Enabled Exchange" tickbox and you'll be able to begin using our exchange functionality!

 

The "Bid Margin" is the percentage "clip" you take from the Buyers bid before passing it through to your Supplier as the amended bid.

Using the above example, I have set a Global bid margin of 15%. So any delivery I add to this setup will automatically inherit this 15% bid margin, however, I can edit this on a per-delivery basis if required.

If the bid returned by my Buyer was £100, my bid margin would be £15 and the bid I show to my Supplier would be £85.

 

Try all buyers until the bid-breakeven point will attempt to sell your lead up to the point of making a loss if your initial buyer rejects the lead.

Using the above example, let's assume Buyer 1 returns a bid of £80. 

If Buyer 1 rejects the lead, I can continue to try and sell my lead until I reach a bid price of £68.

As a result, I can also try EVO1 before I reach my breakeven point. The matrix below helps display this.

 

Now you have the "Enable Exchange" tickbox checked, you'll also see a ping required column on your campaign field.

Set any required fields for your pings here.

Finally, ensure you have Live Buyer Responses enabled in your campaign's advanced settings.

Ping

To submit a ping, ensure your REST API key has the "ping" permission selected (here)

Submit your ping requests in the below format - 

	[POST] https://[YOURDOMAIN].leadbyte.com/restapi/v1.3/leads/ping
	{
		"campid": "MY-CAMPAIGN",
		"sid": "SID1",
		"towncity": "Farndon",
		"county": "Cheshire",
		"postcode": "CH4 8PH"
	}
	
	Headers:
	X_KEY: [YOUR API KEY]

 

Success Response - 

{
"status": "Approved",
"pingId": 98765,
"code": 1,
"deliveries": [
{
"payout": "68.00",
"bidId": 12345
}
]
}

 

Ensure you include all "ping required" fields when submitting the test.

You can also include a callback URL in your ping if required.

Post

The Post will be a JSON-bodied lead submission you're used to but with 2 additional fields - 

• pingId
• bidId

The Post MUST include the BidID and PingID and MUST be submitted to the same campaign as your ping.

Once the PingID is matched with a Post, it cannot be used again.

Example Request with BidID and PingID:

        [POST] https://[YOURDOMAIN].leadbyte.com/restapi/v1.3/leads
        {
                 "campid": "MY-CAMPAIGN",
                 "sid": "SID01",
                 "towncity": "Farndon",
                 "county": "Cheshire",
                 "postcode": "CH4 8PH",
                 "bidId": "12345",
                 "pingId": "98765"
         }

         Headers:
         X_KEY: [YOUR API KEY]

 

Lead Screen Changes and Reporting

To find valid ping requests, check the Leads Tab under the "Search Pings" subsection.

To find invalid ping requests, check the Leads Tab under the "System Rejections" subsection.

To find Pings or Posts (valid leads attached to a PingID) ensure the method is set correctly. 

Pings are not currently being reported on, only when a Post is created will it be marked on your reports.

 

As always, raise a support ticket if you have any questions.

This is an ever-evolving feature, so if you spot any improvements please do inform us.