Integration with Binom¶
Binom tracker versions 1.16 and newer come with native Adspect integration. Tracker distributions include Adspect Sieve™ traffic filtering software that is locally installed on the same server as the tracker itself. This software is different from the cloud-based Adspect service in several major ways:
- Traffic filtering takes place locally on your server, i.e. the software does not make requests to the Adspect cloud in real time, resulting in dramatic increase in click processing speed. Adspect Sieve is written in C++ and sports tremendous processing power limited only by your server hardware and network bandwidth.
- No click logs or other data is sent to Adspect. Your statistics are kept private on your server. The software only performs background synchronization of filters and subscription status every once in a while. Even if it cannot contact Adspect servers or if your subscription expires it will keep working in fully autonomous mode for 3 days, giving you a grace period.
- Adspect streams are not used; Binom campaigns replace them. You do not need to do anything in the Adspect cloud service beyond purchasing a subscription and obtaining credentials.
Adspect Sieve distribution is bundled with Binom. Installation takes three simple steps:
Execute the following command with superuser privileges (log in as root or use
bash /root/binom_install.sh adspect
At the prompt (see screenshot below) type
1for “Yes” and press Enter.
Successful installation will print the
In order to use Adspect Sieve you will need to pair it with an Adspect account using its ID and API key. You will find both in your profile in Adspect clients area:
Account ID and API key are outlined with red.
In Binom, go to campaign settings, open the Protection section, tick the Adspect checkbox there, then click Add account. A dialog window will appear; enter account ID and API key in there and press the Save button:
If you need to change these credentials later, then you may do so in Settings > API.
Adspect Sieve filtering is enabled per-campaign with a campaign rule. You may use either Bot or NOT Bot rules to route traffic, depending on the logic you need: