Trade settings:

• Default url (for filtered traffic and errors) - used for redirecting filtered traffic (i.e. bots).
• Trade algorithm - choose trade algorithm between Effectiveness, Stable, UE, UEE, Only by ratio.
        In all algorithms cron script first computes priority of each trade (by one of trade algorithms), then sorts them by priority and adds them in outlist in that order. Several first positions in outlist have nonzero weight factors (you can set them in outlist settings). The meaning of these factors is the same as in other outlist-based scripts. They are used to compute probability of redirect to url in that outlist position on surfer click. If surfer has visited all trades in outlist positions with nonzero weight factors - he will be redirected to one of trades in outlist positions with zero weight factor ( script try's to sends only uniques )
        Effectiveness - default algorithm. Priority computed by PRIORITY=(CLICKS/OUT)*RATIO*Q, where CLICKS - amount of qualified clicks made by surfers that came from that trader, OUT - amount of qualified outs script sent to that trader, Q - other optional adjustments (like Click Again, Quality, etc).
        Stable - almost identical to Effectiveness. Difference only in handling of stability ( look for stability factor docs below ). Effectiveness (and also UE and UEE) algorithm uses long term and short term "clicks" data for that and Stable algorithm uses long term and short term "unique in" data. So, Stable algorithm is sensitive to changes of "unique in" from trader and Effectiveness is sensitive to changes of "clicks" from trader. That's all the difference. Stable algorithm works almost like UCJ but better Smile
        UE - Priority computed by PRIORITY= (UIN/OUT)*(CLICKS/OUT)*RATIO*Q, where UIN - amount of unique hits in from trader. So, in this algorithm priority depends also on amount of hits in from trader. This algorithm is good for sites where your income doesn't depends on amount of clicks made by surfers ( i.e. sites selling their exit traffic to broker).
        UEE - Identical to UE, but effectiveness of trade weighs more. Formula for priority is PRIORITY=(UIN/OUT)*(CLICKS/OUT)*(CLICKS/OUT)*RATIO*Q
        Only by ratio - Priority computed by formula PRIORITY=(UIN/OUT)*RATIO*Q Maybe someone needs this algorithm, but I dont recommend it
• Use exout - check this box to enable exout function ( not unique clicks will be redirected to exout url ). If unchecked - not unique clicks will be sent to random trade in outlist (recommended)
• Exout url - sets exout url
• Enable "Click Again" adjustments - check that box to enable "Click Again" adjustments ( priority of each trade will be multiplied on "Click Again" factor)
• Redirect referer-blocked traffic - if set "To galleries" - referer blocked traffic will be redirected to specified url in link to out script regardless of skimming ratio in links. If no url is specified in link to out script - referer-blocked traffic redirect url will be used. If set "To trades" - referer blocked traffic will be redirected to trades regardless of skimming ratio in links. If set "To specified url" - referer blocked traffic will be redirected to referer-blocked traffic redirect url
• Referer-blocked traffic redirect url - sets referer-blocked traffic redirect url
• Redirect nocookie clicks - same meaning as with Redirect referer-blocked traffic but with respect to nocookie clicks
• Nocookie clicks redirect url - sets nocookie clicks redirect url
• Page rotation type - choose between "concurrent" and "consecutive". For more detailed information refer to Quick Start guide.
• Stability factor - This is very important setting. Stability factor can be between 0 and 1. If it set to 0 priority of each trade will be calculated only on long term (daily) stats - thats good for accuracy of trade but this way script can send traffic in crazy way ( i.e. your script can send 500 hits in one hour and 30 hits in another ).Also it will have low response to changes in traffic from your traders (i.e. one of your traders may stop sending you hits but you will continue to return or one of your traders may start big forces but you will return not so big). If stability factor set to 1 - only short-term (hourly) stats will be used to compute priority . This way script will be very reactive and trade also may become unstable (stability of trade will depends on stability of traffic flow from that trade). If stability factor between 0 and 1 long-term and short-term stats will be used together to compute priority. This way will be achieved quick response to active traffic conditions and stability of your best trades. By default this factor is set to 0.5 (just like in UCJ) and thats recommended value.

Force handling settings:

• Maximum amount of force positions in outlist - just like it sounds. Recommended values between 1 and 3. If you set it to high value - forced trades will get lower quality traffic.
• Percent of weight for all force positions in outlist (0-99) - i.e. you set it to 50 and your Maximum amount of force positions in outlist setting set to 2. This way if you have 2 or more forced trades, 2 of them will appear in outlist with weight 25% of overall weight of all trades in outlist. If you have only one forced trade - it will appear in outlist with weight 50% of overall weight of all trades in outlist. Set it to big enough value if you want to send high quality traffic to forced trades (but you also can control quality of traffic for each trade separately in edit trade page). 

Anticheat settings:

General notes about anticheat settings: Please, watch at traffic stats. If you see that % of qualified clicks for all traffic is too low, you may want to lighten anticheat settings to achieve better accuracy of trade. % of qualified clicks and outs should be at least 75% I believe.

• Maximum clicks from one ip. Others - to default url - after this amount of clicks from one ip all other clicks will not be qualified and will be sent to default url instead of some trade or content. If set to 0 - this feature will not be used. If you want to use this feature, be sure to set this setting big enough ( 100 or more) otherwise many legit surfers will be redirected to default url.
• Maximum qualified clicks from one ip - just like it sounds. I would recommend to set it between 10 and 15. Surfers will not be redirected to default url after this amount of clicks like in previous setting.
• Maximum qualified outs from one ip to trader - actually that is not anticheat setting but more like "outgoing traffic quality controling" setting. If script sent more than specified amount of outs from one ip to traders, all other outs from this ip will be sent to trades for free.
• Minimum click interval in seconds to qualify that click - just like it sounds. Fast clicks from one surfer will not be qualified. Recommended value between 1 and 5 sec.
• Qualify nocookie clicks - if checked, nocookie clicks will be qualified. I wouldn't recommend to qualify nocookie clicks, becouse most of your traders will not qualify them but cheater can send you all his nocookie traffic. So, cheater will get full return from you and you will not get any return from clicks of cheater's surfers.
• Redirect all known bots to default url - if checked, clicks of all known web bots will not be qualified and will be redirected to default url.
• Qualify clicks only from known browsers - just like it sounds. It is recommended to set it on.
• Qualify clicks only from browsers accepting gzip encoding - all modern browsers accepts gzip encoding but many surfers use some proxies wich cuts Accept-Encoding header and clicks of that surfers will not be qualified if this setting is checked. So, be carefull with this setting since it can greatly reduce accuracy of trade.

Other settings:

• Default traders filter for main stats - sets default stats filter when you enter your admin area.
• Default traders sort type for main stats - sets default stats sort type when you enter your admin area.
• Maximim amount of traders on main stats - sets amount of traders to show on main stats (all trader's list will be splitted by pages)
• Maximum time since last click to keep surfer info - information about surfer (ip, visited sites, etc) keeps in database until certain amount of minutes (defined in this field) elapsed since last surfer's click. Recommended value - 60 minutes. If this setting is set to very high number - this may result in lower speed and more memory usage(and may even cause heap table overflow if you have very big sites). If this setting is set to very low number - speed and memory usage will be lower but accuracy of trade may also be lower.
• Toplists update interval - just like it sounds.
• Use mod_geoip instead of built-in geoip database - Check this box if you have mod_geoip installed and want to use it for country identification instead of built-in geoip database for better speed. But mod_geoip with free geoip database is less accurate than built-in geoip database.
• Output compressed pages - check this box if you want to output gzip-compressed pages to surfers, browsers of which accept gzip encoding, to speed up page loading for surfers and to reduce BW usage. PHP should be compiled with zlib for this feature and you should use provided ftt_index.php as your index page (look at quick start guide).
• Compression level (1-9) - sets gzip compression level if Output compressed pages is on. 1 - lowest compression level. 9 - highest.
• FTT version - in this field you can mannually change FTT version. Most likely you will not need to do that.
• FTT license key - if you upgrade from free version you can enter your obtained license key here. Otherwise do not change this value.