The Revenue Additional Settings tab allows you to manage additional revenue settings. Here you can enable the CPF model, the “Mark buyer accept as 0” feature, and set up the Revenue Ping Back feature.

To customize the Revenue Ping Back, go to the Client Management > Campaigns section, choose the Campaign, and click the “Configure” button. Select the “Revenue Additional Settings'' tab on the Campaign Setup page.

The “Revenue Additional Settings” block contains the following information:

  • CPF: Enable the CPF feature to track revenue from buyers that pay on a "Cost per Funded" model. When enabled, the publisher will be paid according to the campaign price, and "Total Revenue" will be tracked according to earnings received from buyers by the "Revenue Ping Back".

  • Mark buyer accept as "0": Select "Default" to apply the product settings to the assigned campaign. Select "Enabled" to activate the feature for this campaign, regardless of the product settings. Select "Disabled" to disable the feature for this campaign, regardless of the product settings.

  • Allow Ping Back API: Select the "Enabled" status to activate the "Revenue Ping Back" feature. Once enabled, it allows you to once again ping the leads that were not sold through the campaign and get extra revenue.

  • Mark lead status as sold, if the campaign price is 0: Reflects the lead status as “Sold” if a lead was sold to a campaign with a min price set to “0(Default, Enabled, Disabled).

To configure the feature, fill in the following fields:

  • API ID: is generated automatically but can also be manually updated.

  • API Password: has generated automatically and can’t be edited.

  • The Strategy on Duplicate Ping: option allows you to enable or disable the ability to monetize the lead more than once. You can select one of the following options:

    • Select the “Ignore” option for the system to accept only the first revenue ping. The following pings will be ignored.

    • Select the “Add revenue” option for the system to accept all pings. The total revenue amount will be added up, and the buyer will be charged for every following ping-back. The publisher will be paid according to the Revenue Strategy settings. The price can differ for every ping.

Examples:

  • Tracking Strategy: feature allows you to manage the process of lead tracking for a Buyer.

    • Select the “Default” strategy to track leads that are sold both directly and through the Revenue Ping Back. Please note that this can cause double-tracking of the leads in the Buyer’s tracking system - tracking will be triggered by the Campaign Accepted event and the Lead Sold event.

    • Select the “Direct Sold Only” strategy to only track leads that are sold directly and ignore the Revenue Ping Back.

    • Select the “Ping Back Only” strategy to only track leads sold through the Revenue Ping Back and ignore leads that are sold directly.

  • Revenue Strategy: allows to enable or disable publisher’s payouts in a Ping Back process.

    • Ignore Publisher Income: the publisher is not paid for the ping-back.

    • Pay Publisher Income: publisher accrues income according to Rev-Share strategy.

  • Allow Strategy Override: enabling this function allows the buyer to set the revenue strategy for each separate Ping Back. This can be done by passing an extra parameter - strategy (IGNORE / ADD).

Did this answer your question?