AlterCPA for arbitrageur teams

Principles of the traffic aggregator for arbitrage

Aggregator collects traffic and orders from various sources, whether webmaster or third-party networks, and distributes it to recipients, collecting statistics.

Step 1. Receiving traffic

Sources of traffic for the aggregator can be webmasters, members of the arbitrageur team or registered in the CPA-network, and third-party CPA-networks. All clicks and leads come to single "entry point" - the interface of the aggregator network.

Step 2. Distributing leads

The incoming leads are carried by different CPA-networks and transferred to them for processing. In this case, you can configure the distribution of traffic in the most profitable way, directing the leads depending on the countries to the networks that provide the largest payment for the traffic from the specified country.

Step 3. Money and analytics

After processing the leads, the statistics from all networks merge into a single analytical tool. Choose the most advantageous options for the distribution of orders based on payments, the percentage of confirmed orders, the speed of withdrawal of funds. The received finance is distributed between webmasters and third-party networks.

What platform version should you choose?

The aggregator can be easily deployed on both a professional and a free version of the platform.

AlterCPA Professional

The professional version of the platform will allow you to aggregate both commodity and non-commodity traffic, regardless of its sources. Sending leads can be carried out in any described (and some not described) in the documentation. Allows to get advanced Analytics reports for the sites, UTM-marks the time of receipt of leads, redemption. Provides the option of installing meters and the "pixels" of ad networks. Allows you to clone vendor sites and third-party partner networks in semi-automatic mode. Optimal for any amount of traffic, less demanding on server resources.

What tools can you use?

The basis of the traffic aggregator is the automatic integration with other affiliate networks.

There are two schemes of integration with third-party networks. We will designate them as commodity and non-commodity. or info.

  1. Commodity scheme provides for working with your landing pages and further transfer of leads to the partner network through the API. The partner network must support at least one API function: sending leads. Ideally, you will need a function to check the status of leads by their ID. If it does not exist, status updates are implemented via postback requests. More integration under this scheme is described in the section "Integration with other networks" of the documentation, and in the documentation there are examples and ready-made instructions for integration with existing networks.
  2. Non-commodity integration allows you to work with networks without API and offers implemented on their own independent sites. It requires the vendor site ability to memorize a single numeric parameter - the ID of a click, and any interesting events - notify the network through the postback request. In partner networks, it is convenient to use SubID to store the click ID. More information about this scheme is described in the "working with commodity offers" section of the documentation.

When implementing any of these schemes, offers are created on the network side, their landing and pre-landing pages are started, deductions are set up. If you plan to distribute the same offer to different networks depending on the country or other parameters, it is recommended to familiarize yourself with the lead distribution settings.

In the professional version of the platform, the process of creating landing pages has been brought almost to automatism. In the admin section "Offers" of your platform, go to the "Download" button in the website cloning interface. Select offer, please provide links to the sites Lindenhof and prelanding this offer in the network, which will pour traffic. Sites are automatically downloaded and hosted on servers prelanding landing pages and your network. Prelanding in this case, in most cases, ready for use. Landing pages require pre-cleaning and removal of the tracking code of the target partner network.