Arrow Trader 5

Installation Guides
Admin Modules
References

Arrow Trader Core

Installation Guides
Admin Modules
References

Arrow Trader eXtreme V2

Installation Guides
Admin Modules
References

Arrow Trader eXtreme V1

Installation Guides
Admin Modules
References

Arrow Trader Lite 3

Installation Guides
Admin Modules
References

Q&A

Getting started

Search


atl reference
main overview



1.
The active trades table shows trades that are currently in your outgoing list and will receive traffic.
All statistics tables are divided in 4 parts;
1) the checkbox for multi-processing, the unique id of the trade and the domain with various symbols behind it, to indicate icq nrs, hourly forces, etc.
2) the 60 minute stats of the trade. The 60 min stats do not reset per hour but rotate per minute. So for example at 14:40, you see the stats of 13:40 - 14:39.
3) the 24 hour stats of the trade. These are really 1440 minute stats, and like the 60 min stats they rotate per minute. In other words, ATL works with a true timeline.
4) the last selection of columns shows general information and settings for a trade; forces, links to in-depth stats, links to reset / edit / delete the trade, etc
All the columns in the main overview can be enabled and disabled via menu --> template.

2.
Passive trades are trades that are not in your outgoing list. These trades are often times disabled, or do not meet your minimum size requirements. When a trade with a permanent force (force time = -1) is in the passive trades list, the force is not active. However, when a trade has a temporary force (force time > 0), the trade will be placed in the active trades list and in the outgoing list for as long as the force lasts and has not yet been filled.

3.
The button 'select all' will check all checkboxes for all trades, so you can easily mass edit them.
The button 'add trade' will open a pop-up window, allowing you to add a new trade.

4.
By double clicking any trade row, it will highlight. By single clicking on it again the color will go back to normal.
To set the highlight color, go to menu --> css, and edit row .hirow{}.
When you assign a permanent background color to a trade, it can not highlight when you double click it.




5.
Under the Active and Passive trades, a third table shows info about non-trades. These can not be deleted since ATL needs them to function properly.
0) blocked: ATL has several hitbot / garbage filters in the files in.cgi and out.cgi. When a hit is blocked it shows up here.
1) gallery: when a surfer clicks a link that goes to a gallery, the row gallery gets +1 hit out.
2) nocookie: surfers without cookies can be redirected to a set url or galleries only. When that happens this row is credits with +1 hit out.
3) noref: surfers with browsers that don't have any data in the http_referer field are counted as noref. A large percentage of this traffic comes from bookmarkers.
4) blocked ref: when a surfer clicks a link that goes to atl/out.cgi, normally your own domain is set as the referring domain. When the http_referer field however is empty, atl cannot tell where the hit came from, and worse, when this surfer would be redirected to a trade, your trade would not be able to tell it came from you. So ATL can filter out these hits and send them elsewhere.
5) notrade: notrade hits are hits that come from a website (domain) that is not in your trades list. These hits are not bookmarkers / noref hits! When the number of notrade hits keeps growing, check the referrer stats for notrade to see where the hits are coming from. Also, when you delete a trade, all stats of that trade are moved to the row notrade, so your final stats don't show a gap. On several installations of apache, when an image is broken, your main site is reloaded. As a result, notrade will show many hits with virtuall no clicks. In the referrers list of notrade, you will see your own domain. When this happens, check your site and the webserver (apache) errorlog for broken images.
6) exout: when a surfer has visited all your trades, there are 2 options; you can either send the surfer to galleries for the rest of his clicks, or to a special url, the extra out url. When a surfer is sent to the exout url, it shows up in this row. Even when you set ATL to send surfers to galleries, make sure that you fill out the exout url, because it's also used for some exceptions.
7) Search Engines: ATL can track hits from search engines apart from your other trades. In the menu go to SE for the current list of SE domains. All hits that come from one of these domains is counted as SE hit. This way you don't have to add hundreds of disabled domains to your script.
8) atout: a very small percentage (around 0.6% - 0.8%) of the clicks are redirected to arrowscripts.com as form of payment, to support this script. The exact amount can be tracked here. Clicks on toplist links are not skimmed.

6.
The Site Totals table shows a summary of several import statistics of your site, including the average skimming percentage and the amount of uniques.

7.
Multiple copies of ATL 3 can be linked together, both local copies (installed on the same server) and remote copies (installed on a different server). By clicking on the title of a site you will be instantly redirected to the ATL admin of that site.

8.
The bottom table offers several tools to mass-process trades. You can mass reset, mass edit and mass delete trades. First you need to select one or more trades via the checkboxes in front of each trade. To mass edit trades, fill out the fields that you wish to change. Fields that you don't change remain untouched. This also counts for the background color and skim fields. If you wish to reset the bg colors or skim percentages of trades, fill out a hyphen (-)

9.
At the bottom of every ATL admin page, there are 3 numbers.
1) The first number shows the execution time in seconds. You will find that ATL runs incredibly fast.
2) The second number shows the local server time. The statistics are updated at the beginning of every minute.
3) the third number shows the version and build of ATL3. In this example we're running build 06.
A changelog of ATL3 per build can be found on www.arrowscripts.com/atl_changelog.shtml

Help us improve our articles by rating them
- This article is -

Too long & complicated

Too short & simple

Not relevant enough

Just about right
4393