Purchased feeder traffic often comes from thousands of different referring domains,
and sometimes from no referring domain at all (in case of popups / consoles, etc).
There's also a chance that you're trading traffic with a domain who's also indirectly
selling you traffic. All these scenarios make it difficult to accurately track how much
traffic your broker has really sent you.
The ATX v2 feeder traffic trackers solve this problem entirely in one step.
The special trackers switch the real referrer with one that you set.
For example, when you're purchasing traffic from a.com and b.com and c.com
You can use the traffic tracker to set the referrer to be "feeder.com" instead.
Then its just a matter of adding "feeder.com" as a (disabled) trade in ATX,
and all traffic from those 3 domains show up under the "feeder.com" trade!
There are 5 big advantages when using the special trackers:
1) You don't need to add 100s of domains your broker sends from, just 1
2) Traffic without a referrer also gets tracked
3) The ATX referrer stats for the 'feeder.com' trade still displays the full urls like http://www.a.com/, http://teens.b.com, http://c.com/archives/01/!
allowing you to see exactly where the traffic is coming from.
4) Trading traffic with domains that are also selling a part of their traffic via broker to you no longer skews the statistics
since sold hits show up under your special 'feeder.com' trade.
5) You can change the skim level and click patterns for all incoming feeder just by editing the 'feeder.com' trade
There are 2 ways to set things up;
1) by creating a seperate landing page for your feeder traffic, like index2.shtml
2) by adding SSi code to your regular index.shtml which calls either the regular tracker or the special feeder tracker
Scroll down to the table below, download the in-track.cgi file for your OS,
upload it in binary mode to yourdomain.com/cgi-bin/a2/ and chmod (set) the permissions to 755
Method 1. A seperate landing page
In your website content management script (usually a tgp script), go to the template management module
You will find a template file which writes its output to your index.shtml page
Make a copy of this template, and write the output to index2.shtml
Edit the template, and replace this line
<!--#include virtual="/cgi-bin/a2/in.cgi" -->
with this line
<!--#include virtual="/cgi-bin/a2/in-track.cgi?s=feeder.com" -->
Login to the ATX v2 admin, add a new trade with the following settings:
domain = feeder.com
url = http://feeder.com
trade type = disabled
toplist = off
That's it. Wait for your templates to be processed again, and the index2.shtml will be ready.
Open http://www.yourdomain.com/index2.shtml in your browser, and click on 'view source'.
You should see the following code
<script type="text/javascript">
<!--
document.cookie='a2r=feeder.com#!; path=/;'
document.cookie='a2x=#!; path=/;'
document.cookie='a2b=feeder.com#!; path=/; expires=December 31, 2100;'
// -->
</script>
Wait 1 minute, reload the ATX v2 main stats overview, and the trade "feeder.com" will show incoming traffic.
Ask your broker to send traffic to http://www.yourdomain.com/index2.shtml
Method 2. Conditional SSi calls
Open the file yourdomain.com/index.shtml in a text editor
replace this line
<!--#include virtual="/cgi-bin/a2/in.cgi" -->
with these lines
<!--#if expr="$QUERY_STRING = feed" -->
<!--#include virtual="/cgi-bin/a2/in-track.cgi?s=feeder.com" -->
<!--#else -->
<!--#include virtual="/cgi-bin/a2/in.cgi" -->
<!--#endif -->
This code calls the special tracker when the string "feed" appears in the query string
Login to the ATX v2 admin, add a new trade with the following settings:
domain = feeder.com
url = http://feeder.com
trade type = disabled
toplist = off
That's it. Wait for your templates to be processed again,
open http://www.yourdomain.com/index.shtml?feed in your browser, and click on 'view source'.
You should see the following code
<script type="text/javascript">
<!--
document.cookie='a2r=feeder.com#!; path=/;'
document.cookie='a2x=#!; path=/;'
document.cookie='a2b=feeder.com#!; path=/; expires=December 31, 2100;'
// -->
</script>
Wait 1 minute, reload the ATX v2 main stats overview, and the trade "feeder.com" will show incoming traffic.
Ask your broker to send traffic to http://www.yourdomain.com?feed
Method 1 produces less server load, but may not be supported by all site management programs
Method 1 offers better protection against abuse from outside
Method 2 is easier to setup but produces a (unnoticable) extra bit of load
A up-to-date OS however will cache the page with Method 2 so the performance difference is virtually none.
| Operating System |
Download Link |
Linux package II - 32 bit
redhat 8, redhat 9, Fedora Core 1, Fedora Core 2, CentOS 3, Debian 3 |
download |
Linux package III - 32 bit
Fedora Core 3 - 6, Debian 4 |
download |
Linux package III - 64 BIT
Fedora Core 3 - 6, Debian 4 |
download |
Linux package IV - 32 bit
CentOS 4, RedHat Enterprise Linux ES Release 4 |
download |
Linux package V - 64 BIT
CentOS 5 |
download |
|
|
