Looking to manage your revenue setting? Here’s how the Campaign Configuration: Revenue Additional Settings can help you achieve the mission.
The Revenue Additional Settings tab allows you to manage additional revenue settings to optimize publisher earnings alongside existing rev-share settings for the campaign.
To customize the Revenue Additional Settings, go to the Client Management > Campaigns section, select the Campaign, and click the “Configure” button, then go to the “Revenue Additional Settings'' tab on the Campaign Setup page.
Here, you can enable additional revenue settings for both Cost Per Acquisition (CPA) and Ping Post Call scenarios.
Cost Per Acquisition (CPA) Settings
Ping Post Call Settings (LMS only)
Cost Per Acquisition (CPA) Settings
CPA (Cost Per Acquisition) settings allow for managing both publisher compensation and buyer charges, tracking revenue according to earnings from buyers, and managing lead statuses from a reporting perspective. The “Cost Per Acquisition (CPA) Settings” block contains the following options:
- Publisher payout based on the campaign price: When enabled, the publisher will be paid by Admin based on the Campaign price, in accordance with the publisher's rev-share. Meanwhile, buyers won't be charged upfront; they will only pay for the lead if it results in a purchase or contract signing. This may temporarily result in negative Admin revenue. Total Revenue will be tracked based on earnings received from buyers if the Revenue Postback feature is enabled. If the Revenue Postback feature is disabled, Total Revenue will not be available in reports since they do not reflect revenue that has not yet been acquired or earned.
- Track Call Duration (Call Logic only): Select the option for the system to start the call duration tracking:
- Buyer Response: Select this option for the system to start the call duration tracking from the Buyer response.
- Transfer to the Buyer: Select this option for the system to start the call duration tracking from the transfer to the Buyer.
- Revenue Postback: When enabled, Revenue Post Back allows buyers to pay for leads if they result in a purchase or contract signing, and allows admin/publishers to earn additional revenue. To configure this setting, fill in the following fields:
- API ID: The ID is generated automatically by the system and can be changed by the user.
- API Password: The API password is generated automatically by the system and can not be changed.
- Strategy On Duplicate Ping: This feature allows to enable or disable the ability to monetize the lead more than once.
- Select the “Ignore” strategy to have the system accept only the first revenue postback and ignore all following postbacks.
- Select the “Add Revenue” strategy to have the system accept all postbacks. The total revenue amount will be summarized, and the Buyer will pay for each next postback. The price may differ for every sale.
Examples:
- Tracking Strategy: The Tracking Strategy feature allows you to manage the process of lead tracking.
- Select the “Default” strategy to track leads that are sold both directly and through the Revenue Postback.
Note: This can cause double tracking of the leads in the Buyer’s tracking system - tracking will be triggered by the Campaign Accepted event. - Select the “Direct Sold Only” strategy to only track leads that are sold directly and ignore the Revenue Postback.
- Select the “PingBack Only” strategy to only track leads that are sold through the Revenue Postback and ignore leads that are sold directly.
- Select the “Default” strategy to track leads that are sold both directly and through the Revenue Postback.
- Revenue Strategy: The Revenue Strategy feature allows to enable or disable the publisher’s revenue in a postback process.
- Select the “Pay Publisher Income” strategy for the Publisher to receive revenue from the postbacks according to the “Rev-Share” settings.
- Select the “Ignore Publisher Income” strategy for the Publisher not to receive revenue from the postbacks.
- Revenue Strategy Override: Select the “Yes” option for the Buyer to set a strategy for each separate postback. Select the “No” option to disable the strategy override.
- Run Silence Campaign On Ping: This feature allows you to set a trigger for the Silent Campaign (Campaigns) to which the lead will be sent if the Revenue Postback feature is enabled.
Note: This feature is available on-demand only.
- Mark lead status as sold, if the campaign price is 0 (LMS only): This feature is applicable to campaigns with a minimum price of 0 and determines the lead status when it's posted to the buyer. When enabled, the lead will have a “Sold” status; when disabled, the lead will have a “Reject” status. Select one of the following options to enable it:
- Select “Default” to apply the Product settings the Campaign is assigned to.
- Select “Enabled” to enable the feature for this Campaign, regardless of the Product settings. Note: This option overrides the Product configuration.
- Select “Disabled” to disable the feature for this Campaign, regardless of the Product settings. Note: This option overrides the Product configuration.
Note: If the “Mark lead status as sold, if the campaign price is 0” feature is enabled, the feature “Mark buyer accept as “0” will be blocked, and vice versa.
You can perform revenue ping back using the PingBack Link. Enter the Lead ID value and Price value in the braces of the provided link.
Example:
The link provided in your system:
https://leads-instNUMBER-client.phonexa.com/api/transaction/?apiId=E1A230A5&apiPassword=1a01111eaea10ead101aea1e10101f&leadId={leadId}&earning={earning}
Example of the link you should use for Ping Back with the following parameters:
Lead ID: W_0EWLMJ
Price: 100
https://leads-instNUMBER-client.phonexa.com/api/transaction/?apiId=E1A230A5&apiPassword=1a01111eaea10ead101aea1e10101f&leadId={W_0EWLMJ}&earning={100}
To update earnings for multiple leads simultaneously, you can use a JSON Post. Enter the IDs’ of required leads and their earnings in the body of the request and perform the Bulk Revenue Postback.
Use the following link
https://leads-instNUMBER-client.phonexa.com/api/transaction/bulk
Request Example:
{
“apiId”: “AOE00AEA”,
“apiPassword”: “11e1a10000e1daa1e1e00eaff1eaa1",
“transactions”: [
{
“leadId”: “W_1EAEAE”,
“earning”: 10
},
{
“leadId”: “W_2EAEAE",
“earning”: 15
},
{
“leadId”: “W_3EAEAE”,
“earning”: 20,
“strategy”: “ADD”
}
]
}
Ping Post Call Settings (LMS only)
The Ping Post Call Settings are applicable exclusively to ping-post calls for bidding purposes. The “Ping Post Call Settings” block contains the following option:
- Mark buyer accept as "0": When enabled, this feature ensures that no revenue or payouts are recorded for leads with a “Sold” status, regardless of the campaign price. Select one of the following options to enable it:
- Select “Default” to apply the Product settings the Campaign is assigned to.
- Select “Enabled” to enable the feature for this Campaign, regardless of the Product settings. Note: This option overrides the Product configuration.
- Select “Disabled” to disable the feature for this Campaign, regardless of the Product settings. Note: This option overrides the Product configuration.
Note: If the “Mark buyer accept as “0” feature is enabled, the “Mark lead status as sold, if the campaign price is 0” feature will be blocked, and vice versa.
Click the “Save” button to confirm.