Skip to content


Stage of development

Changes June

Changes for June

We planned small updated, but as it happens, we tested it too long, and rewrote internal tools, particularly, update system. Now during update tracker is testing connections with our servers and selecting the one from which loads goes faster.  Also, we improved the process itself, now you can easily close updates tubs, or open it from another device and update will continue as usual. There are not so many features, but all of them are useful.

Domains tests for an

It takes too long to use scripts for domains test for ban, and from time to time it bothers arbitrageurs. Now tracker will let you know by itself that it is time to change domain names for more clean ones.

In landings it looks like that.

In domains like this:

To make check work one need to indicate in settings your Google API Key. Where to find it, add it and all other questions answers are in documentation.

Notes 2.0

Everyone are bored of old notes without “beauty”, and we added it a little bit. Now in notes you can use underlined bold italics, insert screenshots of your profit rates, motivating quotes of the great names of history and lunch shopping list (to not forget).

Also, by numerous request we added notes to the offers and landings editing window.


Changes for April and June

This update was dedicated to tracker’s interface improvement and small but important for many clients functions as Cap, multicurrency, root domain tracking, enhanced API allowing to manage all tracker’s content including traffic distribution in campaigns. We updated LP Pixel, currently it works solidly in all browsers and devices. We created intra-daily trends by hours (while they are quite limited, we are going to improve this function in the next update up to trends by all tracker’s metrics). Also, tracker security was enhanced with protection against brute force and two-factor authorization. But first things first.

CAP by conversions

To date CAP can be done only by conversions but in the next iteration it will be completed by other metrics as clicks, costs, ROI, etc. It works by two schemes by ways of preferences:

1) You can select alternative offer right after CAP

2) You can select next available offer in rotation (inside path), and if there are no available, then alternative

Time zone set up is also available.

Reworking of additional domain

Apart from interface enhancing the main novelty is possibility to track domain index page through special campaigns attaching. It can be useful for detection of moderators and bots traces (real traffic very seldom positions to root domain). Through this campaign you can use as index page any html with help of integrated landing. I.e. in actual words it’s possible to build a mini-site where on pages as will be Money Page or stubs for moderation while on index page will be “white content” + tracking opportunities.

We also added opportunities of domains mass adding and domain selection for meta-refresh in campaign’s settings. We’ve already implemented possibility of mass domain changes in campaigns and check of ban in Google.

Context Menu

We had a question of where to put secondary functions without interface overloading. So, we decided to create context menu in all reports. For example, for the Campaigns page it looks like this.

It allowed us to add different mini-functions such as campaign pre-view, cost update from campaign’s page. In report this is Drilldown, editing and landings and offers pre-view form report, etc.

Also, we added ability to change campaign without necessity to open Campaigns page. Plus, we a little bit overworked filters and export, enhanced calendar and added timeframes “last 2 days” and “last 3 days”, added report by users.

New LP Pixel algorithm

We created Pixel “protecting” algorithm for browsers that block cookies. Safari mobile, Facebook browser and other small ones, now it’s working as it should be and you can add easily without tracking redirects where you want.

Enhanced API

Now through API you can manage whole tracker, campaigns, users, offers, landings, rotations, traffic distribution, and even mark publishers. Detailed documentation is being developing, but following this link you can find all methods and usage examples. Also, you can contact support for consultation.

Protection against brute force and two-factor authorization through Google authorization.

After five failure attempts to enter tracker it is blocked tightly, and can be restored only with Support assistance. But at that time, we created function of password restoring through the Google Authenticator app. If you want to know how to use it, read documentation.

Perhaps someone didn’t notice this small update, which is the best update of this year in my opinion. I mean the “Trends” by the hour (it’s only for today and yesterday for now) for all the campaigns. I used to request stats through the “Campaigns” column to see how’s everything going (bad or better). It took much time to request 30-40+ campaigns at the same time.
So for now you can just go to the “Trends”, choose “Today” and see the stats by hour instead of days.

In future we want to improve this function, expand the count of days (like 1 week), and add sections for campaigns. Now you can see it in the “Info” in the “Campaigns” column


Updates for March and April

Well, the Affiliate Conf in Moscow and the CPALife in Saint Petersburg conferences are over, now it’s time to take two months stock. Our main task was to significantly improve the user system. We want to remind that in Binow you can create an unlimited number of users in your tracker, which allows you to increase your team indefinitely.

New user system

A large number of media buyer teams use Binom. As we got a lot of feedback on multi-user access we decided to rewrite everything and make the best multi-user system on the market.

We fixed the problem of stats grouped by sources as well as open access to individual companies, landing pages, offers, sources, rotations, partner networks. Now you can share everything you want to: groups, individual campaigns, landing pages, offers, etc. It seems to me, that we rewrite half of the tracker since verification of access rights literally permeates it all and the logic of how it works is quite complicated by itself. >>>

Changes for January and February

We started working on the rotation system, tracker monitoring, and affiliate networks catalog, for after the holidays.

Rotation system

It is very simple. You just have to create a rotation, assign campaigns to it, change traffic distribution in the rotation rules, and as a resulting distribution in assigned campaigns is changed. We did our best to make it handy. As an example, you can change traffic distribution in the settings, even if a rotation has already been set. Only that campaign will be modified for the rotation and it will be marked as “custom.”

Anyway, it is easier to try it, than it is to explain it. You can find more detailed information in documentation


Changes for December

First of all, we made the second version of the traffic distribution.

Now you can reach paths in rules, edit landing pages/offers from distribution settings, policies priorities, rules/policies naming, minimizing/maximizing and a more enjoyable interface.


Changes for November


Finally, we launched our long-suffering update. We totally rewrote the system for reports generation.  It was done because of bad comparability with some of MySQL versions (some of the deep reports could not be downloaded at all), problems with report downloading by a few users, time zones necessity and other details. We have been testing the new system for a long time, gradually opening the updates. Testing started 2 weeks ago. Currently, we updated more than 60 trackers, so we don’t expect to experience any problems. Now, reports can be produced even faster.

Multiple selection of landing pages/offers in campaign’s settings

Now it is handier to add to the rotation lots of landing pages and offers. Just choose them in the window and hit button Add.


Changes for October

In October we updated devices and IP, implemented cities databases, which allowed us to determine city of a click. Also, polices of cities and tokens {city} were added, for instance, for displaying in landings. We updated interface with new window styles, fronts, scrolls and much more.  Let’s review our main changes in functionality.


Section Trends


Changes for September

September was quite efficient regarding the new functionalities.

New styles of statistic table

Some people do not like simple a white statistic table. We added two more styles of statistic table white-gray zebra and colored table where rows for profit have a green background, and un-profitable have red.


Changes for August

The release was launched successfully, although with some issues. For half of the month, we sorted out the chaos that occurred after the sales start. We refreshed and set up trackers for clients, collected feedbacks regarding new functions, improved billing-panel to work with a few subscriptions.

Sales results are impressive! Majority of testers moved to the paid subscriptions. We are so happy about it! It means that everything was not for nothing, and users really like our product.

We haven’t added much functionality, mainly we fixed small bugs, stabilized the system, rewrote part of the code responsible for the API and report generating. It allowed us to significantly decrease deep reports load time.

Also, we paid attention to documentation and developing the website.

Binom Tracker Market Launch

Binom is the fastest self-hosted tracker for an effective arbitrage.

The main point is reducing a user’s work time with the tracker, optimization of all actions advertising campaigns and user time saving due to a fast proceeding and thought-out interface.

Moreover, in the future, we want to help the user in determining the correct solution during their campaigns optimizations in a simple way, with the help of the internal functions. This is part of our plans.

This product is complicated with progressive DB architecture. We paid a lot of our attention to the development and testing of the tracker’s core to increase functionality in the near future.

Our current main advantages

– Can hold any loads. No need to scale server or to take a few servers, upgrade it, etc. In 99 percent of the cases, a usual 50 EUR/USD dedicated server is enough even for redirects.

– The highest speed of report generation through competitors. All reports, almost without exception, can be generated instantly. Time of a report preparation doesn’t depend on the total quantity of clicks in the database or in a campaign (which is the main problem of all self-hosted trackers); it means you tracker won’t slow down with a big database. Speed depends on click quantity for a given report period, and this is a nonlinear dependence. No need to delete clicks logs, if you have available disk space.

– Minimal time click processing doesn’t depend on the volume. Again, the main problem of all other current self-host trackers is that during load on a database the speed of redirects slows down which leads to decreasing of ROI. We separated these tasks, and you can refresh statistics and load reports endless times, and the speed of redirect won’t reduce. Also, the quantity of clicks doesn’t influence traffic volume. And this all was made under one database. Currently, the average speed of the redirect is 10ms, on a dedicated server with SSD disk it can be even faster. As far as I know, this is the best result for now. It will allow to significantly improve your campaign ROI.

– Multilevel reports. The majority of trackers has them. But only our tracker can produce reports by very narrow segments with hundreds of thousands of rows in under ten seconds without limitations by groupings.

Group working with campaigns. At the current moment statistics by campaign groups and sources, group deleting and campaigns cleaning are implemented.

The system of filters in statistics reporting. No need to download CSV files, open them in Excel (or in your scripts) and filter through the data. You just have to create filter in the tracker.

Line marks. You can mark publishers sent to the black and white lists if you want to have a second glance at them. Also, you can mark stopped advertisers, OS, and traffics types. Besides, there is the possibility to filter statistics by these parameters, including filtering by API.

Section Trends with statistic by all traffic, all campaign groups, by sources with nice graphs.

– Handy interface. No need to get used to it.

– Convenient API for report displaying, click price refreshing and work with offers/landers. Also, you can add report displaying by ABI saved filters in the tracker and receive complete black and white lists. We are planning further developing the API, gradually all the tracker’s functions will be available by API.

Smart Rotation function. This feature allows you to distribute traffic by paths/landings/offers taking into account clicks uniqueness and offer conversion.

Additional users with access rights.  You can add your employees or colleagues to the tracker and share with them campaigns groups, landings, offers, sources, etc. Also, you can close profit editing or viewing rights. Each user can check his/her campaign statistic.

– You can influence our product. We strive to make the tracker toward your needs by doing our best to introduce necessary functional as soon as possible. Sometimes we do it in less than a day. For example, in the current version, we implemented the transfer of cost from ExoClick. Just write us!

– Skype-support. All users who tested our tracker know how responsive and pleasant support. We are happy to answer all questions, both regarding tracker or arbitrage in general. We are doing our best to be online always, even at night. At the office, we are from 10 am to 10 pm (UTC +3). We are happy to up your tracker on any server.

Our future plans:

– Antispy plugin which will secure from Spy-services

–  Interface and traffic distribution functional reworking

– Traffic distribution templates

– Integration with affiliate networks

– Landings access protection by direct link

– Token refresh from landers

– Clicklog

Changes for July

In July we worked out the interface, eliminated its weak points and finished functionalities presented in all trackers as predefined sources, multi offers on landings, tooltips in the interface, adding tokens buttons and lots of other small changes.

Also, we added a very handy function for reports filtration, traffic distribution on the bases of uniqueness and conversion (smart rotation). But first things first.

New interface for criteria choice 

The old interface was quite simple, made hastily for the beta test. The new window looks like this

The new interface can still display criteria batched with the possibility to copy them by list, for example, list OS versions or devices types. Also, we implemented redirect by time, an option to exact match in a rule, rule of a click uniqueness by all tracker or by a campaign. In the next iteration, we will improve the general interface for settings, add paths in rules, possibility to change names of paths/rules, landings/offers editing from them and other functions.

Smart rotation

In all trackers, traffic distribution between paths, landings and offers takes place evenly, in random order respective to distribution weight. This is correct, but it is not in an optimum way. A user who saw your lander today is less likely to become a lead, than if he were shown another lander or path in which traffic would go to a new funnel or offer. The possibility that user will convert on the same path is small. To optimize traffic distribution taking into account these ideas, we have implemented this function a Smart Rotation in the tracker.

Filter system

With its help, you can easily get annual finished white or black lists of your campaigns, with the possibility to save filters and use them in the future with the help of the API.

It looks like this

List of changes

– Improved interface of selection window of redirect criteria

– Filter system in reports

– Predefined traffic source

– Multi offers on landings

– Traffic distribution by paths/landings/offers on the basis of click uniqueness/conversion

– Traffic loss percent in source and particularly in campaign

– Redirect by time

– Update cost feature is now faster 50x

– Redirect by click uniqueness by all traffic or by one campaign

– Possibility to choose exact match in criteria

– New kind of click id

– Quantity of decimals after comma was increased in CR

– Possibility to delete groups with assigned campaigns/offers/landings

– Current CPC in campaigns’ table

– Button “.txt” in reports with copy of column Name in report

– Transfer to lander’s encoded timestamp (token {htime})

– Parameter &exit=1 в  – Clicked URL’s during its usage is not counted as LP CTR

– Duplicate algorithm on the bases of GET-parameters transferring to the landing

– Prompts in the interface

– Buttons for adding tokens

– Background reload function of statistic by days

– Database memory usage optimization

– Added to reports header to the campaign name of TS

– Advanced settings  in campaign setup


What comes next?

The following week we will implement one more update up to version 1.0! We will implement a new, optimized database requests for statistic generation which will allow to dramatically increase download report speed by campaigns, especially of very intensive ones with 2-3 groupings with hundreds of thousand lines. For instance, Device Brand + Device Model + IP.  This will allow downloading even the most demanding reports. Reports that were impossible to download will be generated in 20 seconds, what took 20 seconds will become available in 7 seconds, for example. Moreover, complete compatibility with all MySQL versions including MariaDB remains the same.

Also, the following week we are launching 1 Click Install of the tracker.


If this update is successful, then on August 1 we will release Binom Tracker.

During the current week, we will be transferring our users from test subscription to release. Pricing policy hasn’t changed, as it was initially planned. The first license will cost $99, and the second and further (additional) $49. All changes to the billing panel are completed. Now you don’t have to register multiple accounts for different licenses.

The new milestone for the product roadmap is going to happen next; it will be more responsible and interesting period.

Our plans for August

– Section Trends with reports by dates for all campaigns, by campaigns group, by sources, etc. with nice graphs

– Traffic distribution interface update. We will improve functional and renew design

– API input to the tracker. For example, if you want to perform a batch change of lander domains, costs of campaigns or download offers it will be comfortable to do through API.  We will add scripting examples for API usage.

– Graphs in reports by campaigns, probably we will do some kind of dashboard to check it in one click all the main information by campaign’s traffic.

–Traffic distribution preset in campaign saving, and other ideas we can’t disclose for obvious reasons. Also, I think in release update to 1.0 we will arrange a user survey for those who updated their trackers, and question what functional should be added in the first place, as we did before. Previous experience was quite successful.

We ask all users to update. In case of any problems we are always happy to see you in skype Don’t hesitate to ask any questions.


We count on your support!

Changes for June

It was a month of the tracker’s code refactoring, internal process optimization and bugs fixing.

We created changelog on site.

List of changes

– Leads in campaign statistic

– Possibility for custom set up of  S2S for each campaign

– We added page Monitor, introduced internal errors check in

– Group campaigns deleting and cleaning

– Redirect by Device type

– We made optimization of information request displaying by last hours. Currently reports don’t overload database

– Time displaying between click and conversion on pages Conversions and Leads in reports

– Conversions in reports by campaigns

– Changes in в Domains, now it works without folders

– Made changes {clickid} in direct url to count conversions

– Made token {time} for displaying on landing timestamp

– We took away Hello, %username% and name set up

– Displaying in conversion table traffic source and campaign

– Request optimization for conversion displaying

– During redirect to other company we don’t count traffic consumption in campaign from which changeover was done

Changes for May

This month we concentrated on the database architecture redesign. We also reduced load requests quantity, the number of tables was reduced more than 2 times, as well we decreased on 40 % the database volume by N clicks ensuring that on the same size hard disk much more information will be stored

We introduced reports by campaigns group and general statistics by source. Now you can analyze publishers by all your white and black campaigns in total or, for example, prepare black list by all sources at once. With help of such cross-reference reports campaign analyze rises to a new level.

We developed an API for statistic displaying. It is very simple. You can find in Settings the parameter with a key &api_key=aaaabbbbccccddddeee, add this is key to a link, and it will be displayed as JSON. In the URL, all parameters will be more or less understandable.

Detailed documentation

We conducted a survey regarding future functionalities.

Here are the results:

Protection from Spy-services 79.17% 19

Interface traffic distribution improving (paths, rules) 66.67% 16

Clickid report and stats by conversions in campaign 37.50% 9

Groups statistic (by a few campaigns, by source etc) 37.50% 9

Trends, Statistic by days, weeks, etc by all campaigns, groups 29.17% 7

Graphs 29.17% 7

Pre-defined traffic source 29.17% 7

Campaign dashboard 20.83% 5

Documentation 20.83% 5

Statistic filtration system 20.83% 5 20.83% 5

Multi offers 16.67% 4

1-click installer (through SSH) 12.50% 3

Traffic interface improving 12.50% 3

Drilldown report 4.17% 1

Import of campaign, landings, offers from other trackers 4.17% 1

Based on this information we will be developing these requests to our tracker in the future.


Changes for April

April was fairly efficient. We made a lot of changes and additions to the functionalities, and fixed a huge number of different bugs.

We added icons to buttons.

We introduced additional domains for tracking.

We made enough functional Update costs (traffic costs update):

We updated devices databases; I redid my landers right away, and as a result, ROI increased over 2x in a single sweep. We improved mobile-detect extremely, and it detects desktops perfectly. Any problems with desktop detection because of browscap are solved. Device type works smoothly, in the next update, we will do redirect by it.

Now examples


List of changes

– Documentation

– New system of device definition (it improves detect by times)

– Multi-domains

– New installer

– Buttons icons

– Statistic by days in camping reports

– Update costs: selection Costs/CPC

– Update costs: Time zones

– Update costs: Import from  CSV

– Update costs: automatic adjustment of current timeframe of a report

– PHP error handler (we will be able to check your mistakes without long investigations)

– Name randomization CSV files

– Notification of exit from campaign editing without saving

– Temp_report –> MyISAM

– Internal procedures optimization, reducing by 2x the database accesses

– Divided custom timeframe in date and time

– Redirect by IP ranges (both recording forms)

– Default grouping in reports: Path-Offer-Lander

– Deleted column Language on a landing page, instead of it language is written in gray to the right form the landing’s name

– Combined Chromium and Chrome in reports by browsers

– Browser version cut to 2 numbers by deleting Chrome’s odd zeros.

– OS versions cutting to two numbers

– Defaulted values of Token’s name (t1,t2..) in fill-in-the-blank field  in a source

– Took away autocompletion  in tokens in source editing

– Tokens {clickid} and {campaignkey} on landers

– Possibility to direct traffic to defined  path or LP (&to_path=1&to_lander=2)

– We changed the cloning processing of offers, landers etc. Now it works without glitches.

– Apply button

– Redirect by user-agent by entry

– New update system

– Checking of input value during conversion update

– Statistic by Rules in reports by paths

Regarding development. In next update we will try to create leads in reports, upsells (cost adding to conversion, for subscription, goods, etc.). We are gradually developing the API and the 1-click installer through SSH for fast set up based on droplets etc.

The only thing we need to rewrite is payment panel for discounts by multi-licensing.

In general, we are planning to slow down development of new functionalities to normalize current one (bugs, bugs, bugs).

I tested responsiveness on DigitalOcean. It is not that bad. Average respond on a dedicated server is 30 ms, and on 4 GB DO it is about 50 ms with decreasing trend during replenishment of internal agent database. 2 GB memory is not enough, but works normally. If the volume is not that big, it can handle it, but response times will be slower to 80-100ms. So, I advise increasing RAM to 4 GB.

Most of the time required for a click processing takes place at the server’s databases; this is the only thing we can’t influence. We spent 80-90 percent of our time on that. But, in the next update, we will be downloading to our tester’s base the top agents (by detect quantity) during update and installation. This way response times will be decreased by 2x. We are fighting for each millisecond!

We updated the tracker with an error reporting system and other issues monitoring. Soon we will add a permanent response check-mark to check if something has gone wrong. These problems (with response time increase) is something all trackers have. You never know where or what component are having an issue and nobody pays attention to it. And how wrong that is! This key element directly influences your ROI.

Changes for March

In March we released 5 updates (0.976,0.977,0.978,0.979,0.980). Lots of work was done for the installer, system for updating the tracker, and internal algorithm stabilization.

Full list of changes

– Updating system improvement

– Installer improvement

– Redirect by full country name and by abbreviation

– Name of generated CSV-file in reports

– Interface of update window

– Added redirect by referral

– Added redirect by referral day of week

– Added redirect by type and speed of connection

– Added redirect by language

– Added redirect by screen resolution

– Click price import form token Cost

– Increased CPC task accuracy to 5 digits after comma

– In Stats, we made 4 digits after comma for CPC and EPC

– Tokens auto fill in source settings

– Correct sorting in reports by day of week and hour

– In landers or offer URLs,  http:// is added automatically

– In redirect direct or return rule is shown

– In reports by traffic rules, flows by usual paths is marked as Default

– Bug tracker website

– Security improvement

– Internal procedure of statistic recalculation in case of failure

– Internal procedure for offer editing

– Improved procedure of backup copy save

– Increased highest values of URL and name

– Improved work with additional data

– Advanced cleaning algorithm

– Developed fields in all tables of database

The month of testing

Starting February 24, we started closed testing.  Gradually we are gathering testers. Fewer and fewer bugs in the backlog are left to squash, and we are gathering more testers. Some of them have transferred all their traffic to our tracker and earn money with us. We are really grateful for it. Thank you for your trust.

One month has already passed. And we have found these results.

–   We launched 6 updates

–   Fixed  91 bugs

–   Made 165 changes

–   Now we have about 30 testers. Active ones are about 10-15.

We are doing our best to fix bugs ASAP. Critical bugs are being fixed as soon as we are informed about it. During testing we had no cases of traffic lost. The first week of testing we mainly worked on the installer and update system. It is not an easy thing to install a tracker, you need root access to the database. There is no other way. And many other details.

To simplify the tracker update as much as possible, we created a 1-click update. User sees in the heading “New update!”, clicks on it and window with changes are being opened. You just need to Install and all is ready. No need to download or add things. This is very important taking into account that updates are issued quite often.

What are our weaknesses now?

Determination of desktop device. Now we use browscap, but it works too slowly, we are planning to change it.

Old base of mobile devices. Free WURFL is now being tested, we will apply the change in April.

Unfinished redirect system (rules). It had lots of bugs. Now it works quite well. But the interface is not too handy.

Custom timeframe. Currently, it is bundled together with time, we are planning to separate it by date/time. This point didn’t prove itself useful, it is not convenient.

During testing and real usage, lots of different interesting details are crossing my mind, if we implement all of them it would be super handy. Together with huge speeds, it gives you a feeling of simplicity and comfort while working.  It is like transferring from slow to fast Internet, you can feel the difference. When you get used to it, it is very hard to switch back to slow trackers.

As I probably wrote before. Our aim is to create simple and easy tracker without a tricky interface and huge amounts of different functions. We want to save your time, make your work pleasurable and help with our functionalities to make your campaigns more profitable.

We made small video with tracker demo. Unfortunately, my dedicated server is not the most powerful one and doesn’t have SSD disks (which will give approximately 2x increase in speed), but it is possible to observe approximate speeds

Tracker core reworking

From the early fall, we are working on the reworking of our tracker database architecture. We succeeded to improve in redirects speed and reports building.

Currently, situation is as following

1. The response time on any load is about 30 ms! We couldn’t emulate load with hundreds of millions of clicks in a day. But I don’t think there are that many people who can buy this much traffic. Theoretically, the tracker can handle as much.

Algorithmically it is not that important how much of input traffic is sent. All current tests were done at volumes approximately 30 million in a day for difficult campaigns with lots of paths, landing pages, offers, and rules.

2.Unique system of stats aggregation was implemented. The tracker develops all necessary report data on the clicks stage recording. Thanks to which all base reports by campaigns, offers, landings pages, etc. are generated instantly (tens of ms) in any timeframes. I can’t disclose all the details, but this is really cool.

3.Over the past week we improved the report generation system and transferred successes with main reports to reports inside of a campaign. We managed to receive almost all reports at any depth instantly. We still experience some issues with tokens and referrals, but we are currently solving it and incorporating data into the interface. It looks amazing right now. Besides, the tracker can output data either per page or all together for any term. Generation speed of any report doesn’t depend on clicks quantity in any given campaign or the quantity in the database in general. So, you can instantly navigate through the pages of a report, minimize and maximize groupings, download CSV. Reports that couldn’t be generated in a wink, also work very fast, because the majority of necessary data is stored ready-made.

Next step is to learn how to generate different reports by offers, landing pages, sources, etc. For example, if you want to check report by all publishers for all time.

As for functionality, the tracker is currently at the same level of other trackers. You have all you need to work, but without superfluous features. The only thing I’d like to add in beta is bots analysis, which will provide the percentage of mobile bots on for publisher. It can analyze very precisely. A more accurate analysis is hardly possible.

In general lots of people offer their help. Thank you for not being indifferent to our work.

What started as “database optimisation” ended as a full reworking of tracker core, clicks recording algorithms and all stats generation. Currently, we are working on interface improvement, site design and billing.

The first operating test

Hi everyone!

Here is another report about our progress for all potential clients and testers.

We have done a lot within the previous month. We have almost finished reworking the structure of our database, wrote the procedure for reports building and click saving. We completed most of the tasks we planned and now we need to unite all the elements in one script, solving some issues and eliminating bugs along the way.

We made an operating test yesterday which rendered us amazing results. I am going to tell about it a bit more.

We used our good old server for testing with the following characteristics:

Intel® Xeon™ E3-1245 Quad-Core incl. – 32 GB DDR3 RAM ECC, 2 x 3 TB 6 Gb/sec 7200 RPM HDD SATA3

ОС: Ubuntu 12.04 Precise LTS 64 bit

Apache server with ISPManager has not been optimized for our database yet.

The operation was made by a multithreaded emulator which I wrote in python. It emulates IP, ISP, Device, tokens, in general, all the parameters of clicks.

Tracker worked with a click, recorded it in the database, handled redirects (test was made with rules) and it showed the time of performing different stages of work on the lander.


The first version

We have just completed the minimal version of the tracker. What do we have now?

The campaign system. Leads Last Hour, Profit Last Hour, Clicks Last Hour – These parameters are available in the statistics; 2 pages schedule; notes are available.
– Landing page system. You can organize your landings by language and group. Landing constructor is not ready, and we are not certain whether it will be available in the first versions or not.
Offer system. They may be organized by country and by group
– Paths and redirect rules. There is an opportunity to redirect the offers, direct link and even send to other campaigns. Possibility to redirect not uniques (by cookies) is in the work.
Devices, browsers, ISP database. We are constantly looking for better databases. If you know some, please, don’t hesitate to let us know.
Cloaking and change of referring source (referrer). For the moment only meta-refresh is done. In future, we plan to make changes to the system.
Sources of traffic. Preset tokens, conversions passing to the source
Affiliate networks.
Manual adding of conversions and update cost of clicks.
Settings page.

All in all, the main part core of the tracker is almost ready. We still need to work on some functions, interface, make security licensable and crypt the codes.

Tracker is self-hosted. The main points are simplicity, speed and functionality.

I found a partner who will provide us servers during beta-testing (we will try to optimize the server for our tracker and to agree on optimal prices for our clients) and afterward. The aim is to make (installation and) the usage of the tracker as simple as in its Cloud version.

All in all, the main part core of tracker is almost ready. We still need to work on some functions, interface, make security licensable and crypt the codes.
Tracker is self-hosted. The main points are simplicity, speed and functionality.

I found a partner who will provide us servers during beta-testing (we will try to optimize the server for our tracker and to agree on optimal prices for our clients) and afterwards. The aim is to make installation and the usage of the tracker as simple as in its Cloud version.