Dynamic Revenue

Follow

Dynamic revenue is the ability to use the response received back from your buyers remote system to determine what revenue should be assigned to a lead. 

Find this option under your delivery settings:

Image_2020-07-29_at_10.28.46_AM.png 

Response Type: String

Find revenue: Split By

Split by should be used when the remote system is returning the response in a string. 

EG -

accepted | 2020-07-29 09:00:00 | 2.50 | true

Split by string

This section is where you tell LeadByte how the response is broken up. In my example above the string is broken up by the "pipe" symbol. So you'd put | in this box.

Split by position

Now you're going to tell LeadByte where in the response the revenue is found. Using my example again, the revenue is found in the 3rd position (Revenue is 2.50. As a result, you would put 3 in this field.

Putting this all together, the dynamic revenue for my example would like this:

Image_2020-07-29_at_9.32.47_AM.png

 

Find Revenue: Match by Keyword

Does your buyer return their response in XML? If so, check out the below:

EG -

<?xml version="1.0" encoding="utf-8"?>
<PostResponse>
<Result>Accept</Result>
<CampaignID>123456</CampaignID>
<LeadID>D7B79F03-4971-45C0-A33E-64FF04E9C453</LeadID>
<Price>100.00</Price>
<RedirectURL>http://www.leadbyte.com/?lid=123ABC</RedirectURL>
</PostResponse>

In the above example, you'd use <Price>[revenue]</Price> to pull the revenue from their response. In essence, you'll be copying the price section and placing a tag where the actual revenue value is shown:

Image_2020-07-30_at_8.31.18_AM.png

 

Response Type: JSON

This option should be utilised when the buyers remote system returns their response in JSON.

EG - 

{
"Success":"True",
"Timestamp":"2020-07-29 09:00:00",
"Assigned_ID":"12345",
"Revenue":"5.00"
}

You'd need to tell LeadByte which field the revenue is found in. In my example this is would simply be Revenue:

Image_2020-07-29_at_10.02.32_AM.png

 

 Please feel free to raise a support ticket with any further questions or concerns.

Was this article helpful?
0 out of 0 found this helpful

Comments